HeaderSIS.jpg

IS480 Team wiki: 2010T2 Fission1:Project Risk

From IS480
Jump to navigation Jump to search


Project Risks

S/N Risk Statement Likelihood (H/M/L) Impact (H/M/L) Level Mitigation Strategy
01 Client changes requirements set list
L
M
C
  • Keep good documentation
  • Carefully evaluate impact and prepare to negotiate whether to formally include into project scope or put into Experimental
02 New code breaks current set of functionalities
M
H
B
  • Patch modules instead of modifying deployed code
  • Separate functions into different patch files to better isolate errors


03 Non-academic commitments interfering with development process
M
M
B
  • Institute a fixed FYP-only day
  • Assign primary-secondary partners for features and functionalities


04 The only member is fluent with Silverlight might hit un-fixable problems
L
M
C
  • Keep Silverlight features simple
  • Start training another member to use Silverlight