HeaderSIS.jpg

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

From IS480
Revision as of 10:53, 26 September 2011 by Chchai.2009 (talk | contribs) (→‎Project Sitemap)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Project Management

Risk Management

Risk Analysis - Project Inception Phase

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

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.

  • Dynamic (undefined) requirement list.
B
Medium
Medium
  • 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
High
  • Prioritize list of features in Pivotal Tracker and get client to confirm.

Mitigated. We have prioritized the functions and agreed with the client how we will progress.

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.

Partially 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
  • 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

3.    Resource Risk
Risk Statement Risk Rating
(Derived)
Likelihood
(High/Med/Low)
Impact Level
(High/Med/Low)
Mitigation Strategy Comments
  • Unavailability of online service resources such as downtime of Google App Engine (GAE).
A
Medium
High
  • Focus the main bulk of code development on local developer's machine (localhost).
  • Shift the load of site-testing onto online resources, to better capitalize on resource capabilities such as load-testing on Cloud Services.


  • 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.

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.

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
  • Complete the basic functionalities required for payments and deploy the application to live server, while the client liaise with PayPal,

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.

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