Is this an appropriate approach to setting detailed 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.

At the beginning of Solution Development Timebox A, the Timebox is being planned in detail. Although Foundations was conducted at a high level, the Prioritised Requirements List was baselined. Now the Solution Development Team is setting detailed acceptance criteria against each requirement.

Is this an appropriate approach to setting detailed acceptance criteria?

A. Yes, because acceptance criteria can only be understood at a high level during Foundations and will always need further investigation.

B. Yes, because the Solution Development Team members will be setting acceptance criteria for the first time during Solution Development Timebox A.

C. No, because the Solution Development Team should NOT be involved in setting acceptance

criteria.

D. No, because acceptance criteria should be set in detail against each requirement during Foundations.

View Answer

Answer: A

Explanation:

A. Yes, because acceptance criteria can only be understood at a high level during Foundations and

will always need further investigation.

Rationale:

In Agile Project Management, while the Foundations phase does involve setting high-level expectations and a prioritized requirements list, the detailed acceptance criteria are often refined during the actual Solution Development iterations or timeboxes. This is because, as the work progresses, the team’s understanding of the product grows, and they are better equipped to define detailed acceptance criteria that align closely with the customer’s needs and the project’s evolving context. It’s a collaborative and iterative process, allowing for greater precision in defining what will make a particular feature or requirement acceptable.