PK0-004 · Question #1069
Which of the following is the BEST approach when the main stakeholder asks for a change in the requirements of an Agile project?
The correct answer is B. Add it to the product backlog and reprioritize. In Agile, the product backlog is the single authoritative, prioritized list of all work to be done on the project. When a stakeholder requests a new requirement, the proper process is to add it to the product backlog and then reprioritize based on business value, urgency, and…
Question
Which of the following is the BEST approach when the main stakeholder asks for a change in the requirements of an Agile project?
Options
- ASubmit a change request to the development learn.
- BAdd it to the product backlog and reprioritize.
- CPut it in the sprint backlog and reprioritize.
- DPut it in the sprint backlog as high priority.
How the community answered
(52 responses)- A2% (1)
- B90% (47)
- C4% (2)
- D4% (2)
Explanation
In Agile, the product backlog is the single authoritative, prioritized list of all work to be done on the project. When a stakeholder requests a new requirement, the proper process is to add it to the product backlog and then reprioritize based on business value, urgency, and dependencies. This ensures the change is captured and considered in proper order without disrupting the ongoing sprint. Adding it directly to the sprint backlog (C or D) bypasses the product owner's prioritization process and can disrupt the current sprint commitment. Submitting a formal change request to the development team (A) is a waterfall/traditional process, not Agile practice. The backlog is Agile's change management mechanism.
Topics
Community Discussion
No community discussion yet for this question.