Page 616

provide a statewide impact by agency by fund as a worksheet in the 1 technology budget file; 2 (ii) Full time equivalent staffing level to include job 3 classification assumptions. This is to assure that the project has 4 adequate state staffing and agency support to ensure success, ensure 5 user acceptance, and adequately test the functionality being 6 delivered in each sprint before it is accepted by the agency's 7 contracting officer or their representative. Key project functions 8 that are deemed "critical" must be retained by state personnel and 9 not outsourced, to ensure that knowledge is retained within state 10 government and that the state can self-sufficiently support the 11 system and make improvements without long-term dependence on a 12 vendor; 13 (iii) Discrete financial budget codes to include at least the 14 appropriation index and program index; 15 (iv) Object and subobject codes of expenditures; 16 (v) Anticipated deliverables to include software demonstration 17 dates; 18 (vi) Historical budget and expenditure detail by fiscal year; and 19 (vii) Maintenance and operations costs by fiscal year for at 20 least five years as a separate worksheet. 21 (c) If a project technology budget changes and a revised 22 technology budget is completed, a comparison of the revised 23 technology budget to the last approved technology budget must be 24 posted to the dashboard, to include a narrative rationale on what 25 changed, why, and how that impacts the project in scope, budget, and 26 schedule. 27 (5)(a) Each project must have a project charter. The charter must 28 include: 29 (i) An organizational chart of the project management team that 30 identifies team members and their roles and responsibilities, and 31 shows that the project is adequately staffed by state personnel in 32 key functions to ensure success; 33 (ii) The office of the chief information officer staff assigned 34 to the project; 35 (iii) A project roadmap that includes the problems the team is 36 solving and the sequence in which the team intends to take on those 37 problems, updated periodically to reflect what has been learned; 38 (iv) Metrics to support the project strategy and vision, to 39 determine that the project is incrementally meeting user needs; 40 p. 615 ESSB 5187.SL