1. Poornima Holla

8. Risk Assessment Risk Assessment

18. Risk Control Risk Control

26. Example Sl. # Risk Element Risk Mitigation actions 1 Wrong algorithm, too many revisions in the requirement specification documents, and/or document versions not controlled properly. Review requirement specification documents properly by the domain expert, before baseline and maintain the version control. 2 Generation of output taking unusually long time (beyond the time the algorithm is expected to take). For every feature, make a reasonable and realistic estimate of the time needed to generate output. Get the code tested for any possible bugs (redundancies, infinite loops, lack of or inaccurate initialization, etc.).

27. Sl. # Risk Elements Risk Mitigation actions 3 Existing feature(s) becoming inaccessible or getting disabled without apparent reason, on adding a new feature. Check for all possible dependencies with existing features before or while coding. Get the code/product tested at every stage of development (unit, integrated, alpha, beta, etc.). 4 Output format, options, dialog box structure, menu structure, look-and-feel, etc. being inconsistent with existing features. Note the output format, options, dialog box structure, command syntax and usage, menu structure, look-and-feel, etc. of existing features. Adopt a style that is common. 5 Key staff leaving the organization at critical times in the project. Assign more than one person to work on a feature.

28. Sl. # Risk Elements Risk Mitigation actions 1 Tester not having knowledge of product Thorough training need to be given 2 Test cases are not ready Allocate test engineer in the beginning of the project.