Scope Management Flashcards
1
Q
Process “Plan Scope Management”
A
- Goal: Create scope mgmt plan that documents how the project and product scope will be planned, validated and controlled
- Inputs: Project charter, PMplan (quality mgmt plan, project life cycle description, development approach), EEFs, OPAs
- Tools+Techniques: Expert judgment, alt. analysis, meetings
- Outputs: Scope mgmt plan, requirements mgmt plan
2
Q
Process “Collect Requirements”
A
- Goal: determine, document and manage stakeholder needs and requirements to meet objectives (provides the basis for defining the product and project scope.
- Inputs: Project charter, PMPlan (Scope Mgmt, Requirements Mgmt and Stakeholder Engagement Plan), Project Documents (Assumption Log, Lessons Learned Reg, Stakeholder Reg.), Business Case, Agreements, EEFs, OPAs
- Tools+Techniques: Expert Judgment, Data Gathering (Brainstorming, Interviews, Focus Groups, Questionnaires and Surveys, Benchmarking), Document Analysis, Decision Making, Data Representation (Affinity Diagrams, Mind mapping), Interpersonal & Team Skills (Nominal Group, Obs/Conversation, Facilitation), Prototypes, Context Diagrams
- Outputs: Req. Documentation, Req. Traceability Matrix
3
Q
Process “Define Scope”
A
- Goal: develop a detailed description of the project and describe the boundaries and acceptance criteria.
- Inputs: Project charter, PMPlan (for scope), project documents (assumption log, req. documentation, risk reg.), EEFs, OPAs
- Tools+Techniques: Expert judgment, Alt. analysis, Multicriteria decision analysis, Facilitation, Product analysis
- Outputs: Project scope statement, project documents updates (assumption log, req. documentation, req. traceability matrix, stakeholder reg.)
4
Q
Process “Create WBS”
A
- Goal: subdivide project deliverables and project work into smaller, more manageable components.
- Inputs: Scope mgmt plan, Project documents (project scope statement, req. documentation), EEFs, OPAs
- Tools+Techniques: Expert judgment, decomposition
- Outputs: scope baseline, project document updates (assumption log, req. documentation)
5
Q
Process “Validate Scope”
A
- Goal: formalize acceptance of the completed project deliverables
- Inputs: PMPlan (scope mgmt plan, req mgmt plan, scope baseline), project documents (lessons learned reg, quality reports, req. documentation, req. traceability matrix, verified deliverables, work performance data
- Tools+Techniques: inspection, voting
- Outputs: accepted deliverables, work performance info, CRs, Project documents updates (lessons learned reg, req. documentation, req traceability matrix)
6
Q
Process “Control Scope”
A
- Goal: monitor the status of the project and product scope and manage changes to the scope baseline
- Inputs: PMPlan (scope, change, config mgmt plan; scope baseline; performance measurement baseline)
- Tools+Techniques: data analysis (variance + trend analysis)
- Outputs: work performance info; CRs; PMPlan updates (scope mgmt plan; scope, schedule, cost + performance measurement baseline), project documents updates (lessons learned reg., req. documentation, req, traceability matrix)
7
Q
Scope Management Process
A
- Develop plan for how you will plan, validate and control scope for and requirements
- Determine requirements (making sure they support business case and project charter)
- Sort and balance the needs of stakeholders and determine scope
- Create the WBS to scope into smaller, more manageable pieces.
- Define each piece in the WBS dictionary.
- Obtain validation (signed acceptance) that completed scope is acceptable to customer & sponsor
- Measure scope performance; adjust as needed.
8
Q
Scope Management Plan (components)
A
- Process for preparing a project scope statement
- Process that enables the creation of the WBS from the project scope statement
- Process that establishes how the scope baseline will be approved and maintained
- Process that specifies how formal acceptance of the completed deliverables will be obtained
9
Q
Requirements Management Plan (components)
A
- how requirements activities will be planned, tracked and reported
- configuration mgmt activities like how changes will be initiated or impacts are analyzed
- requirements prioritization process
- metrics that will be used and the rationale for using them
- traceability structure that reflects the requirement attributes captured in the req. traceability matrix
10
Q
Requirement classifications
A
- Business req.: higher level needs of the org like business opportunities
- Stakeholder req.: needs of stakeholders
- Solution req.: features, functions, and characteristic of the product, service or result (function and nonfunctional like security, performance, safety, etc.)
- Transition and readiness req.: temporary capabilities needed to transition from the current as-is state to desired future state like data imports or trainings etc.
- Project req.: actions, processes, etc. the project has to meet like milestone dates, risk mgmt procedures, etc.
- Quality req.: conditions or criteria to validate the successful completion of a project deliverable or other requirements (tests, certifications, validations, etc.)
11
Q
Affinity Diagrams
A
- organizes a large number of ideas into groups (using their natural relationships).
- used to generate, organize, and consolidate information
- often an organized output from a brainstorming session.
- only used in ‘Collect requirements’ and ‘Manage Quality’
12
Q
Facilitation sessions within requirements gathering
A
- JAD (Joint application design): mainly used in software development, JAD brings business SMEs or end users and the development team together to gather requirements and improve the software dev process
- QFD (Quality functional deployment): technique that helps determine critical requirements by collecting customer needs (VOC), objectively sorting and prioritizing them and setting goals for achieving them.
13
Q
Context diagrams
A
- used to define and model scope (an example of a scope model)
- depicts the product scope and boundaries by showing a business system (processes, IT, etc.) and how people, processes and other systems (actors) interact with it (interfaces)
- only used in ‘Collect Requirements’
14
Q
Requirements Traceability Matrix
A
=grid that links products requirements from their origin to the deliverable that satisfy them
- ensures that each requirements adds business value by linking it to the business and project objectives
- provides a structure for managing changes to the product scope
15
Q
Product analysis techniques
A
- product breakdown
- requirements analysis
- systems analysis
- systems engineering
- value analysis
- value engineering
