View source for IS480 Team wiki: 2011T1 Aperture - Main - Project Management - Risk Management - Project Inception Phase

<div style="width:1000px;">
<font face="century gothic" size="2">

==<div style="background: #00AEFF; padding: 15px; font-weight: bold; line-height: 0.3em"><font color= #FFFFFF>Project Management</font></div>==

<div style="margin-bottom:60px;">
===<span style="color: #797979; padding: 0px 0px 0px 29px;">Risk Management</span>===
<div style="border-left: #797979 solid 12px; padding: 0px 30px 0px 18px; font-family: Arial, Helvetica;">
====Risk Analysis - Project Inception Phase====
{| class="wikitable" cellpadding="15"
|-
| style="background: #00AEFF; color: #FFFFFF; padding: 10px 0 10px 20px; font-weight: bold; font-size: 14px; text-indent: 8px; width: 800px;" colspan="7" valign="top" | 1. &nbsp;&nbsp;&nbsp;<i>Scope Risk</i>
|-
| style="background: #00AEFF; color: #FFFFFF; font-weight: bold; text-indent: 8px; padding-left: 20px;" rowspan="4" valign="top" | 
! style="background: #797979; color: #FFFFFF; text-align: center; width: 24%;" | Risk Statement
! style="background: #797979; color: #FFFFFF; text-align: center; width: 9%;" | Risk Rating<br /><small><i>(Derived)</i></small>
! style="background: #797979; color: #FFFFFF; text-align: center; width: 9%;" | Likelihood<br /><small><i>(High/Med/Low)</i></small>
! style="background: #797979; color: #FFFFFF; text-align: center; width: 10%;" | Impact Level<br /><small><i>(High/Med/Low)</i></small>
! style="background: #797979; color: #FFFFFF; text-align: center; width: 24%;" | Mitigation Strategy
! style="background: #797979; color: #FFFFFF; text-align: center; width: 24%;" | Comments
|-
| style="background: #FFFEF5; padding: 0 10px 12px 20px;" valign="top" | 
*<b>Not being able to complete all the additional functionalities, on top of the basic functionalities.</b>
| style="background: #FFFEF5; padding: 5px 18px 12px 18px; text-align: center;" valign="top" | A<br />
| style="background: #FFFEF5; padding: 5px 10px 12px 18px; color: red;" valign="top" | High<br />
| style="background: #FFFEF5; padding: 5px 10px 12px 18px; color: orange;" valign="top" | Medium<br />
| style="background: #FFFEF5; padding: 0 10px 12px 18px;" valign="top" | 
*Re-allocate manpower to help speed up development process.
*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: #FFFEF5; padding: 0 10px 12px 18px;" valign="top" | 
Partially mitigated. The client understands that the scope of the project has increased. If we are unable to complete all the features, we will discuss it with the client. <br />
|-
| style="background: #FFFFFF; padding: 0 10px 12px 20px;" valign="top" | 
*<b>Dynamic (<i>undefined</i>) requirement list.</b>
| style="background: #FFFFFF; padding: 5px 18px 12px 18px; text-align: center;" valign="top" | B<br />
| style="background: #FFFFFF; padding: 5px 10px 12px 18px; color: orange;" valign="top" | Medium<br />
| style="background: #FFFFFF; padding: 5px 10px 12px 18px; color: orange;" valign="top" | Medium<br />
| style="background: #FFFFFF; padding: 0 10px 12px 18px;" valign="top" | 
*Develop paper prototypes to ensure that the client and the team agrees on the outcome.
*Divide huge tasks into smaller features that can be pushed out on a weekly basis.<br />
| style="background: #FFFFFF; padding: 0 10px 12px 18px;" valign="top" | 
Mitigated. The paper prototype was very useful in ensuring that we understood the requirements of the client.<br />
|-
| style="background: #FFFEF5; padding: 0 10px 12px 20px;" valign="top" | 
*<b>Overpromising new features to client.</b>
| style="background: #FFFEF5; padding: 5px 18px 12px 18px; text-align: center;" valign="top" | A<br />
| style="background: #FFFEF5; padding: 5px 10px 12px 18px; color: orange;" valign="top" | Medium<br />
| style="background: #FFFEF5; padding: 5px 10px 12px 18px; color: red;" valign="top" | High<br />
| style="background: #FFFEF5; padding: 0 10px 12px 18px;" valign="top" | 
*Prioritize list of features in Pivotal Tracker and get client to confirm.<br />
| style="background: #FFFEF5; padding: 0 10px 12px 18px;" valign="top" | 
Mitigated. We have prioritized the functions and agreed with the client how we will progress. <br />
|}

