2 Project Scope and Requirements Free Online FlashCards

What does project scope describe?

Project scope describes the work a project will perform and the products or services it will deliver.

How does a clear scope help a project?

A clear scope gives stakeholders a shared understanding, guides detailed planning, and helps determine whether proposed work belongs in the project.

How do objectives, requirements, and deliverables differ?

Objectives state intended results; requirements specify what the result must do or satisfy; deliverables are the outputs the team produces.

What makes a project objective useful?

Objectives state intended results. They are more useful when specific enough to assess and, where possible, include measures of success and a target date or other relevant constraint.

What is a requirement, and what makes it good?

Requirements express the capabilities, qualities, or conditions a product or service must meet. Good requirements are clear, necessary, consistent, and testable.

How should requirements be made traceable?

Give requirements unique identifiers and link them to the objectives or stakeholder needs they support. Plan how each requirement will be verified.

What is a project deliverable?

A deliverable is a defined output produced by the project, such as an approved design, a working software feature, or a training guide.

What is the purpose of acceptance criteria?

Acceptance criteria make expectations observable, connect to relevant requirements, and should be agreed with appropriate stakeholders.

What does verification check?

Verification checks whether a deliverable meets its specified requirements.

What does validation check?

Validation checks whether the result meets the user’s or customer’s intended need.

What distinguishes in-scope from out-of-scope work?

In-scope work and capabilities are included in what the team will deliver; out-of-scope work is related but will not be delivered by the project.

What are project interfaces?

Interfaces are connections or handoffs with other systems, teams, or organizations. Naming them clarifies how the project relates to external work.