Common use of Development and Sprints Clause in Contracts

Development and Sprints. 19.1. If Parties have agreed in a Statement of Work that ▇▇▇▇▇ ▇▇▇▇▇▇ will provide any development services, project management services and/or similar services, then (unless otherwise agreed upon) such services will be performed in Sprints. Prior to each Sprint, the Parties establish an objectively measurable Deliverable (e.g., a functionality) to be developed during the Sprint. 19.2. Unless otherwise agreed upon, the Parties will lay down such Deliverable and other terms of one or multiple Sprints in a Statement of Work and/or development support systems of ▇▇▇▇▇ Blocks. Only the Deliverable agreed upon in writing for each Sprint falls within the scope of that Sprint. Everything else is out of scope, there are no such things as ‘unreported’ and/or ‘implicit’ wishes or results that apply for a Sprint. The same applies to general reports of meetings, lists with Client’s wishes and/or other such documents. Everything in such documents is out of scope, unless Parties have agreed upon in a Statement of Work that certain specific results shall be developed in a Sprint. 19.3. Client acknowledges that needed development hours communicated by ▇▇▇▇▇ ▇▇▇▇▇▇ to Client are merely estimates and the actual number of hours may differ from the estimates, unless expressly indicated to the contrary. No rights can be derived from such estimations. 19.4. At the end of each Sprint, ▇▇▇▇▇ ▇▇▇▇▇▇ will share the Deliverable with the Client. Client will then test the developed functionality within 7 days in accordance with the test script provided by ▇▇▇▇▇ ▇▇▇▇▇▇. The result of the test is either a ‘pass’, meaning that the Deliverable objectively complies with what was agreed upon, or a ‘fail’, meaning the Deliverable objectively does not comply with what was agreed upon. Any subjective aspects of the Deliverable are never a reason for a ‘fail’. 19.5. If the Deliverable objectively does not comply with the Statement of Work, then ▇▇▇▇▇ ▇▇▇▇▇▇ will use its best efforts to fix this Deliverable. In other cases, e.g., when Client has subjective reasons not to agree with the result, new Sprints must be purchased by Client to develop the desired result. Additional Sprints must also be purchased when the estimated hours were not enough to develop the agreed upon Deliverable.

Development and Sprints. 19.1. If Parties have agreed in a Statement of Work that ▇▇▇▇▇ ▇▇▇▇▇▇ Betty Blocks will provide any development services, project management services and/or similar services, then (unless otherwise agreed upon) such services will be performed in Sprints. Prior to each Sprint, the Parties establish an objectively measurable Deliverable (e.g., a functionality) to be developed during the Sprint. 19.2. Unless otherwise agreed upon, the Parties will lay down such Deliverable and other terms of one or multiple Sprints in a Statement of Work and/or development support systems of ▇▇▇▇▇ Blocks. Only the Deliverable agreed upon in writing for each Sprint falls within the scope of that Sprint. Everything else is out of scope, there are no such things as ‘unreported’ and/or ‘implicit’ wishes or results that apply for a Sprint. The same applies to general reports of meetings, lists with Client’s wishes and/or other such documents. Everything in such documents is out of scope, unless Parties have agreed upon in a Statement of Work that certain specific results shall be developed in a Sprint. 19.3. Client acknowledges that needed development hours communicated by ▇▇▇▇▇ ▇▇▇▇▇▇ Betty Blocks to Client are merely estimates and the actual number of hours may differ from the estimates, unless expressly indicated to the contrary. No rights can be derived from such estimations. 19.4. At the end of each Sprint, ▇▇▇▇▇ ▇▇▇▇▇▇ Betty Blocks will share the Deliverable with the Client. Client will then test the developed functionality within 7 days in accordance with the test script provided by ▇▇▇▇▇ ▇▇▇▇▇▇Betty Blocks. The result of the test is either a ‘pass’, meaning that the Deliverable objectively complies with what was agreed upon, or a ‘fail’, meaning the Deliverable objectively does not comply with what was agreed upon. Any subjective aspects of the Deliverable are never a reason for a ‘fail’. 19.5. If the Deliverable objectively does not comply with the Statement of Work, then ▇▇▇▇▇ ▇▇▇▇▇▇ Betty Blocks will use its best efforts to fix this Deliverable. In other cases, e.g., when Client has subjective reasons not to agree with the result, new Sprints must be purchased by Client to develop the desired result. Additional Sprints must also be purchased when the estimated hours were not enough to develop the agreed upon Deliverable.