HeaderSIS.jpg

Difference between revisions of "IS480 Team wiki: 2012T2 DaDa Achievers Project Management Project Risks"

From IS480
Jump to navigation Jump to search
Line 70: Line 70:
 
| style="text-align: center;" | Low
 
| style="text-align: center;" | Low
 
| style="text-align: center;" | Conduct thorough analysis and provide a concise solution. Walk client through the needs for such changes.  
 
| style="text-align: center;" | Conduct thorough analysis and provide a concise solution. Walk client through the needs for such changes.  
| style="text-align: center;" | '''Controlled''' <br> We have met up with the client several times to review the proposed solution and changes. However, due to the extensive changes, the client has chosen to revert to the old on-site checkout process
+
| style="text-align: center;" | '''Controlled''' <br> We have met up with the client several times to review the proposed solution and changes.  
 
|-
 
|-
 
| style="text-align: center;" | Project Management  
 
| style="text-align: center;" | Project Management  

Revision as of 02:54, 19 April 2013


Home Project Overview Project Management Project Documentation Project Progress Summary Reflections
Project Schedule Project Metrics Project Risks Technologies Used


Project Risks

Classification Risk Description Impact Probability Mitigation Strategy and Triggers (if applicable) Status, and Remarks (if any)
Technology Unfamiliarity of Flash technology for development of the Ring Customization tool High High Allocate time for adequate learning as well as approaching people with relevant experience for guidance. New Mitigation Strategy:
The team discussed the priority of this feature with our client and chose to shift towards a jQuery-based tool
Technical & Learning Risk Delay of prototype development due to technical challenge High Medium Trigger: Schedule Delay
Initiate research on any technologies that would be easier to implement, and if possible, produce a prototype to confirm the technology switch.
Controlled
The team plans to firm up technology decisions via working prototypes by week 2.
Technology Over-reliance on 3rd Party API such as PhoneGap and E-nets High Medium Conduct proper research and seek alternatives Followed Mitigation Strategy:
The team implemented PayPal instead of E-NETS
Project Management Client is resistant to change of business processes and adoption of new technologies Medium Low Conduct thorough analysis and provide a concise solution. Walk client through the needs for such changes. Controlled
We have met up with the client several times to review the proposed solution and changes.
Project Management Scope creep: Client requests to add on functions above and beyond what was agreed upon Medium Medium Perform thorough requirements analysis and create a baseline. When change is required, PM will meet with the team and compare against baseline and project schedule to see if change can be allowed. Risk occurred.
Post UAT, client has brought up numerous changes and adjustments that were necessary. They also highlighted minor cosmetic errors. The team has since made most of the changes requested at the expense of buffer time
Resolved Risks