Agile Process Sample Clauses

POPULAR SAMPLE Copied 1 times
Agile Process. 3.1 The Agile Process shall apply to the Services performed by the Supplier in each Sprint as further described in this paragraph 3. 3.2 The Product Owner and Development Team shall from time to time meet to discuss and agree Epics and Stories, and to establish the Backlog. 3.3 The parties shall hold a Sprint Planning Meeting before the development activities for the relevant Sprint can commence by the Development Team.
View Source
Agile Process. 5.1 For clarity, the parties acknowledge and agree that the Product Owner:‌ 5.1.1 may as it sees fit, from time to time during the Project Term, change the priority of the User Stories included in the Product Backlog and delete User Stories from the Product Backlog; 5.1.2 must follow the Agile Change Control Process if it wishes to include any new User Story in the Product Backlog; and 5.1.3 may not amend the number of Resource Points determined for specific User Stories. 5.2 The parties shall hold a Sprint Planning Meeting before the relevant Sprint commences. 5.3 At the Sprint Planning Meeting for each Sprint:‌ 5.3.1 the Product Owner shall select User Stories from the Product Backlog it wishes to be included in the current Sprint Backlog; 5.3.2 the Product Owner shall notify the Development Team of the selected User Stories and other relevant information; 5.3.3 the Development Team shall determine how many of the selected User Stories can be developed during the current Sprint and notify the Product Owner accordingly; and 5.3.4 the Product Owner and the Development Team may agree to replace a higher-priority User Story with a lower-priority User Story bearing equal or fewer Resource Points if it is technically expedient to do so. 5.4 The Product Owner and the Development Team shall use all reasonable endeavours to agree the selection of User Stories to be included in the current Sprint Backlog.‌ 5.5 Once the User Stories to be included in the Sprint Backlog (Sprint Requirements) have been agreed under paragraph 5.4:‌ 5.5.1 no alterations or additions may be made to those Sprint Requirements; 5.5.2 the Product Owner and the Development Team shall review and, if necessary, amend the Definition of Done in relation to each Sprint Requirement; and 5.5.3 the Development Team shall prepare the Sprint Backlog which shall include: (a) the Sprint Requirements; (b) the Resource Points for each Sprint Requirement; (c) the Definition of Done (the setting of which shall be undertaken in consultation with the Product Owner); and (d) a breakdown of each Sprint Requirement into specific tasks and allocation of these tasks to specific Development Team members. 5.6 The Development Team shall maintain the Sprint Backlog and update it daily to reflect any changes in the Resource Points for any Sprint Requirement. 5.7 During each Sprint the Development Team shall: 5.7.1 develop the Product in accordance with the Sprint Backlog and the relevant Statement of Work; and
View Source
Agile Process. 4.1 This clause 4 shall only apply where Xiatech provides Platform Implementation Services pursuant to a Work Order or where Xiatech provides other Services or Deliverables pursuant to a Work Order that the parties agree shall be provided subject to the agile methodology (Agile Services). 4.2 Xiatech shall provide the Deliverables pursuant to the Agile Services using agile methodologies via iterative Sprints (as agreed between the parties from time to time). 4.3 The parties shall meet on a regular basis and in any event within [5] Business Days on completion of a Sprint (as determined by Xiatech, acting reasonably) to agree: 4.3.1 in respect of future Sprints: (a) the estimated resource requirements and the cost for each future Sprint; (b) a breakdown of each Sprint item into specific tasks, sorted in terms of priority and allocation of these tasks to specific team members, provided that once agreed between the parties, no alterations or additions may be made to those items during the Sprint; and (c) any relevant acceptance criteria for each Sprint item; and 4.3.2 in respect of current or completed Sprints (as determined by Xiatech, acting reasonably): (a) whether the results of the current or completed Sprint meet their respective acceptance criteria in all material respects; and (b) whether any Sprint items that have not been developed during the current Sprint and/or any results that have not been materially delivered to the standard required by this Agreement should be designated to be completed in a future Sprint; 4.3.3 the present status of the relevant project and its compliance with the goals, targeted benefits and overall focus agreed between the parties; and 4.3.4 potential improvements to their practices, teamwork, environment, or organisation for implementation in future Sprints. 4.4 Xiatech shall: 4.4.1 use reasonable endeavours to achieve any agreed results of software development work carried out during the relevant Sprint within the agreed timeframes (provided that any such dates shall be estimates only); and 4.4.2 from time to time, review the estimated required resources for any Sprint items and determine in its discretion whether and, if so, what changes are reasonably required based upon the experience of the Sprint(s) at that point.
View Source

