Chapter 5 Flashcards
what is Project Scope Management?
- processes required to ensure that the project includes all the work required, and ONLY the work required, to complete the project successfully
- defining and controlling what is and isn’t included in the project
what are the processes in Project Scope Management?
- 1 collect requirements
- 2 define scope
- 3 create WBS
- 4 verify scope
- 5 control scope
define Collect Requirements process
- process of defining and documenting stakeholders’ needs to meet the project objectives
what is the Define Scope process?
- process of developing a detailed description of the project and product
what is the Create WBS process?
- process of subdividing project deliverables and work into smaller, more manageable components
what is the Verify Scope process?
- process of formalizing acceptance of the completed project deliverables
what is the Control Scope process?
- process of monitoring the status of the project and product scope and managing changes to the scope baseline
in the project context, what does scope refer to?
can refer to product scope (features and functions that characterize a product, service, or result)
– and/or –
project scope (work that needs to be accomplished to deliver a product, service or result)
what is the scope baseline for a project?
the approved detailed project scope statement, the WBS and the WBS dictionary
planning effort that’s part of the Develop Project Management Plan process creates a scope management plan. what does this plan do?
- provides guidance on how the project scope will be defined, documented, verified, managed and controlled
what is the completed project scope and product scope measured against?
- completion of project scope is measured against the project management plan
- completion of product scope is measured against the product requirements
what are requirements?
- quantified and documented needs and expectations of the sponsor, customer, and stakeholder
- elicited, analyzed and recorded
what are requirements used for in the planning process?
- become the foundation of the WBS and cost, schedule and quality planning are built upon these requirements
what is the different between project requirements and product requirements?
- project requirements can include business requirements, project management requirements, delivery requirements, etc.
- product requirements can include technical requirements, security requirements, performance requirements, etc.
what are the inputs to the Collect Requirements process?
- project charter
2. stakeholder register
what are the tools and techniques used in the Collect Requirements process?
- interviews
- focus groups
- facilitated workshops
- group creativity techniques
- group decision making techniques
- questionnaires and surveys
- observations
- prototypes
what are the outputs of the Collect Requirements process?
- requirements documentation
- requirements management plan
- requirements traceability matrix
how does the project charter contribute to the Collect Requirements process?
- provides the high-level project requirements and high-level description of the project so that detailed product requirements can be developed
how does the stakeholder register contribute to the Collect Requirements process?
- used to identify stakeholders that can provide information on detailed project and product requirements
what are interviews and how do they contribute to the Collect Requirements process?
- interviews involve talking to stakeholders and asking prepared & spontaneous questions and recording their responses
- interviewing experienced project participants, stakeholders and experts can help identify and define features and functions of the project deliverables
what are focus groups and how do they contribute to the Collect Requirements process?
- bring together prequalified stakeholders and experts to learn about their expectations and attitudes about the proposed product, service, or result. run by a moderator
what are facilitated workshops and how do they contribute to the Collect Requirements process?
- focused sessions that bring key cross-functional stakeholders together to define product requirements.
- a primary technique for defining cross-functional requirements and reconciling stakeholder differences
- these sessions can build trust, foster relationships and improve communication among participations which can help with stakeholder consensus
- ex. Joint Application Development (JAD) sessions and Quality Function Deployment (QFD)
what are Joint Application Development (JAD) sessions?
- facilitated sessions that bring together users and the development team to improve the software development process. used in software development industry
what is Quality Function Deployment (QFD)?
used in manufacturing industry, this is a facilitated workshop technique that helps determine critical characteristics for new product development
- takes into account customer needs (Voice of the Customer - VOC)