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.

During Solution Development Timebox A, a new Health and Safety requirement arises: the front door is required to have wheelchair access. This is a legal requirement and is a Must Have before any staff or general public access can be allowed. The Solution Development Team will work with the Local Planning Authority Officer, the specialist who identified the requirement, to identify further acceptance criteria for Solution Development Timebox A.

Is this an appropriate action related to acceptance criteria?

A. Yes, because the new requirement needs to be understood, built and delivered in this Timebox.

B. Yes, because the Local Planning Authority Officer owns the justification for the new requirement.

C. No, because this new requirement would NOT be included in the original Prioritised Requirements List and therefore does NOT need acceptance criteria to be defined.

D. No, because the Business Visionary is responsible for defining acceptance criteria.

View Answer

Answer: A

Explanation:

A. Yes, because the new requirement needs to be understood, built and delivered in this Timebox.

Rationale:

Agile Project Management is adaptable to changes, even late in the development process. The introduction of a new Health and Safety requirement, such as wheelchair access, which is a legal and must-have requirement, needs to be incorporated into the project as soon as it is identified. Working with the Local Planning Authority Officer to define acceptance criteria ensures that the requirement is clearly understood and that the solution developed meets the necessary legal standards. This approach ensures that the team can immediately address the new requirement and integrate it into the current work cycle, aligning with Agile’s principle of welcoming changing requirements, even late in development, for the customer’s competitive advantage.