{| class="wikitable" cellpadding="15"
|-
| style="background: #00AEFF; color: #FFFFFF; padding: 10px 0 10px 20px; font-weight: bold; font-size: 14px; text-indent: 8px; width: 800px;" colspan="7" valign="top" | 2. &nbsp;&nbsp;&nbsp;<i>Schedule Risk</i>
|-
| style="background: #00AEFF; color: #FFFFFF; font-weight: bold; text-indent: 8px; padding-left: 20px;" rowspan="3" valign="top" | 
! style="background: #797979; color: #FFFFFF; text-align: center; width: 24%;" | Risk Statement
! style="background: #797979; color: #FFFFFF; text-align: center; width: 9%;" | Risk Rating<br /><small><i>(Derived)</i></small>
! style="background: #797979; color: #FFFFFF; text-align: center; width: 9%;" | Likelihood<br /><small><i>(High/Med/Low)</i></small>
! style="background: #797979; color: #FFFFFF; text-align: center; width: 10%;" | Impact Level<br /><small><i>(High/Med/Low)</i></small>
! style="background: #797979; color: #FFFFFF; text-align: center; width: 24%;" | Mitigation Strategy
! style="background: #797979; color: #FFFFFF; text-align: center; width: 24%;" | Comments
|-
| style="background: #FFFEF5; padding: 0 10px 12px 20px;" valign="top" | 
*<b>Over-management / Under-management.</b>
| style="background: #FFFEF5; padding: 5px 18px 12px 18px; text-align: center;" valign="top" | C<br />
| style="background: #FFFEF5; padding: 5px 10px 12px 18px; color: green;" valign="top" | Low<br />
| style="background: #FFFEF5; padding: 5px 10px 12px 18px; color: green;" valign="top" | Low<br />
| style="background: #FFFEF5; padding: 0 10px 12px 18px;" valign="top" | 
*Conduct honest and objective peer reviews.
*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" | 
Partially mitigated. Team members have been assisting the Project Manager to check on the schedule, as well as consistently completing their tasks. <br />
|-
| style="background: #FFFFFF; padding: 0 10px 12px 20px;" valign="top" | 
*<b>Different priorities of team members.</b>
| style="background: #FFFFFF; padding: 5px 18px 12px 18px; text-align: center;" valign="top" | C<br />
| style="background: #FFFFFF; padding: 5px 10px 12px 18px; color: orange;" valign="top" | Medium<br />
| style="background: #FFFFFF; padding: 5px 10px 12px 18px; color: green;" valign="top" | Low<br />
| style="background: #FFFFFF; padding: 0 10px 12px 18px;" valign="top" | 
*Communicate and align individual members' priorities and project priorities.
*Set clear tasks together as a team every week.<br />
| style="background: #FFFFFF; padding: 0 10px 12px 18px;" valign="top" | 
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<br />
|}

