HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2014T1 Chocolicious Proj Management"

From IS480
Jump to navigation Jump to search
Line 1,221: Line 1,221:
 
! style="background: #336600; color: white" | Start Date || style="background: #336600; color: white" | End Date
 
! style="background: #336600; color: white" | Start Date || style="background: #336600; color: white" | End Date
 
|-
 
|-
|  1 || 23-May-14 || 12-Jun-14 || 20 || 23-May-14 || 12-Jun-14 || 20 || 1 ||
+
|  1 || 23-May-14 || 12-Jun-14 || 33 || 23-May-14 || 12-Jun-14 || 32 || 93.9697 ||
 
|-
 
|-
|  2 || 13-Jun-14 || 26-Jun-14 || 13 || 13-May-14 || 26-Jun-14 || 13 || 1 ||
+
|  2 || 13-Jun-14 || 26-Jun-14 || 21 || 13-May-14 || 26-Jun-14 || 21 || 100 ||
 
|-
 
|-
|  3 || 27-Jun-14 || 10-Jul-14 || 13 || 27-Jun-14 || 10-Jul-14 || 13 || 1 || Changed Proj framework, integrate with Lean Startup's Minimum Viable Product
+
|  3 || 27-Jun-14 || 10-Jul-14 || 16 || 27-Jun-14 || 10-Jul-14 || 13 || 81.25 || Changed Proj framework, integrate with Lean Startup's Minimum Viable Product
 
|-
 
|-
 
|  4 || 11-Jul-14 || 31-Jul-14 || 20 || 11-Jul-14 || ||    ||  ||  
 
|  4 || 11-Jul-14 || 31-Jul-14 || 20 || 11-Jul-14 || ||    ||  ||  

Revision as of 10:22, 31 July 2014

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

ChocoOurTeam.jpg

Time Line

ChocoMVPTimeline.jpg

The time line shows the IS480 milestones and the iterations for the whole project. Lining the schedule, are the functions that will be released with each deployment. The functions in the later iterations will be added to the functions already available from previous iterations.

Schedule

Planned
Iter Tasks Milestone 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
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
  • Edit/ update claims
  • Delete claims
  • View claims
  • Save function for unsubmitted 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
3 Coding Tasks
  • Refine UI and develop UI for relevant functions
  • Code for club application
  • Code for acceptance and rejection of club application
  • Code for removal of club application
  • Code for editing of claims to relevant parties
  • Code for submission 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

Testing

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

Management & Documentation

  • Update wiki page & project progress
  • Update database & diagrams


Deployment
Users Claims Accounts Budgeting Club Application Reports Additional features
Create, Read, Update, Delete (C.R.U.D.)

Login
Grant user roles

C.R.U.D.

View claims
Save unsubmitted claims

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

Coding Tasks

  • Refine UI and develop UI for relevant functions
  • Code for approval of claims
  • Code for rejection of claims
  • Code for resubmission of rejected claims
  • Code for reject claims due to error
  • Code for change of claims status
  • Code for propose budget (save function for individual account)
  • Code for edit/update of budget
  • Code for removal of budget
  • Code for submit budget
  • Code to view budget

Testing

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

Documentation

  • Update wiki page & project progress


Deployment
Users Claims Accounts Budgeting Club Application Reports Additional features
C.R.U.D.

Login
Grant user roles

C.R.U.D.

View claims
Save unsubmitted claims
Editing of claims
Claims submission

R.U.

View accounts

Create application

Acceptance & Reject
Remove

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
  • Code for SMUSA CBD & SMUSA fin sec to edit submitted
  • 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)
  • Code for inject funds from SAC reserve
  • Code for viewing of SAC account

Testing

  • Develop test cases for revelant functions
  • Deploy a Minimum Viable Product (MVP)
  • Integration testing
  • Debugging

Documentation

  • Update revelant documents & progress
  • Update wiki page & project progress


