Difference between revisions of "IS480 Team wiki: 2011T1 Aperture - Main - Project Management - Risk Management - Risk Analysis"
Cgchen.2009 (talk | contribs) |
Cgchen.2009 (talk | contribs) |
||
Line 30: | Line 30: | ||
*Using the team's average velocity in Pivotal Tracker, gauge the number of functionalities able to be completed, and inform client of functionalities which cannot be completed<br /> | *Using the team's average velocity in Pivotal Tracker, gauge the number of functionalities able to be completed, and inform client of functionalities which cannot be completed<br /> | ||
| style="background: #FFFFFF; padding: 0 10px 12px 18px;" valign="top" | | | style="background: #FFFFFF; padding: 0 10px 12px 18px;" valign="top" | | ||
− | + | Despite the re-allocation of manpower, we were not able to finish every single functionality that was given by the client. However, we informed the client and discussed the priorities of the remaining features after midterm, to manage the client's expectations <br /> | |
|- | |- | ||
| style="background: #00AEFF; color: #FFFFFF; padding: 10px 0 10px 20px; font-weight: bold; font-size: 14px; text-indent: 8px; width: 800px;" colspan="6" valign="top" | 3. <i>Resource Risk</i> | | style="background: #00AEFF; color: #FFFFFF; padding: 10px 0 10px 20px; font-weight: bold; font-size: 14px; text-indent: 8px; width: 800px;" colspan="6" valign="top" | 3. <i>Resource Risk</i> | ||
Line 51: | Line 51: | ||
*Review individual members' progress during weekly meetings and reassign tasks between members where necessary.<br /> | *Review individual members' progress during weekly meetings and reassign tasks between members where necessary.<br /> | ||
| style="background: #FFFFFF; padding: 0 10px 12px 18px;" valign="top" | | | style="background: #FFFFFF; padding: 0 10px 12px 18px;" valign="top" | | ||
− | + | We had to re-allocate manpower and play to each other's strengths. So we allowed the lead developer and system analyst to take over the main development work, while the rest of us translated user feedback and client's requirements into mock-ups and system re-designs | |
|- | |- | ||
| style="background: #00AEFF; color: #FFFFFF; padding: 10px 0 10px 20px; font-weight: bold; font-size: 14px; text-indent: 8px; width: 800px;" colspan="6" valign="top" | 4. <i>Technical Risk</i> | | style="background: #00AEFF; color: #FFFFFF; padding: 10px 0 10px 20px; font-weight: bold; font-size: 14px; text-indent: 8px; width: 800px;" colspan="6" valign="top" | 4. <i>Technical Risk</i> | ||
Line 127: | Line 127: | ||
*Have team members to assist the Project Manager in managing the team's progress.<br /> | *Have team members to assist the Project Manager in managing the team's progress.<br /> | ||
| style="background: #FFFEF5; padding: 0 10px 12px 18px;" valign="top" | | | style="background: #FFFEF5; padding: 0 10px 12px 18px;" valign="top" | | ||
− | + | Mitigated. Team members have been assisting the Project Manager to check on the schedule, as well as consistently completing their tasks. <br /> | |
|- | |- | ||
| style="background: #FFFEF5; padding: 0 10px 12px 40px;" valign="top" | | | style="background: #FFFEF5; padding: 0 10px 12px 40px;" valign="top" | |
Revision as of 10:05, 18 November 2011
Contents
Project Management
Risk Management
Risk Analysis - Project Elaboration Phase
Potential Risks Ahead | |||||
1. Scope Risk | |||||
Risk Statement | Risk Rating (Derived) |
Likelihood (High/Med/Low) |
Impact Level (High/Med/Low) |
Mitigation Strategy | Comments |
---|---|---|---|---|---|
|
A |
High |
Medium |
|
Despite the re-allocation of manpower, we were not able to finish every single functionality that was given by the client. However, we informed the client and discussed the priorities of the remaining features after midterm, to manage the client's expectations |
3. Resource Risk | |||||
Risk Statement | Risk Rating (Derived) |
Likelihood (High/Med/Low) |
Impact Level (High/Med/Low) |
Mitigation Strategy | Comments |
|
B |
Medium |
Medium |
|
We had to re-allocate manpower and play to each other's strengths. So we allowed the lead developer and system analyst to take over the main development work, while the rest of us translated user feedback and client's requirements into mock-ups and system re-designs |
4. Technical Risk | |||||
Risk Statement | Risk Rating (Derived) |
Likelihood (High/Med/Low) |
Impact Level (High/Med/Low) |
Mitigation Strategy | Comments |
|
A |
Medium |
High |
|
Currently, there is an issue with the client's PayPal account which needs to be resolved. We will have to wait for the outcome of PayPal's decision before we are able to proceed. |
Resolved Risks | |||||
1. Scope Risk | |||||
Risk Statement | Risk Rating (Derived) |
Likelihood (High/Med/Low) |
Impact Level (High/Med/Low) |
Mitigation Strategy | Comments |
---|---|---|---|---|---|
|
B |
Low |
Low |
|
Mitigated. The paper prototype was very useful in ensuring that we understood the requirements of the client. |
|
A |
Low |
Low |
|
Mitigated. We have prioritized the functions in the client's requirement list, before coming to an agreement with him. |
2. Schedule Risk | |||||
Risk Statement | Risk Rating (Derived) |
Likelihood (High/Med/Low) |
Impact Level (High/Med/Low) |
Mitigation Strategy | Comments |
|
C |
Low |
Low |
|
Mitigated. Team members have been assisting the Project Manager to check on the schedule, as well as consistently completing their tasks. |
|
C |
Low |
Low |
|
Mitigated. We learnt to compromise about how each team prioritizes this project. The Project Manager will continue to ensure that each member completes his tasks |
4. Technical Risk | |||||
Risk Statement | Risk Rating (Derived) |
Likelihood (High/Med/Low) |
Impact Level (High/Med/Low) |
Mitigation Strategy | Comments |
|
A |
Low |
Low |
|
Mitigated. We have allocated time for each member to learn the new technology. In addition, we are able to post questions on online forums when we encounter issues |
|
A |
Low |
Low |
|
Mitigated, as we started developing from scratch. |