HeaderSIS.jpg

IS480 Team wiki: 2014T1 Chocolicious Proj Management

From IS480
Jump to navigation Jump to search
Chocoliciousmenu.jpg
Overview Project Management Documentation
1. Project Progress 1. Our Team 1. Documents
2. Project Description 2. Time Line 2. Database
3. Stakeholders 3. Schedule 3. Use Cases
4. Learning Outcomes 4. Risks & Constraints 4. System Diagram
5. Metrics

Our Team

Time Line

ScheduleChoco.png

Schedule

Planned Actual
Iter Tasks Milestone Start End Start End
1 Preparation
  • Documentation & Requirement Gathering
  • Research on Technologies
  • Setup necessary software
  • Develop project proposal

Project Management

  • Team roles & management
  • Project Schedule
  • Risk Assessment
  • Learning Outcome

Technical Requirements

  • Develop Use Case Diagram
  • Draft database entity
23 May 2014
12 Jun 2014
23 May 2014
12 Jun 2014
2 Management & Documentation
  • Finalise project proposal
  • Prepare project writeup on wiki
  • Refine UCD
  • Develop diagrams
Proposal deadline

Coding Tasks

  • Develop mock UI & framework
  • Build up database
  • Login & authentication
  • Grant user roles
  • Create claims
  • Save function for unsubmitted claims
  • Edit/ update claims
  • View claims

Testing

  • Develop test cases for revelant functions
  • Integration testing
  • Debugging

Documentation

  • Update revelant documents & progress
  • Update wiki page & project progress
Proposal
18 Jun 2014
13 Jun 2014
26 Jun 2014
13 Jun 2014
26 Jun 2014
3 Coding Tasks
  • Refine UI and develop UI for relevant functions
  • Code for submission/editing of claims to relevant parties
  • Code for viewing/editting of all accounts for SMUSA Fin sec
  • Code for viewing/editting of accounts for users of different level

Testing

  • Develop test cases for revelant functions
  • Integration testing
  • Debugging

Management & Documentation

  • Update wiki page & project progress
  • Update database & diagrams
27 Jun 2014
10 Jul 2014
27 Jun 2014
4 Management
  • Revise documentations / wiki page
  • Revise diagrams & test cases

Coding Tasks

  • Refine UI and develop UI for relevant functions
  • Approval of claims
  • Rejection of claims
  • Resubmission of rejected claims
  • Report generation for claims
  • Filtering of reports for relevant user type
  • Reject claims due to error
  • Change of claims status

Testing

  • Develop test cases for revelant functions
  • Integration testing
  • Debugging

Documentation

  • Update wiki page & project progress
11 Jul 2014
31 Jul 2014
5 Management
  • Revise documentations / wiki page
  • Prepare for acceptance presentation
  • Revise diagrams & test cases

Coding Tasks

  • Refine UI and develop UI for relevant functions
  • Submit budget
  • Propose budget (save function for individual account)
  • Code for SMUSA CBD & SMUSA fin sec to edit submitted budget

Testing

  • Develop test cases for revelant functions
  • Integration testing
  • Debugging

Documentation

  • Update revelant documents & progress
  • Update wiki page & project progress
Acceptance Presentation
Acceptance Presentation
14 Aug 2014
1 Aug 2014
14 Aug 2014
6 Management
  • Revise documentations / wiki page
  • Prepare for acceptance presentation
  • Revise diagrams & test cases