Deployment
Users Claims Accounts Budgeting Club Application Reports Additional features
C.R.U.D.

Login
Grant user roles

C.R.U.D.

View claims
Save unsubmitted claims
Editing of claims
Claims submission
Approval & Rejection Resubmission Status changed

R.U.

View accounts

C.R.U.D.

View budget
Save & Submit

Create application

Acceptance & Reject
Remove

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 pull back funds from SAC reserve
  • Code for editalble pull back formula for SMUSA fin sec
  • Code for viewing of reserve account
  • Code for SMUSA fin sec to approve reserve withdrawal
  • Code for request reserve withdrawal (CBD & Club fin sec)

Testing

  • Develop test cases for revelant functions
  • Deploy MVP
  • Integration Testing
  • Debugging
  • UAT - Iteration 5 deployment

Documentation

  • Update revelant documents & progress
  • Update wiki page & project progress


Deployment
Users Claims Accounts Budgeting Club Application Reports Additional features
C.R.U.D.

Login
Grant user roles

C.R.U.D.

View claims
Save unsubmitted claims
Editing of claims
Claims submission
Approval & Rejection Resubmission Status changed

R.U.

View accounts
SAC - Fund allocation
SAC - Injecting funds
SAC - Revenue deposit
View SAC accounts

C.R.U.D.

Submission
View budget
Save & Submit
Edit submitted budget

Create application

Acceptance & Reject
Remove

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
  • Code for fund transfer between CBD & Club fin sec
  • Code for report generation for fund transactions
  • Code for report generation of transaction of pullback and allocation

Testing

  • Develop test cases for revelant functions
  • Deploy MVP
  • Integration Testing
  • Debugging
  • UAT - Iteration 6 deployment

Documentation

  • Update revelant documents & progress
  • Update wiki page & project progress


Deployment
Users Claims Accounts Budgeting Club Application Reports Additional features
C.R.U.D.

Login
Grant user roles

C.R.U.D.

View claims
Save unsubmitted claims
Editing of claims
Claims submission
Approval & Rejection Resubmission Status changed

R.U.

View accounts
SAC - Fund allocation
SAC - Injecting funds
SAC - Revenue deposit
View SAC accounts
SAC - Change reserve limit
SAC - Pullback funds
SAC - Edit pullback formula
SAC - View reserve accounts
SAC - Request reserve withdrawal
SAC - Approve reserve withdrawal

C.R.U.D.

View budget
Save & Submit
Edit submitted budget

Create application

Acceptance & Reject
Remove

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
  • Code for club level report
  • Code for CBD level report
  • Code for SMUSA level report
  • Code for report generation of transaction history
  • Code for analytics dashboard
  • Code for e-receipt generation
  • Code for e-payment function

Testing

  • Develop test cases for revelant functions
  • Deploy MVP
  • Integration Testing
  • Debugging
  • UAT - Iteration 7 deployment

Documentation

  • Update revelant documents & progress
  • Update wiki page & project progress


Deployment
Users Claims Accounts Budgeting Club Application Reports Additional features
C.R.U.D.

Login
Grant user roles

C.R.U.D.

View claims
Save unsubmitted claims
Editing of claims
Claims submission
Approval & Rejection Resubmission Status changed

R.U.

View accounts
SAC - Fund allocation
SAC - Injecting funds
SAC - Revenue deposit
View SAC accounts
SAC - Change reserve limit
SAC - Pullback funds
SAC - Edit pullback formula
SAC - View reserve accounts
SAC - Request reserve withdrawal
SAC - Approve reserve withdrawal
SAC - Fund transfer

C.R.U.D.

View budget
Save & Submit
Edit submitted budget

Create application

Acceptance & Reject
Remove

Fund transactions

Transaction of pullback and allocation

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 club level report
  • Code for CBD level report
  • Code for SMUSA level report
  • Code for report generation of transaction history
  • Code for analytics dashboard
  • Code for e-receipt generation
  • Code for e-payment function
  • Code for vendor recommendation

