Methodology Lifecycles Clause Samples
The 'Methodology Lifecycles' clause defines the process by which methodologies used in a project or agreement are established, maintained, updated, and retired. It typically outlines the criteria for introducing new methodologies, the procedures for reviewing and updating existing ones, and the steps for phasing out outdated approaches. For example, it may specify that methodologies must be reviewed annually or that changes require stakeholder approval. This clause ensures that all parties are aligned on how methodologies evolve over time, promoting consistency, adaptability, and quality control throughout the project's duration.
Methodology Lifecycles. The Features will be developed applying one of the Methodology Lifecycles described below. The applicable Methodology Lifecycle is specified in the applicable Order Form.
Methodology Lifecycles. 方法生命週期。 The Features will be developed applying one of the Methodology Lifecycles described below. The applicable Methodology Lifecycle is specified in the applicable Order Form. 開發功能時將會套用以下所述的其中一種方法生命週期。在適用訂購單中，會指定適用的方法生命週期。
(a) 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 plann...
Methodology Lifecycles