Related to Agile Process

  • Sale Process If a Non-Economic Facility is marketed for sale in accordance with Section 5.02 and Manager receives an offer therefor which it wishes to accept on behalf of the relevant TRS and Owner, Manager shall give the relevant TRS prompt notice thereof, which notice shall include a copy of the offer and any other information reasonably requested by such TRS. If the relevant TRS, on behalf of the relevant Owner, shall fail to accept or reject such offer within seven (7) Business Days after receipt of such notice and other information from Manager, such offer shall be deemed to be accepted. If the offer is rejected by the relevant TRS on behalf of the relevant Owner, and if Manager elects to continue marketing the Non-Economic Facility by providing written notice to the relevant TRS within seven (7) days of such rejection and Manager does not obtain another offer within ninety (90) days that is accepted by the relevant TRS, the Non-Economic Facility shall be deemed to have been sold to the relevant TRS on the date, at the price and on such other terms contained in the offer. If a Non-Economic Facility is sold to a third party or deemed to have been sold to the relevant Owner pursuant to such offer, effective as of the date of sale or deemed sale: (i) the Management Agreement shall terminate with respect to such Non-Economic Facility; (ii) Aggregate Invested Capital shall be reduced by an amount equal to the net proceeds of sale after reduction for the costs and expenses of the relevant TRS, the relevant Owner and/or Manager (or, in the case of a deemed sale, the net proceeds of sale determined by reference to such offer, after reduction for any amounts actually expended and any amounts which would reasonably have been expected to have been expended if the sale had been consummated by the relevant TRS, the relevant Owner and/or Manager). If the reduction in Aggregate Invested Capital is less than the Invested Capital of the Non-Economic Facility sold or deemed to have been sold, the difference shall be proportionately reallocated to the Invested Capital of the remaining Facilities.

  • Complaints Process The School shall establish and adhere to a process for resolving public complaints which shall include an opportunity for complainants to be heard. The final administrative appeal shall be heard by the School's Governing Board, except where the complaint pertains to a possible violation of any law or term under this Contract. The complaints process shall be readily accessible from the School’s website, as described in Section 11.4.1.

  • Grievance Process (a) Either party, with the agreement of the other party, may submit a grievance to Grievance Mediation at any time within ten (10) working days after the Employer’s decision has been rendered at the step prior to arbitration. Where the matter is so referred, the mediation process shall take place before the matter is referred to Arbitrator. (b) Grievance Mediation shall be scheduled within twenty (20) working days of the grievance being submitted to mediation, or longer period as agreed by the parties. (c) No matter may be submitted to Grievance Mediation which has not been properly carried through the grievance procedure, provided that the parties may extend the time limits fixed in the grievance procedure. (d) The parties shall agree on a mediator. (e) Proceedings before the Mediator shall be informal. Accordingly, the rules of evidence will not apply, no record of the proceedings shall be made and legal counsel shall not be used by either party, unless otherwise mutually agreed. (f) If possible, an agreed statement of facts will be provided to the Mediator, and if possible, in advance of the Grievance Mediation Conference. (g) The Mediator will have the authority to meet separately with either party. (h) If no settlement is reached within five (5) working days following Grievance Mediation, the parties are free to submit the matter to Arbitration in accordance with the provisions of the collective agreement. In the event that a grievance which has been mediated subsequently proceeds to arbitration, no person serving as the Mediator may serve as an Arbitrator, unless otherwise mutually agreed. Nothing said or done by the mediator may be referred to Arbitration. (i) The Union and Employer will share the cost of the Mediator, if any.

  • Change Order Process 12.2.1 Contractor shall provide Notice to Owner as soon as practicable, but no later than five (5) Business Days, after the time when Contractor knows of the impact of any Force Majeure Event, Owner Caused Delay or any other basis for a Change Order that will impact the Work. Failure to provide such Notice within ten (10) Business Days after the time when Contractor knows of the impact of any Force Majeure Event shall be deemed to be a waiver of the Contractor’s right to receive a Change Order with respect thereto. Such Notice shall, to the extent practicable, specify the estimated impact on the Target Price and/or the Project Schedule, as applicable, the impact upon the various portions of the Work occasioned by reason of such Force Majeure Event, Owner Caused Delay or any other basis for a Change Order, and shall substantiate the foregoing to the satisfaction of Owner. In the event that Contractor does not know or is unable to specify with reasonable certainty the impact upon the Work at the time such Notice is to be delivered, Contractor shall instead provide Owner with a notice of a potential or anticipated impact of any Force Majeure Event, Owner Caused Delay or any other basis for a Change Order that could impact the Work, and shall thereafter provide Owner (and, if requested by Owner, the Independent Engineer) with periodic supplemental Notices during the period that the Force Majeure Event, Owner Caused Delay or any other basis for a Change Order, as applicable, continues, detailing any developments, progress or other relevant information of which Contractor is aware. To the extent Owner (in consultation with the Independent Engineer with respect to a Material Change) agrees with the Contractor’s determination of a Force Majeure Event or Owner Caused Delay or any other basis for a Change Order, as applicable, and the effects thereof, Owner shall notify Contractor of Owner’s acceptance. In the event Owner (in consultation with the Independent Engineer with respect to a Material Change) does not accept the Contractor’s findings, Owner or Contractor shall be permitted to dispute such Change Order in accordance with Article 36, and Contractor shall be paid for any Work performed in respect of such disputed Change Order as provided in Section 12.2.5. 12.2.2 As soon as practicable, and in any event within fifteen (15) Days (or such other period as is mutually agreed by Owner and Contractor) after receipt from Owner of a request for a change or Notice of Owner’s acceptance under Section 12.2.1, Contractor shall submit to Owner a proposal for implementing the change indicating the estimated change to the Target Price and/or the Project Schedule, as applicable. If Owner (having consulted with the Independent Engineer in the case of a Material Change) agrees that the Contractor’s proposal should be implemented, Owner (having consulted with the Independent Engineer in the case of a Material Change) shall issue a Change Order incorporating such proposal. Upon receiving such Change Order, Contractor shall diligently perform the change in accordance with the terms thereof. 12.2.3 Contractor’s proposal required pursuant to Section 12.2.2 shall consist of: (a) a detailed material take-off with supporting calculations in accordance with the pricing structure herein, for pricing the change, (b) revisions, if any, to the Drawings and Specifications, (c) a schedule for the work associated with the proposed change, (d) the effect, if any, to the Target Price and/or the Project Schedule, as applicable, (e) the effect, if any, of the change on the Work, including the Performance Tests and/or Demonstration Tests (or protocol therefor), (f) changes, if any, to any right, liability or obligation of a Party or any other provision hereof and (g) changes, if applicable, to any Applicable Deadline.

  • CENTRAL GRIEVANCE PROCESS The following process pertains exclusively to grievances on central matters that have been referred to the central process. In accordance with the School Boards Collective Bargaining Act central matters may also be grieved locally, in which case local grievance processes will apply.