Testing

  • Develop test cases for revelant functions
  • Deploy MVP
  • Integration Testing
  • Debugging
  • UAT - Iteration 8 deployment

Documentation

  • Update revelant documents & progress
  • Update wiki page & project progress


Deployment
Users Claims Accounts Budgeting Club Application Reports Additional features
C.R.U.D.

Login
Grant user roles

C.R.U.D.

View claims
Save unsubmitted claims
Editing of claims
Claims submission
Approval & Rejection Resubmission Status changed

R.U.

View accounts
SAC - Fund allocation
SAC - Injecting funds
SAC - Revenue deposit
View SAC accounts
SAC - Change reserve limit
SAC - Pullback funds
SAC - Edit pullback formula
SAC - View reserve accounts
SAC - Request reserve withdrawal
SAC - Approve reserve withdrawal
SAC - Fund transfer

C.R.U.D.

View budget
Save & Submit
Edit submitted budget

Create application

Acceptance & Reject
Remove

Fund transactions

Transaction of pullback and allocation
Club level
CBD level
SMUSA level
Transaction history

Club level
E-receipt & E-payment

Club level
Analytics dashboard

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 analytics dashboard
  • Code for e-receipt generation
  • Code for e-payment function
  • Code for vendor recommendation

Testing

  • Develop test cases for revelant functions
  • Deploy MVP
  • Integration Testing
  • Debugging
  • UAT - Iteration 9 deployment

Documentation

  • Update revelant documents & progress
  • Update wiki page & project progress


Deployment
Users Claims Accounts Budgeting Club Application Reports Additional features
C.R.U.D.

Login
Grant user roles

C.R.U.D.

View claims
Save unsubmitted claims
Editing of claims
Claims submission
Approval & Rejection Resubmission Status changed

R.U.

View accounts
SAC - Fund allocation
SAC - Injecting funds
SAC - Revenue deposit
View SAC accounts
SAC - Change reserve limit
SAC - Pullback funds
SAC - Edit pullback formula
SAC - View reserve accounts
SAC - Request reserve withdrawal
SAC - Approve reserve withdrawal
SAC - Fund transfer

C.R.U.D.

View budget
Save & Submit
Edit submitted budget

Create application

Acceptance & Reject
Remove

Fund transactions

Transaction of pullback and allocation
Club level
CBD level
SMUSA level
Transaction history

E-receipt & E-payment

Analytics dashboard
Vendor recommendation

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

  • Develop test cases for revelant functions
  • Deploy fully functioning system
  • Integration Testing
  • Debugging
  • UAT - Iteration 10 deployment

Documentation

  • Update revelant documents & progress
  • Update wiki page & project progress


Deployment
Users Claims Accounts Budgeting Club Application Reports Additional features
C.R.U.D.

Login
Grant user roles

C.R.U.D.

View claims
Save unsubmitted claims
Editing of claims
Claims submission
Approval & Rejection Resubmission Status changed

R.U.

View accounts
SAC - Fund allocation
SAC - Injecting funds
SAC - Revenue deposit
View SAC accounts
SAC - Change reserve limit
SAC - Pullback funds
SAC - Edit pullback formula
SAC - View reserve accounts
SAC - Request reserve withdrawal
SAC - Approve reserve withdrawal
SAC - Fund transfer

C.R.U.D.

View budget
Save & Submit
Edit submitted budget

Create application

Acceptance & Reject
Remove

Fund transactions

Transaction of pullback and allocation
Club level
CBD level
SMUSA level
Transaction history

E-receipt & E-payment

Analytics dashboard
Vendor recommendation

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

  • Develop test cases for revelant functions
  • Deploy fully functioning system
  • Integration Testing
  • Debugging
  • UAT - Iteration 11 deployment
Poster Day

Documentation

  • Update revelant documents & progress
  • Update wiki page & project progress


