HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2011T1 Aperture - Main - Project Management - Risk Management - Risk Analysis"

From IS480
Jump to navigation Jump to search
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" |  
Partially mitigated. As we are building the application from scratch, we have discussed with the client and came up with a prioritized list of functionalities to complete. <br />
+
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. &nbsp;&nbsp;&nbsp;<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. &nbsp;&nbsp;&nbsp;<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" |  
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.  
+
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. &nbsp;&nbsp;&nbsp;<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. &nbsp;&nbsp;&nbsp;<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" |  
Partially mitigated. Team members have been assisting the Project Manager to check on the schedule, as well as consistently completing their tasks. <br />
+
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

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
  • Not being able to complete all the additional functionalities, on top of the basic functionalities.
A
High
Medium
  • 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

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
  • Overreliance on skilled / experienced team members.
B
Medium
Medium
  • 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.

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
  • PayPal implementation.
A
Medium
High
  • Create a separate live PayPal account for Pivotal Expert if we are unable to use the client's account for Pivotal Expert.

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
  • Dynamic (undefined) requirement list.
B
Medium
Low
Medium
Low
  • 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.

Mitigated. The paper prototype was very useful in ensuring that we understood the requirements of the client.

  • Overpromising new features to client.
A
Medium
Low
High
Low
  • Prioritize list of features in Pivotal Tracker and get client to confirm.

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
  • Over-management / Under-management.
C
Low
Low
  • Conduct honest and objective peer reviews.
  • Have team members to assist the Project Manager in managing the team's progress.

Mitigated. Team members have been assisting the Project Manager to check on the schedule, as well as consistently completing their tasks.

  • Different priorities of team members.
C
Medium
Low
Low
  • Communicate and align individual members' priorities and project priorities.
  • Set clear tasks together as a team every week.

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
  • Working with new technology and tools.
A
High
Low
High
Low
  • 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.

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

  • Application contains bugs after handover.
A
High
Low
High
Low
  • 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.

Mitigated, as we started developing from scratch.


Project Sitemap