{| class="wikitable" cellpadding="15"
|-
| style="background: #00AEFF; color: #FFFFFF; padding: 10px 0 10px 20px; font-weight: bold; font-size: 14px; text-indent: 8px; width: 800px;" colspan="7" valign="top" | 3. &nbsp;&nbsp;&nbsp;<i>Resource Risk</i>
|-
| style="background: #00AEFF; color: #FFFFFF; font-weight: bold; text-indent: 8px; padding-left: 20px;" rowspan="3" valign="top" | 
! style="background: #797979; color: #FFFFFF; text-align: center; width: 24%;" | Risk Statement
! style="background: #797979; color: #FFFFFF; text-align: center; width: 9%;" | Risk Rating<br /><small><i>(Derived)</i></small>
! style="background: #797979; color: #FFFFFF; text-align: center; width: 9%;" | Likelihood<br /><small><i>(High/Med/Low)</i></small>
! style="background: #797979; color: #FFFFFF; text-align: center; width: 10%;" | Impact Level<br /><small><i>(High/Med/Low)</i></small>
! style="background: #797979; color: #FFFFFF; text-align: center; width: 24%;" | Mitigation Strategy
! style="background: #797979; color: #FFFFFF; text-align: center; width: 24%;" | Comments
|-
| style="background: #FFFEF5; padding: 0 10px 12px 20px;" valign="top" | 
*<b>Unavailability of online service resources such as downtime of Google App Engine (GAE).</b>
| style="background: #FFFEF5; padding: 5px 18px 12px 18px; text-align: center;" valign="top" | A<br />
| style="background: #FFFEF5; padding: 5px 10px 12px 18px; color: orange;" valign="top" | Medium<br />
| style="background: #FFFEF5; padding: 5px 10px 12px 18px; color: red;" valign="top" | High<br />
| style="background: #FFFEF5; padding: 0 10px 12px 18px;" valign="top" | 
*Focus the main bulk of code development on local developer's machine (<i>localhost</i>).
*Shift the load of site-testing onto online resources, to better capitalize on resource capabilities such as load-testing on Cloud Services.<br />
| style="background: #FFFEF5; padding: 0 10px 12px 18px;" valign="top" | 
<br />
|-
| style="background: #FFFFFF; padding: 0 10px 12px 20px;" valign="top" | 
*<b>Overreliance on skilled / experienced team members.</b>
| style="background: #FFFFFF; padding: 5px 18px 12px 18px; text-align: center;" valign="top" | B<br />
| style="background: #FFFFFF; padding: 5px 10px 12px 18px; color: orange;" valign="top" | Medium<br />
| style="background: #FFFFFF; padding: 5px 10px 12px 18px; color: orange;" valign="top" | Medium<br />
| style="background: #FFFFFF; padding: 0 10px 12px 18px;" valign="top" | 
*Allocate tasks according to each member's strength and assigned job scope(s).
*Break down tasks into smaller tasks so that they are more easily manageable.
*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" | 
Some of the risk has been mitigated. If we are stuck with some technical difficulties, we will post questions on forums such as Google groups, instead of relying on one person to complete the task for us. However, if we are behind schedule, we will have to re-allocate manpower.  
|}

