Difference between revisions of "IS480 Team wiki: 2014T1 Chocolicious Proj Management"
Line 505: | Line 505: | ||
{| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | {| class="wikitable mw-collapsible mw-collapsed" style="width:100%" | ||
|- | |- | ||
− | ! scope="row" colspan=" | + | ! scope="row" colspan="6" | Project Risk |
|- | |- | ||
− | ! style="width:50%"|Possible Risk | + | ! style="width:50%"|Possible Risk || Reason & Implications |
!Probability<br>(1-3) || Effects<br>(1-3) || Priority<br>(P x E) || Strategy | !Probability<br>(1-3) || Effects<br>(1-3) || Priority<br>(P x E) || Strategy | ||
|- | |- | ||
− | |<b>Medical Certificate | + | |<b>Medical Certificate (MC) / Leave of Absence (LOA)</b><br> |
− | + | |<b> Reason</b> | |
+ | <li>Falling sick | ||
+ | <li>Personal reasons | ||
+ | <li>Unforeseen circumstances | ||
+ | <br /> | ||
+ | <br /> | ||
+ | <b> Implications</b> | ||
+ | Allocated work may not be completed on time | ||
|Low (1) | |Low (1) | ||
|Medium (2) | |Medium (2) | ||
|2 | |2 | ||
− | |< | + | |Project Manager to reschedule tasks or reallocate tasks to another member. |
− | + | <br />Buffer days should be included in project schedule to accommodate such situations. | |
+ | |||
+ | |||
|- | |- | ||
− | |<b>Minimal knowledge | + | |<b>Minimal or lack thereof knowledge on <li>accounting-related software/tools<li>frameworks <li>languages </b><br> |
− | + | |<b> Reason</b><br /> Not learned prior to start of project. | |
+ | <br /> | ||
+ | <b> Implications</b><br /> | ||
+ | Additional time will need to be allocated for learning the language and framework | ||
|Medium (2) | |Medium (2) | ||
|Medium (2) | |Medium (2) | ||
|4 | |4 | ||
− | |< | + | |Project Manager to allocate time for collaborative learning for the team. <br /> |
− | + | Lead Developer to organize meetings to facilitate team learning.<br /> | |
+ | <br /> Team to speak with SMUSA accountant. <br /> | ||
+ | |||
+ | |||
|- | |- | ||
− | |<b> | + | |<b>Change of project requirements</b><br> |
− | + | |<b>Reason</b><br /> Current requirements no longer fits client’s needs | |
+ | <br /> | ||
+ | <b>Implications</b><br /> | ||
+ | Delay in project completion date | ||
|Medium (2) | |Medium (2) | ||
− | |Medium ( | + | |Medium (3) |
− | | | + | |6 |
− | |< | + | |Project Manager to adjust project schedule to accommodate the changes.<br /> |
− | + | Business Analyst to update team on the change of requirements.<br /> | |
+ | <br />System Analyst and Quality Assurance Analyst to ensure that team changes codes in accordance to change in requirements without affecting code quality. | ||
+ | |||
+ | |||
|- | |- | ||
− | |<b> | + | |<b>Hardware unavailability</b><br> |
− | + | |<b>Reason</b><br /> Laptop crash | |
+ | <br /> | ||
+ | <b>Implications</b><br /> | ||
+ | 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) | |Medium (2) | ||
− | |Low | + | |Low (3) |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|6 | |6 | ||
− | |< | + | |Project Manager to reschedule tasks or reallocate tasks to another member.<br /> |
− | + | Member may be able to borrow laptop from team members to complete immediate tasks. | |
+ | |||
+ | |||
|- | |- | ||
− | |<b> | + | |<b>Incomplete tasks</b><br> |
− | + | |<b>Reason</b><br /> Unable to code out the function | |
− | + | <br /> | |
− | + | <b>Implications</b><br /> | |
− | + | Deviations from project schedule will affect the whole team | |
− | |<b> | + | |Medium (1) |
− | |||
− | |||
− | |||
− | |||
− | | | ||
|High (3) | |High (3) | ||
|3 | |3 | ||
− | |< | + | |Project Manager to reschedule tasks or reallocate tasks to another member.<br /> |
− | + | <br />Member may be able to borrow laptop from team members to complete immediate tasks. | |
− | + | ||
− | + | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
|<b>Miscommunication</b><br> | |<b>Miscommunication</b><br> | ||
− | + | |<b>Reason</b><br /> The idea was not presented or understood correctly | |
+ | <br /> | ||
+ | <b>Implications</b><br /> | ||
+ | Time spent wrongly on things not required | ||
|Low (1) | |Low (1) | ||
− | | | + | |High (2) |
|2 | |2 | ||
− | | | + | |Business Analyst to ensure that each team member fully understands exactly what he/she is to accomplish.<br /> |
− | + | <br />Project Manager to allocate some time for team member to rectify the mistakes. | |
− | + | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
− | |<b> | + | |<b>Conflicts among team members</b><br> |
− | + | |<b>Reason</b><br /> Team members might have a difference in opinion on how things should be done and unable to solve it on their own | |
+ | <br /> | ||
+ | <b>Implications</b><br /> | ||
+ | Such conflicts impede smooth project flow | ||
|Low (1) | |Low (1) | ||
− | |High ( | + | |High (2) |
− | | | + | |2 |
− | | | + | |Project Manager to arrange meeting for team to come together and talk things out. |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|} | |} | ||
==Metrics== | ==Metrics== |
Revision as of 12:31, 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. |