HKSM
Updated Implementation Deadlines for Projects
Project implementation due dates can be revised when new or modified user stories add or change requirements, ensuring the timeline reflects the added effort, risks, and dependencies.
Key Points
- Triggered by changes in the product backlog, such as new or revised user stories.
- Requires impact analysis on scope, estimates, dependencies, risks, and team capacity.
- Update the release plan or schedule baseline through backlog refinement and change control as needed.
- Communicate the new dates and realign milestones and external commitments with stakeholders.
Example
During release planning, a new security user story is added after a regulatory update. The team estimates 16 points and flags an integration dependency. With a velocity of 20 points per sprint, the release date moves from May 10 to May 24, and the change is communicated to sponsors and impacted teams.
PMP Example Question
A product owner introduces two new user stories that add reporting requirements mid-release. What should the project manager do to apply Updated Implementation Deadlines for Projects?
- Lock the original release date and require overtime to absorb the change.
- Re-estimate the backlog, analyze impacts, and adjust the implementation deadline as needed while communicating changes.
- Add the stories but keep scope and schedule fixed to protect the date.
- Cancel the current release and start a new project.
Correct Answer: B — revise the implementation deadline based on new or changed user stories.
Explanation: New or modified user stories that introduce or change requirements should trigger impact analysis and potential schedule updates, with transparent stakeholder communication.
