IS480 Team wiki: 2012T1 One-hit Wonder MT Team Reflection

From IS480
Revision as of 11:51, 8 October 2012 by Laymian.koh.2009 (talk | contribs)
Jump to navigation Jump to search

Undo-icon.png Main Wiki

HomeOHW.png Home

Calendar 2 icon&48.png Project Management

Chart line icon&24.png Project Metrics

20px‎ Technical Complexity

Users24.png Usability Studies

TeamRef White.png Team Reflection

Learning Outcome
No. Type of Risk Risk Statement Likelihood (H/M/L) Impact Mitigation Strategy / Contingency Plan
Schedule Risk
1 Technical Schedule. Team members are busy with school work High
Plan ahead and make sure that all team members are comfortable with the work load and free to meet on the dates scheduled. Team members to encourage each other and make extra effort to accommodate to each other and keep in pace with the schedule. Set weekly compulsory meeting dates.
Scope Risk
2 Internal Project scope is too big Medium High
  • Discuss with clients and supervisor on our scope
  • Priortise the more important functions that can value-add our application
Technical Risk
3 Technical Search function. Team is unfamiliar with the implementation techniques. Medium High
  • Set aside time for exploration of techniques
  • Insert buffer for this implementation
4 Technical Instant resume template. Difficult and time-consuming to implement because need to create CSS from scratch. Medium Medium
  • Scheduled for early implementation to prevent delay
  • Include buffer time for this implementation
5 Technical Deployment. Deploying to client server may affect the functioning of certain parts of the application. Medium High Always deploy in advance (1 week before) & test run the application.
Individual Reflection
Team Reflection OHW.png