Common use of Acceptance Testing Procedure Clause in Contracts

Acceptance Testing Procedure. ‌ The customer shall undertake the acceptance tests to determine whether the sprint results have met their respective acceptance criteria. The customer shall carry out the acceptance tests using the acceptance criteria within [one] business day of completion of the relevant sprint, at a time to be agreed in writing with the supplier. The customer shall permit supplier to attend and observe the acceptance tests. The customer shall not unreasonably withhold or delay its agreement that any particular sprint result meets its acceptance criteria. The customer shall be deemed to have agreed that the sprint requirements have met their respective acceptance criteria on the earliest of: The customer's written agreement to that effect; The expiry of [one] business day after the completion of the relevant acceptance tests, unless the customer has given written notice to the supplier that one or more sprint results do not meet their respective acceptance criteria, specifying the relevant sprint result or sprint results and details of the nature of the failure, in each case; The expiry of [two] business days after the supplier informs the customer that the sprint requirements are ready for the relevant acceptance tests, if those acceptance tests have not been completed; and The live use of the software (or the relevant part of it) by the customer or any of its employees, agents or contractors. Within five business days of the end of every second sprint the product owner, scrum master and the development team shall hold a release planning session. At each release planning session, the product owner, scrum master and the development team shall: Discuss whether development of the software remains aligned with the product vision and with the parties' expectations. Evaluate cost and timeline impacts due to additions of requirements to, or deletions of requirements from, the product backlog. Material changes to the product backlog shall be subject to the agile change control process.

Appears in 2 contracts

Sources: Support Agreement, Support Agreement