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.
View SourceView Similar (58)
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...
View Source
Methodology Lifecycles 
View Source

Related to Methodology Lifecycles

  • Methodology 1. The price at which the Assuming Institution sells or disposes of Qualified Financial Contracts will be deemed to be the fair market value of such contracts, if such sale or disposition occurs at prevailing market rates within a predefined timetable as agreed upon by the Assuming Institution and the Receiver. 2. In valuing all other Qualified Financial Contracts, the following principles will apply:

  • Parameters In calculating the MtM Exposure for each Transaction, the following parameters are set on the Transaction Date: ▪ On-Peak Initial ▇▇▇▇ ▇▇▇▇▇ ▪ Off-Peak/On-Peak Price Ratio ▪ Off-Peak Initial ▇▇▇▇ ▇▇▇▇▇ ▪ MW-Measure: initial Capacity PLC Per Tranche ▪ On-Peak Estimated Energy Quantity Per MW-Measure for each of the twelve calendar months ▪ Off-Peak Estimated Energy Quantity Per MW-Measure for each of the twelve calendar months ▪ Number of awarded Tranches In calculating the MtM Exposure for each Transaction, the following parameters are set each Business Day subsequent to the Transaction Date: ▪ On-Peak Forward Price ▪ Off-Peak Forward Price ▪ Current Capacity PLC Per Tranche ▪ On-Peak Estimated Energy Quantity ▪ Off-Peak Estimated Energy Quantity Process to Update the On-Peak Initial Mark Prices and Off-Peak Initial Mark Prices on a Daily Basis On each Business Day subsequent to the Transaction Date, the Pricing Agent will contact four Reference Market-Makers to obtain price quotes for on-peak and off-peak energy for PJM Western Hub. The Pricing Agent may not rely upon quotes from Seller or any Affiliate of Seller. The updated mark for a month will be equal to the average mark for that month over all sources from which a quote is available. If a monthly quote is available from any source, only the monthly quote or monthly quotes shall be used. Where quotes provide a bid and ask, the average shall be used. Where a quote for an individual month is unavailable, but the month is quoted as part of a “packaged” quote (e.g., January 2011 is only available in the form of a January/February 2011 “packaged” quote or an annual quote): ▪ If the other month/months of the package quote is/are also unavailable, then the marks for all months of the package will be calculated by multiplying the packaged quote by the ratio of the corresponding month to the corresponding calculated package quote from the previous day. Example: There are no On-Peak quotes available on day X during the contract for July 2011 or August 2011. However, there is an On-Peak July/August 2011 packaged quote of $73.00/MWh available. The On-Peak marks from day X-1 for July 2011 and August 2011 were $73.50/MWh and $76.50/MWh respectively. The day X On-Peak mark for July 2011 is set at 73.00 * [73.50] / [( (73.50 * 352) + (76.50 * 336) ) / (352+336) ] = 73 * (73.50/ 74.97) = $71.57/MWh. The day X On-Peak mark for August 2011 is set at 73.00 * [76.50] / [( (73.50 * 352) + (76.50*336) ) / (352+336) ] = 73 * (76.50 / 74.97) = $74.49/MWh. ▪ If the other month/months of the package quote is/are available, then the mark for the month will be set such that the average of the month and the other month(s) (weighted for either the On-Peak Hours or Off-Peak Hours as applicable) equals the packaged quote (see calculation example below).

  • Scoring The number of routes each company operates (Route # 0001-2999, 8000-8199) will be multiplied by 2 to determine the daily number of trips. (Only accidents, breakdowns and service reports related to routes falling in this range will be used for the evaluation). The daily number of trips will be multiplied by 175 to arrive at the annual number of trips. The number of accidents, breakdowns and service complaints will be divided by the total number of trips to calculate a percent figure. Each company’s percentage will be compared to the total average. See below for a sample. BUS COMPANY NUMBER OF TOTAL BKDN PERCENT ACCIDENTS PERCENT2 SERVICE PERCENT3 ROUTES TRIPS BKDN ACCIDENTS REPORTS COMPLAINTS TO TRIPS TO TRIPS TO TRIPS A 360 58680 3 0.01% 27 0.05% 46 0.08% B 48 7824 3 0.04% 4 0.05% 39 0.50% C 123 20049 11 0.05% 9 0.04% 27 0.13% D 91 14833 0.00% 10 0.07% 11 0.07% E 124 20212 20 0.10% 19 0.09% 18 0.09% TOTALS 746 121598 37 0.03% 69 0.06% 141 0.12% To score, if a company’s percentage is less than or equal to the total percentage for that category, the company will be awarded 6 points per category. Percentages greater than the total percentage for each distinct category (Accident, Breakdown, Service Complaints) will be scored according to the following scale: Less than-Equal to Ave. 6 points 0-3% above average 5 points 4-7% above average 4 points 5-8% above average 3 points 9-12% above average 2 points 13-16% 1 points Greater than 17% 0 points Any circumstance whereby a Breakdown or Accident is found by PTS to be ‘Non Reported’ by vendor within the required timeframe (see G-36) will count as (20) ‘Reported’ instances for the purpose of this Contractor Evaluation Scoring.