5 2 Collect Requirements The process of determining

  • Slides: 6
Download presentation
5. 2 Collect Requirements The process of determining, documenting and managing stakeholder needs and

5. 2 Collect Requirements The process of determining, documenting and managing stakeholder needs and requirements to meet project objectives Includes both product and project scope. Success is reliance on active stakeholder involvement. Occurs during Planning Monitor Initiation Planning Execution Close Control Adapted from PMBOK 5 th Edition

5. 2 Collect Requirements: quantified and documented needs and expectations of stakeholders. These need

5. 2 Collect Requirements: quantified and documented needs and expectations of stakeholders. These need to be detailed to enable control. 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. Monitor Initiation Planning Execution Close Control Adapted from PMBOK 5 th Edition

5. 2 Collect Requirements Business Stakeholder Solution Transition Project Quality Requirements documentation

5. 2 Collect Requirements Business Stakeholder Solution Transition Project Quality Requirements documentation

5. 2 Collect Requirements Inputs to Collect Requirements ü Scope management plan ü Requirements

5. 2 Collect Requirements Inputs to Collect Requirements ü Scope management plan ü Requirements management plan ü Stakeholder management plan ü Project Charter ü Stakeholder register Adapted from PMBOK 5 th Edition

5. 2 Collect Requirements Tools and techniques to Collect Requirements Brainstorming Ranking Interviews Questionaries

5. 2 Collect Requirements Tools and techniques to Collect Requirements Brainstorming Ranking Interviews Questionaries Focus groups Surveys Research Prototype Observation Mind Mapping Workshops Adapted from PMBOK 5 th Edition

5. 2 Collect Requirements Outputs of this process include – ü Requirements documentation as

5. 2 Collect Requirements Outputs of this process include – ü Requirements documentation as per previous slides ü 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 5 th Edition