Is this an appropriate action related to acceptance criteria?

Answer the following questions about the acceptance criteria within the project.

Decide whether the approach to setting and using acceptance criteria has been applied appropriately and select the response that supports your decision.

The requirement to ‘install a heat reclamation system’ shows as a Should Have in the Prioritised Requirements List. During Investigation in Solution Development Timebox B, the Project Manager advised the team NOT to set detailed acceptance criteria for this requirement until later in the Timebox, since the requirement may have to be dropped and the work would be wasted.

Is this an appropriate action related to acceptance criteria?
A . Yes, because only Must Have requirements should be fully understood.
B . Yes, because the acceptance criteria might need to be changed during the Solution Development Timebox.
C . No, because it is necessary to understand the full detail of all the work for completion in the Solution Development Timebox during Investigation.
D . No, because it indicates that the Solution Development Team has NO intention of delivering the Should Have requirements.

View Answer

Answer: B

Explanation:

B. Yes, because the acceptance criteria might need to be changed during the Solution Development Timebox.

Rationale:

In Agile Project Management, flexibility is key. It is important to prioritize work based on the value it provides and the necessity of the requirement. "Should Have" requirements are important but not critical, and they can be subject to change as the project progresses and as more information becomes available. Deferring the detailed setting of acceptance criteria for a "Should Have" requirement that might be dropped is a practical approach to managing workload and focusing efforts on the most critical aspects of the project first. This approach is in line with Agile’s principle of responding to change over following a fixed plan.