Coding Tasks

  • Refine UI and develop UI for relevant functions
  • Code for SMUSA fin sec to allocate funds (from SAC account to every clubs' expenditure account)
  • Code for deposit revenue into expenditure account (CBD fin sec & SMUSA sec)

Testing

  • Develop test cases for revelant functions
  • Debugging

Documentation

  • Update revelant documents & progress
  • Update wiki page & project progress
15 Aug 2014
28 Aug 2014
7 Management
  • Revise documentations / wiki page
  • Revise diagrams & test cases

Coding Tasks

  • Refine UI and develop UI for relevant functions
  • Fund transfer between CBD & Club fin sec
  • Report generation for fund transactions

Testing

  • Integration testing
  • Develop test cases for revelant functions
  • Debugging

Documentation

  • Update revelant documents & progress
  • Update wiki page & project progress
29 Aug 2014
11 Sep 2014
8 Management
  • Revise documentations / wiki page
  • Revise diagrams & test cases

Coding Tasks

  • Refine UI and develop UI for relevant functions
  • Inject funds from SAC reserve
  • Pull back funds from SAC reserve
  • Viewing of expenditure & SAC account
  • Report generation of transaction of pullback and allocation

Testing

  • Integration testing
  • Develop test cases for revelant functions
  • Debugging

Documentation

  • Update revelant documents & progress
  • Update wiki page & project progress
12 Sep 2014
25 Sep 2014
9

Mid term preparation

Management

  • Revise documentations / wiki page
  • Revise diagrams & test cases

Coding Tasks

  • Refine UI and develop UI for relevant functions
  • Code for SMUSA fin sec to change reserve limit
  • Editalble pull back formula for SMUSA fin sec
  • Viewing of reserve account
  • Report generation of transaction of pullback and allocation

Testing

  • Integration testing
  • Develop test cases for revelant functions
  • Debugging

Documentation

  • Update revelant documents & progress
  • Update wiki page & project progress
Mid Term Presentation
Mid Term Presentation
10 Oct 2014
26 Sep 2014
10 Oct 2014
10 Management
  • Revise documentations / wiki page
  • Revise diagrams & test cases

Coding Tasks

  • Refine UI and develop UI for relevant functions
  • Code for SMUSA fin sec to approve reserve withdrawal
  • Code for request reserve withdrawal (CBD & Club fin sec)
  • Report generation of transaction history

Testing

  • Integration testing
  • Develop test cases for revelant functions
  • Debugging

Documentation

  • Update revelant documents & progress
  • Update wiki page & project progress
11 Oct 2014
23 Oct 2014
11 Management
  • Revise documentations / wiki page
  • Revise diagrams & test cases

Coding Tasks

  • Refine UI and develop UI for relevant functions
  • Code for concurrency control

Testing

  • Testing
  • Develop test cases for revelant functions
  • Debugging

Documentation

  • Update revelant documents & progress
  • Update wiki page & project progress
24 Oct 2014
6 Nov 2014
12

Prepare for Poster Day

Management

  • Revise documentations / wiki page
  • Revise diagrams & test cases

Coding Tasks

  • Refine UI and develop UI for relevant functions

Testing

  • Testing
  • Develop test cases for revelant functions
  • Debugging
Poster Day

Documentation

  • Update revelant documents & progress
  • Update wiki page & project progress
Poster Day
10 Nov 2014
7 Nov 2014
20 Nov 2014
13

Prepare for Final Presentation
Prepare for Poster Day

Management

  • Revise documentations / wiki page

Testing

  • Final round of testing
Final Presentation
Poster Day

Documentation

  • Update revelant documents & progress
  • Update wiki page & project progress
Final Presentation
24 Nov - 2 Dec 2014
Poster Day
3 Dec 2014
21 Nov 2014
3 Dec 2014

Risks & Constraints

Risk Table

Probability 1-low 2-medium 3-high
Effect 1-low 2-medium 3-high
Priority Higher number more important
Project Risk
Possible Risk Reason & Implications Probability
(1-3)
Effects
(1-3)
Priority
(P x E)
Strategy
Medical Certificate (MC) / Leave of Absence (LOA)
Reason
  • Falling sick
  • Personal reasons
  • Unforeseen circumstances

    Implications
    Allocated work may not be completed on time
  • Low (1) Medium (2) 2 Project Manager to reschedule tasks or reallocate tasks to another member.


    Buffer days should be included in project schedule to accommodate such situations.


    Minimal or lack thereof knowledge on
  • accounting-related software/tools
  • frameworks
  • languages
  • Reason
    Not learned prior to start of project.


    Implications
    Additional time will need to be allocated for learning the language and framework

    Medium (2) Medium (2) 4 Project Manager to allocate time for collaborative learning for the team.
     

    Lead Developer to organize meetings to facilitate team learning.

    Team to speak with SMUSA accountant.


    Change of project requirements
    Reason
    Current requirements no longer fits client’s needs


    Implications
    Delay in project completion date

    Medium (2) Medium (3) 6 Project Manager to adjust project schedule to accommodate the changes.
     

    Business Analyst to update team on the change of requirements.

    System Analyst and Quality Assurance Analyst to ensure that team changes codes in accordance to change in requirements without affecting code quality.


    Hardware unavailability
    Reason
    Laptop crash


    Implications
    Member whose laptop has crashed will require time to either repair it or get a new laptop and re-install all required programs

    Medium (2) Low (3) 6 Project Manager to reschedule tasks or reallocate tasks to another member.
     

    Member may be able to borrow laptop from team members to complete immediate tasks.


    Incomplete tasks
    Reason
    Unable to code out the function


    Implications
    Deviations from project schedule will affect the whole team

    Medium (1) High (3) 3 Project Manager to reschedule tasks or reallocate tasks to another member.


    Member may be able to borrow laptop from team members to complete immediate tasks.


    Miscommunication
    Reason
    The idea was not presented or understood correctly


    Implications
    Time spent wrongly on things not required

    Low (1) High (2) 2 Business Analyst to ensure that each team member fully understands exactly what he/she is to accomplish.


    Project Manager to allocate some time for team member to rectify the mistakes.


    Conflicts among team members
    Reason
    Team members might have a difference in opinion on how things should be done and unable to solve it on their own


    Implications
    Such conflicts impede smooth project flow

    Low (1) High (2) 2 Project Manager to arrange meeting for team to come together and talk things out.



    Technical Risk
    Possible Risk Reason & Implications Probability
    (1-3)
    Effects
    (1-3)
    Priority
    (P x E)
    Strategy
    Defective components
    Reason

    Faulty parts in machine

    Implications Corrupted projects files resulting in much time wastage

    Low (1) Medium (3) 3 Team member to resolve problem on individual machine.


    Systems Analyst to ensure that shared project version has not been corrupted. Project Manager to assign team member to provide assistance if need be.


    Data Loss
    Reason
    Hardware used to store data might be corrupted


    Implications
    Project will not be updated resulting in wasted time and more time to be wasted

    Low (1) High (3) 3 Member to immediately revert back to previous version in repository and continue with work.


    Project Manager to assign team member to provide assistance if need be.



    Business Risk
    Possible Risk Reason & Implications Probability
    (1-3)
    Effects
    (1-3)
    Priority
    (P x E)
    Strategy
    User-unfriendly system
    Reason

    Non-technical users may find the system user-unfriendly

    Implications
    System will be deemed useless if users reject it

    Low (2) Medium (3) 6 Business Analyst and Quality Assurance Analyst to ensure that user guide cater to non-technical users.


    Project Manager to arrange meeting with client and personally teach him/her.

    Metrics