Scrum Lifecycle Clause Samples

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...
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 會向客...

Related to Scrum Lifecycle

  • Loss Leader; Recycled Products Contractor shall not sell or use any article or product as a “loss leader” as defined in Section 17030 of the Business and Professions Code. If Contractor will sell to the Judicial Council, or use in the performance of this Agreement, goods specified in PCC 12207 (for example, certain paper products, office supplies, mulch, glass products, lubricating oils, plastic products, paint, antifreeze, tires and tire-derived products, and metal products), then with respect to those goods: (i) Contractor shall use recycled products in the performance of this Agreement to the maximum extent doing so is economically feasible, and (ii) upon request, Contractor shall certify in writing under penalty of perjury, the minimum, if not exact, percentage of post consumer material as defined in the PCC 12200, in such goods regardless of whether the goods meet the requirements of PCC 12209.

  • 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.