Project State: From As-Is to Future State Requirements

PMBOK v8 Definition

Project requirements describe the actions, processes, or other conditions the project should meet to transition from the current, as-is state to the desired future state. These requirements include milestone dates, contractual obligations, constraints, and other conditions that define what the project must achieve. Quality requirements capture any condition or criteria required to validate the successful completion of a project deliverable or fulfillment of other project requirements, including tests, certifications, and validations.

Why It Matters for the Exam

The concept of project state and requirements transition is frequently tested in PMI exam questions about scope management and requirements gathering. Questions often appear in the context of defining project success criteria, validating deliverables, and understanding the difference between project requirements and quality requirements. Expect scenario-based questions where you must identify which type of requirement is being described.

Key Points to Remember (for the exam)

• Core Definition: Project state describes the gap between the current "as-is" state and the desired "future state" that the project must achieve
• Two Requirement Types:
  • Project requirements: Actions, processes, conditions (milestone dates, contractual obligations, constraints)
  • Quality requirements: Conditions/criteria to validate successful completion (tests, certifications, validations)
• Transition Focus: The project's purpose is to bridge the gap between as-is and future state
• Requirements Management Plan: Documents how requirements will be analyzed, documented, and managed throughout the project
• Requirements Traceability Matrix: Links requirements to their origin and tracks them through the project lifecycle
• Change Control: Any change to requirements must go through the formal Assess and Implement Changes process
• Final Report: Documents the transition of the final product, service, or result from one team to another

Typical PMI Exam Example

A construction project manager is defining the requirements for a new office building. During stakeholder interviews, the facilities team states they need the building to achieve LEED Gold certification. The project manager documents this as a quality requirement. Meanwhile, the legal department specifies that construction must be completed by December 31, 2025, per the contract. This is documented as a project requirement.

PMI Exam Traps

• Trap: Confusing project requirements with quality requirements

  • Reality: Project requirements describe what the project must do (actions, conditions); quality requirements describe how to validate successful completion (tests, certifications)

• Trap: Thinking the "as-is state" is the project's starting point only

  • Reality: The as-is state represents the current situation, and the future state is what the project aims to achieve; the project's purpose is to transition between these states

• Trap: Assuming all requirements are documented in the same way

  • Reality: Project requirements and quality requirements are distinct categories with different documentation and validation approaches

• Trap: Believing requirements are fixed once documented

  • Reality: Requirements can change through the formal change control process (Assess and Implement Changes)

Important PMI Connections

Quick Review Questions

1. What is the difference between a project requirement and a quality requirement as defined in PMBOK v8?

2. A stakeholder requests that a software application must pass security penetration testing before release. Is this a project requirement or a quality requirement?

3. What document captures how requirements will be analyzed, documented, and managed throughout the project?

4. During which process are changes to requirements formally assessed and implemented?

5. What output documents the transition of the final product from one team to another?

PMBOK v8 Reference

Section 2.4 – Project Requirements and Quality Requirements (as referenced in the PMBOK v8 RAG context)

Note: The exact section numbering may vary in your PMBOK v8 copy. The content is derived from the requirements definition and management sections of the PMBOK v8 Standard for Project Management.