Deploy Fully Functioning System
Users Claims Accounts Budgeting Club Application Reports Additional features
C.R.U.D.

Login
Grant user roles

C.R.U.D.

View claims
Save unsubmitted claims
Editing of claims
Claims submission
Approval & Rejection Resubmission Status changed

R.U.

View accounts
SAC - Fund allocation
SAC - Injecting funds
SAC - Revenue deposit
View SAC accounts
SAC - Change reserve limit
SAC - Pullback funds
SAC - Edit pullback formula
SAC - View reserve accounts
SAC - Request reserve withdrawal
SAC - Approve reserve withdrawal
SAC - Fund transfer

C.R.U.D.

View budget
Save & Submit
Edit submitted budget

Create application

Acceptance & Reject
Remove

Fund transactions

Transaction of pullback and allocation
Club level
CBD level
SMUSA level
Transaction history

E-receipt & E-payment

Analytics dashboard
Vendor recommendation

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

  • UAT - Iteration 12 deployment
  • Final round of testing
Final Presentation
Poster Day

Documentation

  • Update revelant documents & progress
  • Update wiki page & project progress


Deploy Fully Functioning System
Users Claims Accounts Budgeting Club Application Reports Additional features
C.R.U.D.

Login
Grant user roles

C.R.U.D.

View claims
Save unsubmitted claims
Editing of claims
Claims submission
Approval & Rejection Resubmission Status changed

R.U.

View accounts
SAC - Fund allocation
SAC - Injecting funds
SAC - Revenue deposit
View SAC accounts
SAC - Change reserve limit
SAC - Pullback funds
SAC - Edit pullback formula
SAC - View reserve accounts
SAC - Request reserve withdrawal
SAC - Approve reserve withdrawal
SAC - Fund transfer

C.R.U.D.

View budget
Save & Submit
Edit submitted budget

Create application

Acceptance & Reject
Remove

Fund transactions

Transaction of pullback and allocation
Club level
CBD level
SMUSA level
Transaction history

E-receipt & E-payment

Analytics dashboard
Vendor recommendation

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
Project may not be accepted
Implications/Reason

Project is being done for the third time

Medium(2) High(3) 6 Do our best to satisfy expectations of Course Coordinator.


Incompatibility with client’s server when application is deployed
Implications/Reason

Client has their own server/domain

Low (1) High(3) 3 Project Manager to search for plausible solutions.


Lead Developer to explore deploying on other servers in case compatibility issues cannot be resolved.


Underestimation of scope during development and testing
Implications/Reason

Over-confidence of development ability

Low (1) High(3) 3 Project Manager to allocate buffer time in schedule and monitor schedule metrics closely. Scheduling of tasks to be adjusted according to metrics.


Team to seek advice from supervisor as to whether certain functionalities should be dropped.


Insufficient users for testing
Implications/Reason

Lack of incentives for users to do testing for us

Medium(2) Medium(2) 4 Business Analyst to discuss with sponsors to provide users with incentives.


Inaccurate feedback given by testers
Implications/Reason

Wrong testing mind-set (i.e. purpose of test is to show that application works, not to find defects or testers’ lack of commitment to support the testing efforts)

Medium(2) Medium(2) 4 Team to get non-IT users for testing to ensure that feedback is more applicable to the generic public to ensure user-friendliness.


Testers to be briefed and encouraged to test the application without reservations.






Team Risk
Possible Risk Reason & Implications Probability
(1-3)
Effects
(1-3)
Priority
(P x E)
Strategy
Team is faced with technical difficulties
Implications/Reason

Inadequate skills

Medium(2) High(3) 6 Lead Developer to learn these new skills and teach team.


Systems analyst to research on other methods/technologies that could provide an easier solution.


Team member is faced with sudden illness
Implications/Reason

Virus attack

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


Project Manager to include buffer days in project schedule to accommodate such situations.