{| class="wikitable" cellpadding="15"
|-
| style="background: #00AEFF; color: #FFFFFF; padding: 10px 0 10px 20px; font-weight: bold; font-size: 14px; text-indent: 8px; width: 800px;" colspan="7" valign="top" | 4. &nbsp;&nbsp;&nbsp;<i>Technical Risk</i>
|-
| style="background: #00AEFF; color: #FFFFFF; font-weight: bold; text-indent: 8px; padding-left: 20px;" rowspan="4" valign="top" | 
! style="background: #797979; color: #FFFFFF; text-align: center; width: 24%;" | Risk Statement
! style="background: #797979; color: #FFFFFF; text-align: center; width: 9%;" | Risk Rating<br /><small><i>(Derived)</i></small>
! style="background: #797979; color: #FFFFFF; text-align: center; width: 9%;" | Likelihood<br /><small><i>(High/Med/Low)</i></small>
! style="background: #797979; color: #FFFFFF; text-align: center; width: 10%;" | Impact Level<br /><small><i>(High/Med/Low)</i></small>
! style="background: #797979; color: #FFFFFF; text-align: center; width: 24%;" | Mitigation Strategy
! style="background: #797979; color: #FFFFFF; text-align: center; width: 24%;" | Comments
|-
| style="background: #FFFEF5; padding: 0 10px 12px 20px;" valign="top" | 
*<b>PayPal implementation.</b>
| style="background: #FFFEF5; padding: 5px 18px 12px 18px; text-align: center;" valign="top" | A<br />
| style="background: #FFFEF5; padding: 5px 10px 12px 18px; color: orange;" valign="top" | Medium<br />
| style="background: #FFFEF5; padding: 5px 10px 12px 18px; color: red;" valign="top" | High<br />
| style="background: #FFFEF5; padding: 0 10px 12px 18px;" valign="top" | 
*Complete the basic functionalities required for payments and deploy the application to live server, while the client liaise with PayPal,<br />
| style="background: #FFFEF5; padding: 0 10px 12px 18px;" valign="top" | 
Currently, due to the large amount of money transactions going through PayPal, PayPal has to verify that the client's transactions are legit, and thus we will have to wait for them to resolve the matter before verifying our website. <br />
|-
| style="background: #FFFFFF; padding: 0 10px 12px 20px;" valign="top" | 
*<b>Working with new technology and tools.</b>
| style="background: #FFFFFF; padding: 5px 18px 12px 18px; text-align: center;" valign="top" | A<br />
| style="background: #FFFFFF; padding: 5px 10px 12px 18px; color: red;" valign="top" | High<br />
| style="background: #FFFFFF; padding: 5px 10px 12px 18px; color: red;" valign="top" | High<br />
| style="background: #FFFFFF; padding: 0 10px 12px 18px;" valign="top" | 
*Plan the project to allow sufficient time for the team to familiarize themselves with new technology and tools.
*Arrange mini-group learning / sharing sessions, to help improve members' knowledge on new technology and tools.<br />
| style="background: #FFFFFF; padding: 0 10px 12px 18px;" valign="top" | 
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<br />
|-
| style="background: #FFFEF5; padding: 0 10px 12px 20px;" valign="top" | 
*<b>Application contains bugs after handover.</b>
| style="background: #FFFEF5; padding: 5px 18px 12px 18px; text-align: center;" valign="top" | A<br />
| style="background: #FFFEF5; padding: 5px 10px 12px 18px; color: red;" valign="top" | High<br />
| style="background: #FFFEF5; padding: 5px 10px 12px 18px; color: red;" valign="top" | High<br />
| style="background: #FFFEF5; padding: 0 10px 12px 18px;" valign="top" |
*Have mini-test sessions on different modules of project, especially when a new feature is rolled out.
*Allocate a few weeks post-development for the lead developer to test and clean up the codes.<br />
| style="background: #FFFEF5; padding: 0 10px 12px 18px;" valign="top" | 
Mitigated, as we started developing from scratch.<br />
|}

</div>
</div>

==<div style="background: #EC008C; padding: 15px; font-weight: bold; line-height: 0.3em"><font color= #FFFFFF>Project Sitemap</font></div>==
<div style="margin-bottom:40px;">

<span style="color: #EC008C; border-left: #EC008C solid 12px; padding: 0px 30px 0px 38px; font-size:15px; font-weight: bold;">[[IS480 Team wiki: 2011T1 Aperture|<span style="color: #EC008C;"><small>BACK TO</small> <span style="color: #797979;">&oplus;</span> [ <small>TEAM Aperture</small> | <small>MAIN PAGE</small> ]</span>]]</span><br />
<span style="color: #EC008C; border-left: #EC008C solid 12px; padding: 0px 30px 0px 38px; font-size:15px; font-weight: bold;">
[[IS480 Team wiki: 2011T1 Aperture - Main - Project Management - Risk Management - Risk Analysis|<span style="color: #EC008C;"><small>HEAD TO</small> <span style="color: #797979;">&oplus;</span> [ <small>TEAM Aperture</small> | <small>RISK ANALYSIS PAGE</small> ]</span>]]</span><br />
<span style="color: #EC008C; border-left: #EC008C solid 12px; padding: 0px 30px 0px 38px; font-size:15px; font-weight: bold;">[[IS480 Team wiki: 2011T1 Aperture - Main - Sitemap|<span style="color: #EC008C;"><small>HEAD TO</small> <span style="color: #797979;">&oplus;</span> [ <small>TEAM Aperture</small> | <small>SITEMAP PAGE</small> ]</span>]]</span>

</div>