Difference between revisions of "IS480 Team wiki: 2014T1 Chocolicious Proj Management"
Line 603: | Line 603: | ||
|2 | |2 | ||
|Project Manager to arrange meeting for team to come together and talk things out. | |Project Manager to arrange meeting for team to come together and talk things out. | ||
+ | |} | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | {| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | ||
+ | |- | ||
+ | ! scope="row" colspan="6" | Technical Risk | ||
+ | |- | ||
+ | ! style="width:50%"|Possible Risk || Reason & Implications | ||
+ | !Probability<br>(1-3) || Effects<br>(1-3) || Priority<br>(P x E) || Strategy | ||
+ | |- | ||
+ | |<b>Defective components</b><br> | ||
+ | |<b> Reason</b> | ||
+ | Faulty parts in machine | ||
+ | <br /> | ||
+ | <br /> | ||
+ | <b> Implications</b> | ||
+ | Corrupted projects files resulting in much time wastage | ||
+ | |Low (1) | ||
+ | |Medium (3) | ||
+ | |3 | ||
+ | |Team member to resolve problem on individual machine. | ||
+ | <br />Systems Analyst to ensure that shared project version has not been corrupted. | ||
+ | Project Manager to assign team member to provide assistance if need be.<br /> | ||
+ | |||
+ | |||
+ | |- | ||
+ | |<b>Data Loss</b><br> | ||
+ | |<b>Reason</b><br /> Hardware used to store data might be corrupted | ||
+ | <br /> | ||
+ | <b>Implications</b><br /> | ||
+ | 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. <br /> | ||
+ | <br />Project Manager to assign team member to provide assistance if need be. | ||
+ | |||
+ | |} | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | {| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | ||
+ | |- | ||
+ | ! scope="row" colspan="6" | Business Risk | ||
+ | ! style="width:50%"|Possible Risk || Reason & Implications | ||
+ | !Probability<br>(1-3) || Effects<br>(1-3) || Priority<br>(P x E) || Strategy | ||
+ | |- | ||
+ | |<b>User-unfriendly system</b><br> | ||
+ | |<b> Reason</b> | ||
+ | Non-technical users may find the system user-unfriendly | ||
+ | <br /> | ||
+ | <br /> | ||
+ | <b> Implications</b> | ||
+ | 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. | ||
+ | <br />Project Manager to arrange meeting with client and personally teach him/her. | ||
|} | |} | ||
==Metrics== | ==Metrics== |
Revision as of 13:29, 17 June 2014
|
Our Team
Time Line
Schedule
Planned | Actual | ||||||
---|---|---|---|---|---|---|---|
Iter | Tasks | Milestone | Start | End | 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
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 |
Medical Certificate (MC) / Leave of Absence (LOA) |
Reason
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.
|
Minimal or lack thereof knowledge on |
Reason Not learned prior to start of project.
|
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.
|
Change of project requirements |
Reason Current requirements no longer fits client’s needs
|
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.
|
Hardware unavailability |
Reason Laptop crash
|
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
|
Medium (1) | High (3) | 3 | Project Manager to reschedule tasks or reallocate tasks to another member.
|
Miscommunication |
Reason The idea was not presented or understood correctly
|
Low (1) | High (2) | 2 | Business Analyst to ensure that each team member fully understands exactly what he/she is to accomplish.
|
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
|
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
|
Low (1) | Medium (3) | 3 | Team member to resolve problem on individual machine.
|
Data Loss |
Reason Hardware used to store data might be corrupted
|
Low (1) | High (3) | 3 | Member to immediately revert back to previous version in repository and continue with work.
|
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
|
Low (2) | Medium (3) | 6 | Business Analyst and Quality Assurance Analyst to ensure that user guide cater to non-technical users.
|