Team member drops module at the eleventh hour
Implications/Reason

Inability to cope

Low(1) High(3) 3 Project Manager to reallocate tasks.


Team members to devote more time to FYP.


Malfunction of software/hardware during development phase
Implications/Reason

Software crash/hardware malfunction

Medium(2) High(3) 6 Project Manager to reschedule tasks.


Team to consistently back up all data.



Sponsor Risk
Possible Risk Reason & Implications Probability
(1-3)
Effects
(1-3)
Priority
(P x E)
Strategy
Constantly adding/changing of requirements
Implications/Reason

Sponsor unsure of all that they want from the very beginning

High(3) High(3) 9 Major changes are not permitted after agreement on requirements.


Project Manager to look at schedule for minor changes to see if project can still be completed on time if changes are accommodated.
Lead Developer and Systems Analyst to accommodate changes if changes are accepted.
Business Analyst to reject if changes are not accepted.


Project is not taken up by SMUSA after completion
Implications/Reason

Users are not comfortable with the system and opt instead to revert back to their old way of doing things

High (3) Low (1) 3 Team to organize training sessions for users.


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


SMUSA does not know how to operate the system
Implications/Reason

SMUSA lacks technical knowledge

Medium(2) Low (1) 2 Business Analyst to discuss with SMUSA on whether to add user manuals.


Miscommunication between Business Analyst and SMUSA
Implications/Reason

Language interpretation issues

High(3) Low (1) 3 Team to discuss with supervisor before proceeding.

Metrics

Schedule Metrics

The formula for calculating schedule metrics is as follows: Estimated time / Actual Time * 100

Score (S) tiers Actions to take
S <= 50% Team's progress is TOO SLOW!!!
  1. Reflect on progress and reassess schedule.
  2. Consider dropping functions.
50% < S <= 90% Team's progress is too slow. Tasks are possibly under-estimated.
  1. Consider the possibility of tasks being under-estimated.
  2. Use buffer days if available.
    • If there are no buffer days available, consider dropping functions.
90% < S <= 110% Estimations are fairly accurate.
110% < S <= 150% Team's progress is too fast
  1. Reflect on progress and reassess schedule.
  2. Add number of days gained as buffer days.
150% < S Team's progress is TOO FAST!!!
  • Mitigations are the same as the previous tier.


Iteration Planned Duration Actual Duration Score Remarks
Start Date End Date Start Date End Date
1 23-May-14 12-Jun-14 33 23-May-14 12-Jun-14 32 93.9697
2 13-Jun-14 26-Jun-14 21 13-May-14 26-Jun-14 21 100
3 27-Jun-14 10-Jul-14 16 27-Jun-14 10-Jul-14 13 81.25 Changed Proj framework, integrate with Lean Startup's Minimum Viable Product
4 11-Jul-14 31-Jul-14 20 11-Jul-14
5 1-Aug-14 14-Aug-14 13
6 15-Aug-14 28-Aug-14 13
7 29-Aug-14 11-Sep-14 13
8 12-Sep-14 25-Sep-14 13
9 26-Sep-14 10-Oct-14 14
10 11-Oct-14 23-Oct-14 12
11 24-Oct-14 6-Nov-14 13
12 7-Nov-14 20-Nov-14 13
13 21-Nov-14 3-Dec-14 12

Bug Metrics

Severity Description
Low impact (1 point) Unimportant. Typo error or small user interface alignment issues.
High impact (5 points) The system runs. However, some non-critical functionalities are not working.
Critical impact (10 points) The system is down or is un-usable after a short period of time. We have to fix the bugs to continue.

Points Calculation: Total = 1 x num (low) + 5 x num (high) + 10 x num (critical)

Points in iteration (P) Action
P <= 5 Fix during buffer time only.
5 < P < 10 Use the planned debugging time.
10 <= P Stop current development and resolve the bug immediately. Project Manager reschedules the project.