Indefinable requirements 1 = <10 per cent Refer to the Project Management Plan, (Known unknowns) specifically the Work Breakdown 2 = 20 per cent Structure and Project Schedule to What percentage of tasks identify inter-dependant tasks and 3 = 30 per cent cannot be fully defined until calculate accordingly. the completion of previous 4 = 40 per cent tasks? 5 = >40 per cent Note: These are tasks that may be understood but cannot be documented in detail due to dependency on results from a previous task. To what extent are the 1 = All requirements are Are any requirements uncertain or are project’s requirements clear, clear, complete, and assumed requirements excluded? completed, and communicated. communicated? 3 = Up to 10 per cent of Note: If all requirements have not total requirements are been defined at the time of the not complete or are assessment, then use the upcoming undocumented. as the basis for the response, else 5 = More than 10 per cent use the entire project as the basis. of total requirements are not complete or are unclear. How many of the following 1 = All of the project Does the current project information project characteristics are requirement adequately represent the expected to remain stable? characteristics are requirements? If some of the expected to remain requirements are expected to change quality stable. due to incomplete or uncertain information, then some of the project functionality 2 = Five of the six project characteristics will inevitably be requirement considered unstable. schedule characteristics are expected to remain Typically, for IT-E projects, schedule, integration stable. design, and testing is expected to design remain stable. 3 = Four of the six project testing requirement characteristics are expected to remain Note: Project characteristics stable. should be expected to
Indefinable requirements (Known unknowns) What percentage of tasks cannot be fully defined until the completion of previous tasks? Note: These are tasks that may be understood but cannot be documented in detail due to dependency on results from a previous task. 1 = <10 per cent 2 = 20 per cent 3 = 30 per cent 4 = 40 per cent 5 = >40 per cent Refer to the Project Management Plan, specifically the Work Breakdown Structure and Project Schedule to identify inter-dependant tasks and calculate accordingly. To what extent are the project’s requirements clear, completed, and communicated? 1 = All requirements are clear, complete, and communicated. 3 = Up to 10 per cent of total requirements are not complete or are undocumented. 5 = More than 10 per cent of total requirements are not complete or are unclear. Are any requirements uncertain or are assumed requirements excluded? Note: If all requirements have not been defined at the time of the assessment, then use the upcoming as the basis for the response, else use the entire project as the basis. How many of the following project characteristics are expected to remain stable? quality functionality schedule integration design testing Note: Project characteristics should be expected to 1 = All of the project requirement characteristics are expected to remain stable. 2 = Five of the six project requirement characteristics are expected to remain stable. 3 = Four of the six project requirement characteristics are expected to remain stable. Does the current project information adequately represent the requirements? If some of the requirements are expected to change due to incomplete or uncertain information, then some of the project characteristics will inevitably be considered unstable. Typically, for IT-E projects, schedule, design, and testing is expected to remain stable.
risqueproj-riskmnl-eng.docx