Difference between revisions of "IS480 Team wiki: 2014T1 Chocolicious Proj Management"
Line 144: | Line 144: | ||
<center> | <center> | ||
{| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | {| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | ||
− | ! scope="row" colspan="4" | | + | ! scope="row" colspan="4" | Deployment |
|- | |- | ||
! Users || Claims || Accounts || Budgeting | ! Users || Claims || Accounts || Budgeting | ||
Line 198: | Line 198: | ||
<center> | <center> | ||
{| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | {| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | ||
− | ! scope="row" colspan="4" | | + | ! scope="row" colspan="4" | Deployment |
|- | |- | ||
! Users || Claims || Accounts || Budgeting | ! Users || Claims || Accounts || Budgeting | ||
Line 255: | Line 255: | ||
<center> | <center> | ||
{| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | {| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | ||
− | ! scope="row" colspan="4" | | + | ! scope="row" colspan="4" | Deployment |
|- | |- | ||
! Users || Claims || Accounts || Budgeting | ! Users || Claims || Accounts || Budgeting | ||
Line 325: | Line 325: | ||
<center> | <center> | ||
{| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | {| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | ||
− | ! scope="row" colspan="4" | | + | ! scope="row" colspan="4" | Deployment |
|- | |- | ||
! Users || Claims || Accounts || Budgeting | ! Users || Claims || Accounts || Budgeting | ||
Line 390: | Line 390: | ||
<center> | <center> | ||
{| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | {| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | ||
− | ! scope="row" colspan="4" | | + | ! scope="row" colspan="4" | Deployment |
|- | |- | ||
! Users || Claims || Accounts || Budgeting | ! Users || Claims || Accounts || Budgeting | ||
Line 463: | Line 463: | ||
<center> | <center> | ||
{| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | {| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | ||
− | ! scope="row" colspan="4" | | + | ! scope="row" colspan="4" | Deployment |
|- | |- | ||
! Users || Claims || Accounts || Budgeting | ! Users || Claims || Accounts || Budgeting | ||
Line 548: | Line 548: | ||
<center> | <center> | ||
{| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | {| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | ||
− | ! scope="row" colspan="4" | | + | ! scope="row" colspan="4" | Deployment |
|- | |- | ||
! Users || Claims || Accounts || Budgeting | ! Users || Claims || Accounts || Budgeting | ||
Line 640: | Line 640: | ||
<center> | <center> | ||
{| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | {| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | ||
− | ! scope="row" colspan="4" | | + | ! scope="row" colspan="4" | Deployment |
|- | |- | ||
! Users || Claims || Accounts || Budgeting | ! Users || Claims || Accounts || Budgeting |
Revision as of 09:57, 22 July 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.
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
Proposal Feedback (Actions)
|
||||||||||||||||
4 | Management
Coding Tasks
Testing
Documentation
|
||||||||||||||||
5 | Management
Coding Tasks
Testing
Documentation
|
14 Aug 2014 |
|||||||||||||||
6 | Management
Coding Tasks
Testing
Documentation
|
||||||||||||||||
7 | Management
Coding Tasks
Testing
Documentation
|
||||||||||||||||
8 | Management
Coding Tasks
Testing
Documentation
|
||||||||||||||||
9 |
Mid term preparation Management
Coding Tasks
Testing
Documentation
|
10 Oct 2014 |
|||||||||||||||
10 | Management
Coding Tasks
Testing
Documentation
|
||||||||||||||||
11 | Management
Coding Tasks
Testing
Documentation
|
||||||||||||||||
12 |
Prepare for Poster Day Management
Coding Tasks
Testing
Documentation
|
10 Nov 2014 |
|||||||||||||||
13 |
Prepare for Final Presentation Management
Testing
Documentation
|
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. |
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!!!
|
Iteration | Planned | Duration | Actual | Duration | Score | Remarks | ||
---|---|---|---|---|---|---|---|---|
Start Date | End Date | Start Date | End Date | |||||
1 | 23-May-14 | 12-Jun-14 | 20 | 23-May-14 | 12-Jun-14 | 20 | 1 | |
2 | 13-Jun-14 | 26-Jun-14 | 13 | 13-May-14 | 26-Jun-14 | 13 | 1 | |
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 |
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. |