Common use of Project Methodology Clause in Contracts

Project Methodology. 6.1. For clarity, the parties acknowledge and agree that each Project has different requirements which may evolve over time and accordingly: 6.1.1. Unless expressly set out in the Service Order Form, the Supplier will propose what it considers to be a suitable methodology following Good Industry Practice based on the needs of the Customer at the time. The Supplier shall provide a reasonably detailed summary of its proposed methodologies and ways of working upon request by the Customer. Such determination may take into account differing levels of priority as to duration, cost, efficiency, level of creative input required etc and where applicable the Supplier shall maintain a Backlog to record any parts of the services which are de-prioritised for later delivery and shall keep the Customer informed and updated as the Backlog changes; 6.1.2. Either the Supplier, Customer or the Product Owner may, from time to time during the Project Term, request a change to the priority of the Deliverables or request a change to the Project Methodology specified in the relevant Service Order Form or otherwise adopted by the Supplier in relation to a Project. Subject to an agreement in writing between the Supplier and one of the Product Manager or the Customer, such a change may not require a formal Change Request if the Supplier confirms that there would be no impact on the scope or cost of the Project; 6.1.3. the Product Owner must submit any other change as part of a Change Request to the Supplier for approval. 6.2. The Product Owner and the Project Team shall use all reasonable endeavours to agree the Acceptance Criteria for applicable Deliverables as soon as possible following the Commencement Date for each Project, or as soon as possible after the applicable Deliverable is proposed during the Project. 6.3. Once the Deliverables to be included in the Project have been agreed any changes may be subject to a formal Change Request: 6.4. Where the Project Methodology requires, the Supplier shall keep the Customer updated as to its progress in relation to each applicable Deliverable or the progression of Requirements and the status of the Backlog where relevant. The Supplier may provide access to a project planning/management system at its discretion from time to time, such as Jira. 6.5. The Project shall be complete once all Deliverables are Accepted and/or the Result is deemed to substantially meet the Requirements by either party acting reasonably (“Completion”). Please see clause 15.5 of this Agreement for the Acceptance Testing procedure. If there is any disagreement as to whether or not a Project has reached “Completion” the parties shall follow the Dispute Resolution Procedure set out in clause 37. 6.6. Within five (5) Business Days of Completion, the Supplier shall provide the Customer with written notice of the same and shall deliver any remaining undelivered Deliverables to the Customer (in object code versions only).