Scrum Lifecycle Sample Clauses

Scrum Lifecycle. (1) SAP will designate a contact person (“Product Owner”) to discuss Customer’s Requirements and their priorities. The Product Owner will be responsible for managing the Product Backlog and for assigning the final priorities taking into account Customer’s business needs, the technical feasibility and the dependencies. (2) The Vision & Scope Document and the initial version of the Product Backlog are already available and attached to the applicable Order Form. SAP will start directly with the first Sprint. (3) As a prerequisite for Product Backlog Items to become part of a Sprint, they have to be specified in sufficient detail in the Product Backlog including description, acceptance criteria and prioritization. The SAP Product Owner continuously works together with Customer to break down and refine those Product Backlog Items that are not yet specified to the necessary level of detail. Refined Product Backlog Items result in new versions of the Product Backlog, which SAP submits to Customer for confirmation as described in this Supplement. (4) At the beginning of each Sprint SAP will conduct a planning meeting to decide which Product Backlog Items will be realized as Features by SAP in the Sprint. After the planning meeting SAP will inform Customer of the Sprint Scope. The respective Product Backlog Items are now considered fixed and cannot be altered during the Sprint. (5) At the end of each Sprint a review meeting will take place in which SAP will present to Customer the Features that have been developed during the Sprint. SAP will send via e-mail to Customer minutes of the Sprint review meeting for Customer to confirm. The minutes will reflect the Product Backlog Items that SAP considers completed and Customer’s objections to the demonstrated Features, if any. Customer must confirm or reject the Sprint review meeting minutes via e- mail within a period of five working days as of their submission. Customer’s confirmation or rejection must be based on the description of the Product Backlog Item and on the corresponding acceptance criteria. If Customer confirms or does not reject via e-mail the minutes of the Sprint review meeting within the five working days, the completed Product Backlog Items will move to status “confirmed”. As far as a Product Backlog Item is rejected, the status will remain “in progress“ and necessary adjustments will be made during one of the upcoming development Sprints, or latest during the integration test. (6) During the Build Pha...
Sample 1Sample 2Sample 3See All (58)
AutoNDA by SimpleDocs
Scrum Lifecycle. Scrum 生命週期 (1) SAP will designate a contact person (“Product Owner”) to discuss Customer Requirements and their priorities. The Product Owner will be responsible for managing the Product Backlog and for assigning the final priorities taking into account Customer’s business needs, the technical feasibility and the dependencies. SAP 將會指定一名聯絡人員 (「產品擁有人」)，以討論客戶需求及其優先順序。產品擁有人負責管理產品未交貨訂單，並考量客戶的業務需要、技術可行性和依賴性來指派最終優先順序。 (2) According to the Scrum Lifecycle SAP will start the development of the Features based on the initial version of the Product Backlog. SAP 會根據 Scrum 生命週期，以產品未交貨訂單的初始版本為基礎開始執行特性開發作業。 a) If no initial version of the Product Backlog is available, SAP will create the initial version of the Product Backlog based on the Customer Requirements as described in the Solution Proposal attached to the applicable Order Form. The initial version of the Product Backlog must be formally accepted by Customer. The first Sprint starts after acceptance of the initial version of the Product Backlog. 若無可用的產品未交貨訂單初始版本，SAP 將會根據適用訂購單所檢附方案建議書中述及的客戶需求，建立產品未交貨訂單的初始版本。產品未交貨訂單的初始版本必須獲得客戶正式同意。客戶同意產品未交貨訂單的初始版本後，即會開始執行第一次衝刺 (Sprint)。 b) If the initial version of the Product Backlog is already available, it will be attached to the applicable Order Form and SAP will start directly with the first Sprint. 若已提供產品未交貨訂單的初始版本，則其會附加至適用的訂購單，且 SAP 會直接開始執行第一次衝刺 (Sprint)。 (3) As a prerequisite for Product Backlog Items to become part of a Sprint, they have to be specified in sufficient detail in the Product Backlog including description, acceptance criteria and prioritization. The SAP Product Owner continuously works together with Customer to break down and refine those Product Backlog Items that are not yet specified to the necessary level of detail. Refined Product Backlog Items result in new versions of the Product Backlog, which SAP submits to Customer for confirmation as described in this Supplement. 讓產品未交貨訂單項目成為衝刺 (Sprint) 一部分的先決條件，即是必須在產品未交貨訂單中充分詳盡地指定這些項目，包括說明、驗收標準和優先順序。SAP 產品擁有人會持續與客戶共同合作細分和研擬這些未指定所需細節程度的產品未交貨訂單項目。經過研擬的產品未交貨訂單項目，會產生新版本的產品未交貨訂單，SAP會按照本補充條款中所述，將其提交給客戶確認。 (4) At the beginning of each Sprint SAP will conduct a planning meeting to decide which Product Backlog Items will be realized as Features by SAP in the Sprint. After the planning meeting SAP will inform Customer of the Sprint Scope. The respective Product Backlog Items are now considered fixed and cannot be altered during the Sprint. SAP 會在每次衝刺 (Sprint) 開始時實行規劃會議，以決定 SAP 要在衝刺 (Sprint) 中實現哪些產品未交貨訂單項目作為特性。規劃會議結束後，SAP 會向客...
Sample 1

