HKSM

Formally authorized changes that are cleared for implementation and placed into the prioritized product backlog, to be scheduled for delivery in upcoming sprints. These approvals may come from program or portfolio management and become inputs for future iterations.

Key Points

• They have passed the defined approval process (e.g., Product Owner or change control governance) before work begins.
• Once approved, they are added to the prioritized product backlog and sequenced with other work.
• Requests may originate from stakeholders including program or portfolio managers.
• Implementation is planned in a future sprint and tracked for transparency and traceability.

Example

A portfolio manager submits a compliance update request. After review and approval, the Product Owner adds it to the prioritized product backlog and schedules it into the next available sprint where capacity allows.

PMP Example Question

Which statement best describes Approved Change Requests in an agile project?

1. Ideas proposed by team members for continuous improvement during retrospectives.
2. Unreviewed change requests waiting for triage by the Product Owner.
3. Changes formally authorized and queued in the prioritized product backlog for upcoming sprints.
4. Scope changes implemented immediately to prevent any impact on velocity.

Correct Answer: C — Changes formally authorized and queued for delivery

Explanation: Approved Change Requests are reviewed and authorized, then added to the prioritized product backlog to be planned into future sprints.