26 Questions
What is the primary output of the requirement elicitation process?
Requirements documentation
Which of the following is NOT a tool or technique used in requirement elicitation?
Scope Statement
What is the purpose of translating high-level requirements into more detailed requirements?
To eventually turn into the deliverables
Which process involves verifying that the project scope is correct and complete?
Scope Verification
What is the primary purpose of the Work Breakdown Structure?
To comprise the project deliverables
Which of the following is an input to the requirement elicitation process?
Project Charter
What is the purpose of scope change control?
To manage changes to the project scope
Which of the following is a technique used in requirement elicitation to gather information from a large group of stakeholders?
Facilitated workshops
What is the primary purpose of a Work Breakdown Structure (WBS)?
To define project scope and decompose deliverables into smaller tasks
What can lead to vastly different understandings of project deliverables?
Differences in perception of project requirements
What is the primary output of scope verification?
Accepted deliverables
What is the purpose of a scope change control process?
To manage and document changes to the project scope
What is the primary input to the scope verification process?
Requirements documentation
What is the purpose of a project scope statement?
To define project scope and objectives
What is a key benefit of using a Work Breakdown Structure (WBS)?
It provides a framework for decomposing project scope into smaller tasks
What is a key activity in scope creep management?
Controlling changes to project scope
What is the primary purpose of the project scope statement?
To describe the project's deliverables and constraints
What is the main goal of scope verification?
To verify that the project deliverables meet the acceptance criteria
What is scope creep management?
A process to control and document changes to the project scope
What is the purpose of the scope change control process?
To approve or reject changes to the project scope
What is the main component of a work breakdown structure (WBS)?
Project deliverables and milestones
What is the output of the define scope process?
Project scope statement
What is included in a project scope statement?
Product scope description and project deliverables
What is the purpose of decomposition in creating a work breakdown structure (WBS)?
To break down the project into smaller, manageable tasks
What is the output of the create WBS process?
Work breakdown structure (WBS) and WBS dictionary
What is the relationship between the project scope statement and the work breakdown structure (WBS)?
The project scope statement is an input to the WBS
Study Notes
Define Scope
- Project scope statement includes: product scope description, product acceptance criteria, project deliverables, project exclusions, project constraints, and project assumptions.
- Input: project charter, requirements documentation, and organizational process assets.
- Tools and techniques: expert judgment, product analysis, alternatives identification, and facilitated workshops.
- Output: project scope statement, project document updates.
Create Work Breakdown Structure (WBS)
- A WBS is a deliverable-oriented grouping of the work involved in a project, defining the total scope of the project.
- A WBS is used for planning and managing project schedules, costs, resources, and changes.
- Decomposition is subdividing project deliverables into smaller, manageable pieces.
- Input: project scope statement, requirements documentation, and organizational process assets.
- Tools and techniques: decomposition.
- Output: WBS, WBS dictionary, scope baseline, and project document updates.
Verify Scope
- Verify scope ensures that the project deliverables are complete and meet the stakeholders' requirements.
- Differences in perception of project deliverables can lead to vastly different understandings of what exactly is required.
- Input: project management plan, requirements documentation, and validated deliverables.
- Tools and techniques: inspection and reviews.
- Output: accepted deliverables, change requests, and project document updates.
Requirement Elicitation
- Requirement elicitation involves gathering, documenting, and defining the stakeholders' requirements.
- Requirements need to be translated from high-level requirements to more detailed requirements.
- Input: project charter, stakeholder register, and requirements management plan.
- Tools and techniques: interviews, focus groups, facilitated workshops, group creativity techniques, group decision making techniques, questionnaires and surveys, observations, prototypes, and document analysis.
- Output: requirements documentation and requirements traceability matrix.
This quiz is about defining the scope of a software project, covering inputs, tools, and techniques, and outputs. It includes the project charter, requirements documentation, and expert judgment.
Make Your Own Quizzes and Flashcards
Convert your notes into interactive study material.
Get started for free
