Difference between revisions of "IS480 Team wiki: 2014T1 Chocolicious Proj Management"
Line 32: | Line 32: | ||
==Schedule== | ==Schedule== | ||
− | |||
<!-- Scrollable table --> | <!-- Scrollable table --> | ||
Line 252: | Line 251: | ||
<ul> | <ul> | ||
<li>Refine UI and develop UI for relevant functions</li> | <li>Refine UI and develop UI for relevant functions</li> | ||
− | <li>Code for SMUSA CBD & SMUSA fin sec to edit submitted </li> | + | <li>Code for SMUSA CBD & SMUSA fin sec to edit submitted budget</li> |
<li>Code for SMUSA fin sec to allocate funds (from SAC account to every clubs' expenditure account)</li> | <li>Code for SMUSA fin sec to allocate funds (from SAC account to every clubs' expenditure account)</li> | ||
− | |||
− | |||
<li>Code for viewing of SAC account</li> | <li>Code for viewing of SAC account</li> | ||
</ul> | </ul> | ||
− | + | <b> Injection and Deposits shifted to Iteration 6, to focus on functions planned for Acceptance instead in Iteration 5. </b><br/> | |
<b>Testing</b><br> | <b>Testing</b><br> | ||
<ul> | <ul> | ||
Line 297: | Line 294: | ||
| R.U.<br/> | | R.U.<br/> | ||
View accounts<br/> | View accounts<br/> | ||
− | <font color="red"> Revenue deposit </font><br/> | + | <!--<font color="red"> Revenue deposit </font><br/>--> |
<font color="red"> SAC - Fund allocation </font><br/> | <font color="red"> SAC - Fund allocation </font><br/> | ||
− | <font color="red"> SAC - Injecting funds </font><br/> | + | <!--<font color="red"> SAC - Injecting funds </font><br/>--> |
<font color="red"> SAC - View accounts</font><br/> | <font color="red"> SAC - View accounts</font><br/> | ||
| C.R.U.D.<br/> | | C.R.U.D.<br/> | ||
Line 331: | Line 328: | ||
<b>Coding Tasks</b><br> | <b>Coding Tasks</b><br> | ||
<ul> | <ul> | ||
+ | <li>Code for deposit revenue into expenditure account (CBD fin sec & SMUSA sec)</li> | ||
+ | <li>Code for inject funds from SAC reserve</li> | ||
+ | <li>Code for SMUSA fin sec to change reserve limit</li> | ||
<li>Refine UI and develop UI for relevant functions</li> | <li>Refine UI and develop UI for relevant functions</li> | ||
<li>Code for pull back funds from SAC reserve</li> | <li>Code for pull back funds from SAC reserve</li> | ||
− | |||
<li>Code for viewing of reserve account</li> | <li>Code for viewing of reserve account</li> | ||
<li>Code for SMUSA fin sec to approve reserve withdrawal</li> | <li>Code for SMUSA fin sec to approve reserve withdrawal</li> | ||
<li>Code for request reserve withdrawal (CBD & Club fin sec)</li> | <li>Code for request reserve withdrawal (CBD & Club fin sec)</li> | ||
</ul> | </ul> | ||
− | + | <b>Modifiable Pull back Formula removed (function was not required, it was initially included due to misunderstanding of requirements on our part.)</b><br/> | |
<b>Testing</b><br> | <b>Testing</b><br> | ||
<ul> | <ul> | ||
Line 379: | Line 378: | ||
View accounts<br/> | View accounts<br/> | ||
<font color="red"> Change reserve limit </font><br/> | <font color="red"> Change reserve limit </font><br/> | ||
− | |||
<font color="red"> View reserve accounts </font><br/> | <font color="red"> View reserve accounts </font><br/> | ||
<font color="red"> Request reserve withdrawal </font><br/> | <font color="red"> Request reserve withdrawal </font><br/> | ||
<font color="red"> Approve reserve withdrawal </font><br/> | <font color="red"> Approve reserve withdrawal </font><br/> | ||
− | SAC - | + | <font color="red">SAC - Injecting funds <br/> |
− | SAC - | + | <font color="red">SAC - Revenue deposit <br/> |
− | SAC - | + | <font color="red"> SAC - Pullback funds </font><br/> |
SAC - View accounts<br/> | SAC - View accounts<br/> | ||
− | |||
| C.R.U.D.<br/> | | C.R.U.D.<br/> | ||
View budget<br/> | View budget<br/> | ||
Line 478: | Line 475: | ||
|} | |} | ||
− | | | + | |<center>UAT 1<br><b>05 Sep 2014</b></center> |
|<center>29 Aug 2014</center> | |<center>29 Aug 2014</center> | ||
|<center>11 Sep 2014</center> | |<center>11 Sep 2014</center> | ||
Line 499: | Line 496: | ||
<li>Code for analytics dashboard</li> | <li>Code for analytics dashboard</li> | ||
<li>Code for e-receipt generation</li> | <li>Code for e-receipt generation</li> | ||
− | <li>Code for | + | <li>Code for Vendor Recommendation </li> |
</ul> | </ul> | ||
− | + | <b>E-Payment shifted to later after Midterm</b><br/> | |
+ | <b>Analytic Dashboard has been dropped to focus on Vendor Recommendation and E-Payment.</b><br/> | ||
+ | <b>SAP Integration has been dropped due to external reasons.<br/>The team has however decided to persist with the objective of SAP Integration by coming up with another function: Auto Approval to accomplish the same objective as this will greatly value add to the Accounting Information System. Upon discussion with our supervisor, we have been approved to go ahead. We recognise that there may be some risk involved with the task, but we are determined to resolve that together with our client. </b><br/> | ||
<b>Testing</b><br> | <b>Testing</b><br> | ||
<ul> | <ul> | ||
Line 566: | Line 565: | ||
− | |<font color="red" | + | |<font color="red">E-receipt</font> |
− | |||
|} | |} | ||
− | | | + | |<center>UAT 2<br><b>19 Sep 2014</b></center> |
|<center>12 Sep 2014</center> | |<center>12 Sep 2014</center> | ||
|<center>25 Sep 2014</center> | |<center>25 Sep 2014</center> | ||
Line 592: | Line 590: | ||
<li>Code for SMUSA level report</li> | <li>Code for SMUSA level report</li> | ||
<li>Code for report generation of transaction history</li> | <li>Code for report generation of transaction history</li> | ||
− | <li>Code for | + | <li>Code for Vendor Recommendation</li> |
− | <li>Code for e- | + | <li>Code for e-Receipt Mailing</li> |
− | |||
<li>Code for vendor recommendation</li> | <li>Code for vendor recommendation</li> | ||
</ul> | </ul> | ||
Line 662: | Line 659: | ||
− | | | + | |E-receipt<br/> |
− | + | <font color="red">Vendor recommendation</font><br/> | |
− | |||
|} | |} | ||
Line 688: | Line 684: | ||
<ul> | <ul> | ||
<li>Refine UI and develop UI for relevant functions</li> | <li>Refine UI and develop UI for relevant functions</li> | ||
− | |||
− | |||
<li>Code for e-payment function</li> | <li>Code for e-payment function</li> | ||
+ | <li>Code for Auto Approval</> | ||
<li>Code for vendor recommendation</li> | <li>Code for vendor recommendation</li> | ||
</ul> | </ul> | ||
Line 759: | Line 754: | ||
|<font color="red">E-receipt & E-payment</font><br/> | |<font color="red">E-receipt & E-payment</font><br/> | ||
− | + | <font color="red">Vendor recommendation</font><br/> | |
− | + | <font color="red">Auto Approval</font> | |
|} | |} | ||
Line 847: | Line 842: | ||
|E-receipt & E-payment<br/> | |E-receipt & E-payment<br/> | ||
− | |||
Vendor recommendation<br/> | Vendor recommendation<br/> | ||
+ | Auto Approval | ||
|} | |} | ||
Line 942: | Line 937: | ||
|E-receipt & E-payment<br/> | |E-receipt & E-payment<br/> | ||
− | |||
Vendor recommendation<br/> | Vendor recommendation<br/> | ||
+ | Auoto Approval | ||
|} | |} | ||
Line 1,038: | Line 1,033: | ||
|<center>3 Dec 2014</center> | |<center>3 Dec 2014</center> | ||
|} </div> | |} </div> | ||
− | |||
==Risks & Constraints== | ==Risks & Constraints== |
Revision as of 12:12, 4 October 2014
![]()
|
Contents
Our Team
Time Line
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.
C.R.U.D. refers to Create, Read, Update, Delete.
Schedule
Planned | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Iter | Tasks | Milestone | Start | End | ||||||||||||||||||
1 | Preparation
Project Management
Technical Requirements
|
|||||||||||||||||||||
2 | Management & Documentation
Coding Tasks
Testing
Documentation
|
18 Jun 2014 |
||||||||||||||||||||
3 | Coding Tasks
Testing
Management & Documentation
|
|||||||||||||||||||||
4 | Management
Coding Tasks
Testing
Documentation
|
|||||||||||||||||||||
5 | Management
Coding Tasks
Injection and Deposits shifted to Iteration 6, to focus on functions planned for Acceptance instead in Iteration 5.
Documentation
|
14 Aug 2014 |
||||||||||||||||||||
6 | Management
Coding Tasks
Modifiable Pull back Formula removed (function was not required, it was initially included due to misunderstanding of requirements on our part.)
Documentation
|
25 Aug 2014 |
||||||||||||||||||||
7 | Management
Coding Tasks
Testing
Documentation
|
05 Sep 2014 |
||||||||||||||||||||
8 | Management
Coding Tasks
E-Payment shifted to later after Midterm
Documentation
|
19 Sep 2014 |
||||||||||||||||||||
9 |
Mid term preparation Management
Coding Tasks
Testing
Documentation
|
10 Oct 2014 |
||||||||||||||||||||
10 | Management
Coding Tasks
Testing
Documentation
|
|||||||||||||||||||||
11 | Management
Coding Tasks
Testing
Documentation
|
27 Oct 2014 |
||||||||||||||||||||
12 |
Prepare for Poster Day Management
Coding Tasks
Testing
Documentation
|
10 Nov 2014 |
||||||||||||||||||||
13 |
Prepare for Final Presentation Management
Testing
Documentation
|
1 Dec 2014 24 Nov - 2 Dec 2014 Poster Day 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.
|
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.
|
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.
|
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.
|
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.
|
Team member drops module at the eleventh hour |
Implications/Reason
Inability to cope
|
Low(1) | High(3) | 3 | Project Manager to reallocate tasks.
|
Malfunction of software/hardware during development phase |
Implications/Reason
Software crash/hardware malfunction
|
Medium(2) | High(3) | 6 | Project Manager to reschedule tasks.
|
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 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.
|
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. |
External Risk | |||||
---|---|---|---|---|---|
Possible Risk | Reason & Implications | Probability (1-3) |
Effects (1-3) |
Priority (P x E) |
Strategy |
Application will not be used after completion |
Implications/Reason
Users are resistant to change
|
Medium(2) | High(3) | 6 | User Champion We have discussed with SMUSA and agreed that the current SMUSA finance secretary - Ellora, is the user champion of the system.
|
No maintenance of system after completion of project |
Implications/Reason
No appointed person to maintain system.
|
Medium(2) | Medium(2) | 4 | We have discussed with our client, and come to this arrangement with our client:
|
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!!!
|
50% < S <= 90% | Team's progress is too slow. Tasks are possibly under-estimated.
|
90% < S <= 110% | Estimations are fairly accurate. |
110% < S <= 150% | Team's progress is too fast
|
150% < S | Team's progress is TOO FAST!!!
|
Schedule Log | ||||
---|---|---|---|---|
Iteration | Planned Duration | Actual Duration | Metric Score | Action |
1 | 20 | 20 | 1.00 | Proceed as planned |
2 | 13 | 14 | 0.93 | Proceed as planned |
3 | 13 | 12 | 1.08 | Proceed as planned |
4 | 21 | 22 | 0.95 | Proceed as planned |
5 | 13 | 13 | 1.00 | Proceed as planned |
6 | 13 | 15 | 0.87 | Underestimated complexity of coding tasks, arrange more time for similar tasks in future iterations |
7 | 13 | 13 | 1.00 | Proceed as planned |
8 | 13 | 13 | 1.00 | Proceed as planned |
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. |
Bug Log | ||
---|---|---|
Iteration | Remarks | Points |
3 | When record contains multiple clubs, only some will get deleted even though all are selected to be deleted | 5 |
3 | Add and delete options work only from second try onwards | 1 |
4 | Able to set amount to negative number | 1 |
4 | Error when submitting too large an amount for claims | 1 |
4 | Error when duplicate club id | 1 |
4 | Able to add club with neither club id nor club name | 5 |
4 | Able to submit claim without entering claim amount (amount will be nil) | 1 |
4 | Error when adding non-existent clubfinsec | 1 |
5 | Clicking on "confirm email" brings user to wrong page | 5 |
5 | Entering large amounts for claims, deposits and budgets causes program to crash | 10 |
6 | not selecting category when creating new budget event causes program to crash | 10 |
6 | Remember me when logging in doesn't work | 1 |
6 | Club deposit in SMUSA President - acknowledge then cancel causes "undefined" to come out | 1 |
6 | Club claims in SMUSA President - acknowledge then cancel causes "undefined" to come out | 1 |
7 | Updating expenditure account with large values causes program to crash | 10 |
7 | Rejecting claim with long remarks causes program to crash | 10 |
7 | Club and CBD Fin secs are able to add themselves as president | 5 |
8 | Budget request sac can become negative (because they made income more than expenditure) | 5 |
8 | Able to backdate budget to long long time ago (able to budget for 1923) | 1 |
8 | When a user with no role assigned tries to edit profile, the redirection to home page will cause error500 page | 5 |