Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
52 Cards in this Set
- Front
- Back
Key outputs when planning your project scope?
|
requirements documentation, project scope statement, scope baseline and WBS; you need to reference your scope management plan to define, develope, validate manage and control scope.
|
|
What is product scope?
|
what the project is creating
|
|
What is project scope?
|
The work required to create the project results
|
|
Process - Plan scope management
|
In the PLANNING process group. It emphasis the creation of the scope management plan;
|
|
What is the Scope management plan?
|
Contributes to the management and definition of the project by defining how scope will be managed. It guides: requirements gathering, scope statement, WBS, and validation and control of the scope of the project. It defines how we will: create a scope statement, create a WBS, validate project deliverables, address scope change requests
|
|
Process - Plan scope management: inputs
|
Project management plan; project charter
|
|
Process - Plan scope management: tools and techniques
|
Expert judgement
|
|
Process - Plan scope management: outputs
|
Scope management plan; Requirements management plan
|
|
Project charter
|
the high-level description of the project and product details.
|
|
Scope creep
|
The risk of unmanaged scope expansion due to not making use of the Scope management plan defined in the Plan Scope Management process
|
|
What is the Requirements management plan?
|
It helps theproject manager and team analyze, document and manage the project requirements. It defines how we will: manage requirements, create requirements, plan+track+report requirement activity, perform configuration management activities, initiate changes to the product or service or result, analyze the impact of requirement changes, change approval authorization, prioritize requirements, determine product metrics and usage rationale, define the traceability structure for the requirements traceability matrix and traceability to any other requirements-related documentation
|
|
Process - Collect Requirements
|
In the PLANNING process group. It emphasis the creation of requirements based on the analysis of sponsor, customer or stakeholder needs; Rrequirements feed the WBS and factor into Quality, schedule and cost estimates; begins with the analysis of the project charter and stakeholder register;
|
|
Process - Collect Requirements: inputs
|
Scope management plan; requirements management plan; stakeholder management plan; project charter; stakeholder register
|
|
Process - Collect Requirements: tools and techniques
|
Interviews; facilitated workshops, focus groups; group creativity techniques; observations; group decision-making techniques; prototypes; questionnaires and surveys; benchmarking; context diagrams;
|
|
Process - Collect Requirements: outputs
|
Requirements documentation; Requirements traceability matrix
|
|
What are some Group Creativity Techniques?
|
brainstorming; nominal group technique; multiple criteria decision analysis; idea/mind mapping; affinity diagrams
|
|
What is a Requirements traceability matrix?
|
A document that itemizes each requirement and associates it to the detailed and high-level requirements documentation where it was discovered and defined as well as to any design, implementation or test documentation
|
|
Process - Define scope
|
In the PLANNING process group; It emphasises writing the scope statement used in future decision-making and should include: what the project consists of; what is involved to create the project; and what it is expected to provide/do once it is complete
|
|
Process - Define scope: inputs
|
Scope management plan; Project charter; Requirements documentation
|
|
Process - Define scope: tools and techniques
|
Expert judgement, product analysis; alternatives generation; facilitated workshops
|
|
Process - Define scope: outputs
|
project scope statement
|
|
What is product analysis?
|
It translates product descriptions into actual deliverables
|
|
What is Alternatives generation?
|
brainstorming and lateral thinking to indentify approach alternatives in how you approach the execution and performance of the project
|
|
What is the Project Scope Statement?
|
Defines the project in terms of it's scope, key deliverables, product acceptance criteria, exclusions, assumptions and constraints; It facilitates team project planning and identifies stakeholder expectations;
|
|
What makes up the Project Scope Statement?
|
Typically consists of: product scope description (progresively elaborated), product acceptance criteria, project deliverables, project exclusions, project contraints and assumptions
|
|
Process - Create WBS
|
In the PLANNING process group; It emphasises breaking down the project into pieces that can be easily tracked;
|
|
What is Rolling wave planning?
|
Project planning that is progressively elaborated as additional requirements become more clear; It is used when initial project decomposition is unable to break down deliverable requirments due to a lack of information
|
|
Process - Create WBS: inputs
|
Scope management plan, project scope statement, requirements documentation
|
|
Process - Create WBS: tools and techniques
|
Decomposition (breaking down scope and requirements into manageable pieces)
|
|
Process - Create WBS: outputs
|
Scope baseline (the details of the planned scope of the project) which includes the approved: project scope statement, WBS and WBS dictionary
|
|
What is the WBS?
|
Work breakdown structure; The team defines the main pieces of the project work, decomposing them into WORK PACKAGES (the lowest level of the WBS, often deliverables) and possibly down to activity lists; teams working on this creates buy-in from team members
|
|
What are the main pieces of a WBS?
|
control accounts, planning packages, and work packages
|
|
What is a control account?
|
A management control point that represents a collection of one or more work packages; it acts like a management milestone with rolled up scope, time and cost.
|
|
What is a work package?
|
A work package is an estimated (level of effort in terms of: cost, time, and scope) for a descrete piece of work in the project
|
|
What is the 100% rule?
|
!00% of the project work needs to be represented in the WBS (from admin to testing)
|
|
What is WBS numbering?
|
It lets team members know where work fits into the project
|
|
What is the WBS dictionary?
|
Provides supporting details for each WBS item that is typically not practical to put into the graphical format of the WBS. The WBS dictionary typically includes: code of accounts, list of schedule milestones, cost estimates, description of work, associated sceduled activities, quality requirements, contract information, responsible organization, resources required, acceptance criteria
|
|
What is the Organizational breakdown structure?
|
Shows how the project organization is structured in terms of human resources, to accomplish project activities
|
|
What is the Risk breakdown structure?
|
Shows the potential project risk broken down by risk category
|
|
What is the Resource breakdown structure?
|
Shows the types of resources used in the project
|
|
What is the Bill of materials?
|
Includes components, sub-assemblies and assemblies used to build a product or service
|
|
Process - Validate Scope
|
In the MONITORING AND CONTROLLING process group; Used to secure sign-off of project scope at logical intervals during the process (milestones, each deliverable, possibly each phase, when the work is complete, etc)
|
|
Process - Validate Scope: inputs
|
Project management plan; requirements documentation; requirements traceability matrix; verified deliverables; work performance data
|
|
Process - Validate Scope: tools and techniques
|
Inspection (to measure, examine and validate that the work and deliverables fulfill the requirements)
|
|
Process - Validate Scope: outputs
|
Accepted deliverables; change requests (not yet approved)
|
|
Process - Control Scope
|
in the MONITORING AND CONTROLLING process group; proces for handling any scope change requests and related matters
|
|
Process - Control Scope: inputs
|
Project management plan; Requirements documentation; requirements traceability matrix; work performance data
|
|
Process - Control Scope: tools and techniques
|
Variance Analysis
|
|
Process - Control Scope: outputs
|
Work performance information; Change requests
|
|
What is Variance analysis?
|
it determines the difference between the original scope baseline and actual performance.
|
|
What is Work performance data?
|
The raw data coming from people executing activities in the EXECUTING process group
|
|
Work is Work performance information?
|
The reports generated from having analyzed work performance data
|