Related to Scrum Lifecycle

  • API If the Software offers integration capabilities via an API, your use of the API may be subject to additional costs or Sage specific policies and terms and conditions (which shall prevail in relation to your use of the API). You may not access or use the API in any way that could cause damage to us or the Software, or in contravention of any applicable laws. We reserve the right in our sole discretion, to: (i) update any API from time to time; (ii) place limitations around your use of any API; and (iii) deny you access to any API in the event of misuse by you or to otherwise protect our legitimate interests.

  • Innovative Scheduling Schedules which are inconsistent with the Collective Agreement provisions may be developed in order to improve quality of working life, support continuity of resident care, ensure adequate staffing resources, and support cost-efficiency. The parties agree that such innovative schedules may be determined locally by the Home and the Union subject to the following principles: (a) Such schedules shall be established by mutual agreement of the Home and the Union; (b) These schedules may pertain to full-time and/or part-time employees; (c) The introduction of such schedules and trial periods, if any, shall be determined by the local parties. Such schedules may be discontinued by either party with notice as determined through local negotiations; (d) Upon written agreement of the Home and the Union, the parties may agree to amend collective agreement provisions to accommodate any innovative unit schedules; (e) It is understood and agreed that these arrangements are based on individual circumstances and each agreement is made on a without prejudice or precedent basis. (f) It is understood and agreed that these arrangements can be utilized for temporary job postings for seasonal coverage (e.g. weekend workers, etc.).

  • PRODUCT MANUFACTURER'S SUPPLIERS Only those dealers/distributors listed by the manufacturer will be considered authorized to act on behalf of the Product Manufacturer.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Xxxx has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Xxxx. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Xxxx (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Xxxx, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Xxxx will then have the option of paying the one-time SC rates to place the Loop.

  • Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.

  • Synchronization, Commissioning and Commercial Operation 4.1.1 The Power Producer shall give at least fifteen (15) days written notice to the SLDC / ALDC / DISCOM as the case may be, of the date on which it intends to synchronize the Power Project to the Grid System. 4.1.2 Subject to Article 4.1.1, the Power Project may be synchronized by the Power Producer to the Grid System when it meets all the connection conditions prescribed in the Grid Code and otherwise meets all other Indian legal requirements for synchronization to the Grid System. 4.1.3 The synchronization equipment and all necessary arrangements / equipment including Remote Terminal Unit (RTU) for scheduling of power generated from the Project and transmission of data to the concerned authority as per applicable regulation shall be installed by the Power Producer at its generation facility of the Power Project at its own cost. The Power Producer shall synchronize its system with the Grid System only after the approval of GETCO / SLDC / ALDC and GEDA. 4.1.4 The Power Producer shall immediately after each synchronization / tripping of generator, inform the sub-station of the Grid System to which the Power Project is electrically connected in accordance with applicable Grid Code. 4.1.5 The Power Producer shall commission the Project within SCOD. 4.1.6 The Power Producer shall be required to obtain Developer and/ or Transfer Permission, Key Plan drawing etc, if required, from GEDA. In cases of conversion of land from Agricultural to Non-Agriculture, the commissioning shall be taken up by GEDA only upon submission of N.A. permission by the Power Producer. 4.1.7 The Power Producer shall be required to follow the Forecasting and Scheduling procedures as per the Regulations issued by Hon’ble GERC from time to time. It is to clarify that in terms of GERC (Forecasting, Scheduling, Deviation Settlement and Related Matters of Solar and Wind Generation Sources) Regulations, 2019 the procedures for Forecasting, Scheduling & Deviation Settlment are applicable to all solar generators having combined installed capacity above 1 MW connected to the State Grid / Substation including those connected via pooling stations.

  • COVID-19 Vaccine Passports Pursuant to Texas Health and Safety Code, Section 161.0085(c), Contractor certifies that it does not require its customers to provide any documentation certifying the customer’s COVID-19 vaccination or post-transmission recovery on entry to, to gain access to, or to receive service from the Contractor’s business. Contractor acknowledges that such a vaccine or recovery requirement would make Contractor ineligible for a state-funded contract.

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • Alignment with Modernization Foundational Programs and Foundational Capabilities The activities and services that the LPHA has agreed to deliver under this Program Element align with Foundational Programs and Foundational Capabilities and the public health accountability metrics (if applicable), as follows (see Oregon’s Public Health Modernization Manual, (xxxx://xxx.xxxxxx.xxx/oha/PH/ABOUT/TASKFORCE/Documents/public_health_modernization_man ual.pdf): a. Foundational Programs and Capabilities (As specified in Public Health Modernization Manual) b. The work in this Program Element helps Oregon’s governmental public health system achieve the following Public Health Accountability Metric: c. The work in this Program Element helps Oregon’s governmental public health system achieve the following Public Health Modernization Process Measure:

  • Transporting Students 1. Employees shall not transport students except in accordance with School Board rules. The Board shall adopt a school board policy outlining the teacher’s and the Board’s responsibilities and liabilities. Said policy shall be included in all school handbooks beginning with the 2004-05 school year. 2. Teachers will not be required to transport pupils to and from activities which take place away from the school grounds.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!