5 1 Collect Requirements The process of defining

5. 1 Collect Requirements • The process of defining and documenting the needs of stakeholders • Encompasses the requirements related to the specific characteristics of any end products being delivered by the project • Large projects will often define the requirements at a high level during this process and then allow for a more detailed requirements definition process at the beginning of project execution • Relates to project success measures • Occurs during Planning Monitor Initiation Planning Execution Close Control Adapted from PMBOK 4 th Edition BSBPMG 502 A Manage Project Scope

5. 1 Collect Requirements • Inputs to Collect Requirements ü Project Charter ü Stakeholder needs and expectations ü Rough specifications • Tools and techniques to Collect Requirements Questionaries Brainstorming Focus groups Ranking Interviews Surveys Observation Research Mind Mapping Workshops Prototype Adapted from PMBOK 4 th Edition BSBPMG 502 A Manage Project Scope

5. 1 Collect Requirements • Common requirements documentation includes – ü Objectives and success measures ü Functional requirements – how an end product must perform ü Non functional requirements – not related to product performance, could include optional characteristics, cosmetic details and other organisational requirements ü Quality requirements ü Acceptance criteria ü Support and training requirements ü Assumptions and constraints Monitor Initiation Planning Execution Close Control Adapted from PMBOK 4 th Edition BSBPMG 502 A Manage Project Scope

5. 1 Collect Requirements • Outputs of this process include – ü Requirements documentation as per previous slide ü Requirements Management Plan (advanced concept, often applied to large Information Technology, Defence and Engineering projects) – Detailed plan of how the requirements will be planned, tracked and reported – Especially important where the project is large enough to have a Requirements Workstream or Sub-Project ü Requirements Traceability Matrix (advanced concept, often applied to large Information Technology, Defence and Engineering projects) – Links requirements to their origin in order to trace them through the project lifecycle – Can be linked to objectives, high level requirements, testing Adapted from PMBOK 4 th Edition BSBPMG 502 A Manage Project Scope