Bash, the Crucial Exams Chat Bot
AI Bot
Scope & Requirements Management Flashcards
| Front | Back |
| Define scope creep | Unauthorized changes to project scope after baseline approval |
| Define the critical success factor | Key elements that must be in place for project to succeed |
| Explain requirements elicitation | Techniques used to draw out stakeholder requirements such as interviews and workshops |
| Explain the change control process | Formal procedure for submitting reviewing and approving project changes |
| Explain the MoSCoW method | Prioritization technique using Must Should Could and Wont labels |
| How to prevent scope creep? | Establish clear change control process and engage stakeholders continuously |
| What are functional requirements? | Features and capabilities the system must perform |
| What are nonfunctional requirements? | System qualities and performance criteria such as reliability and usability |
| What is a scope baseline? | Approved version of project scope statement WBS and WBS dictionary |
| What is a scope management plan? | Document that defines how scope will be defined validated and controlled |
| What is a scope statement? | Document that describes the project deliverables and the work required to create them |
| What is a use case? | Detailed scenario describing interaction between actor and system |
| What is a user story? | Short description of a feature from the end user perspective |
| What is a work breakdown structure? | Hierarchical decomposition of deliverables to manage project work |
| What is acceptance criteria? | Specific conditions that deliverables must meet for stakeholder approval |
| What is project scope? | The work required to deliver the project objectives |
| What is requirement prioritization? | Ranking requirements based on importance urgency and feasibility |
| What is requirements gathering? | Process of collecting stakeholder needs to meet project objectives |
| What is requirements traceability matrix? | Grid linking requirements to their source and deliverables |
| What is scope validation? | Formal acceptance of completed project deliverables by stakeholders |
| What is stakeholder analysis? | Identification and assessment of stakeholder influences and interests |
| What is the purpose of a requirements document? | Formal record that outlines all project requirements and their details |
| Why is scope control important? | To monitor and manage changes ensuring project remains aligned with objectives |
Front
Why is scope control important?
Click the card to flip
Back
To monitor and manage changes ensuring project remains aligned with objectives
Front
What is a user story?
Back
Short description of a feature from the end user perspective
Front
What is stakeholder analysis?
Back
Identification and assessment of stakeholder influences and interests
Front
What is project scope?
Back
The work required to deliver the project objectives
Front
Explain the MoSCoW method
Back
Prioritization technique using Must Should Could and Wont labels
Front
What is a work breakdown structure?
Back
Hierarchical decomposition of deliverables to manage project work
Front
What is requirements gathering?
Back
Process of collecting stakeholder needs to meet project objectives
Front
What is the purpose of a requirements document?
Back
Formal record that outlines all project requirements and their details
Front
How to prevent scope creep?
Back
Establish clear change control process and engage stakeholders continuously
Front
What is requirement prioritization?
Back
Ranking requirements based on importance urgency and feasibility
Front
What is a scope statement?
Back
Document that describes the project deliverables and the work required to create them
Front
What is a use case?
Back
Detailed scenario describing interaction between actor and system
Front
Explain the change control process
Back
Formal procedure for submitting reviewing and approving project changes
Front
What is requirements traceability matrix?
Back
Grid linking requirements to their source and deliverables
Front
Explain requirements elicitation
Back
Techniques used to draw out stakeholder requirements such as interviews and workshops
Front
What is a scope baseline?
Back
Approved version of project scope statement WBS and WBS dictionary
Front
Define scope creep
Back
Unauthorized changes to project scope after baseline approval
Front
What is scope validation?
Back
Formal acceptance of completed project deliverables by stakeholders
Front
What are nonfunctional requirements?
Back
System qualities and performance criteria such as reliability and usability
Front
What is a scope management plan?
Back
Document that defines how scope will be defined validated and controlled
Front
What is acceptance criteria?
Back
Specific conditions that deliverables must meet for stakeholder approval
Front
Define the critical success factor
Back
Key elements that must be in place for project to succeed
Front
What are functional requirements?
Back
Features and capabilities the system must perform
1/23
Explores defining project scope, gathering requirements, preventing scope creep, and ensuring alignment with objectives.