Scope & Requirements Management Flashcards
CompTIA Project+ PK0-005 (V5) 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 |
Related Study Materials
About the Flashcards
Flashcards for the CompTIA Project+ exam help you master scope and change concepts common on the test. They cover definitions and controls for project scope, including scope statement, scope baseline, work breakdown structure, scope management plan, scope validation and acceptance criteria, plus scope control, scope creep and the formal change control process.
The deck also reviews requirements terminology and practical techniques: requirements gathering and elicitation methods, functional and nonfunctional requirements, requirements traceability matrix, prioritization methods such as MoSCoW, and artifacts like requirements documents, user stories and use cases. Focused cards reinforce stakeholder analysis and critical success factors for quick recall.
Topics covered in this flashcard deck:
- Scope definition and baselines
- Scope control and change
- Requirements elicitation methods
- Functional and nonfunctional requirements
- Requirements traceability matrix
- WBS, user stories, use cases