Page 618

section. The statewide dashboard must meet the requirements in 1 section 155 of this act. 2 (8) For any project that exceeds $2,000,000 in total funds to 3 complete, requires more than one biennium to complete, or is financed 4 through financial contracts, bonds, or other indebtedness: 5 (a) Independent quality assurance services for the project must 6 report independently to the office of the chief information officer; 7 (b) The office of the chief information officer, based on project 8 risk assessments, may require additional quality assurance services 9 and independent verification and validation services; 10 (c) The office of the chief information officer must review, and, 11 if necessary, revise the proposed project to ensure it is flexible 12 and adaptable to advances in technology; 13 (d) The technology budget must specifically identify the uses of 14 any financing proceeds. No more than thirty percent of the financing 15 proceeds may be used for payroll-related costs for state employees 16 assigned to project management, installation, testing, or training; 17 (e) The agency must consult with the office of the state 18 treasurer during the competitive procurement process to evaluate 19 early in the process whether products and services to be solicited 20 and the responsive bids from a solicitation may be financed; 21 (f) The agency must consult with the contracting division of the 22 department of enterprise services for a review of all contracts and 23 agreements related to the project's information technology 24 procurements; 25 (g) The agency and project must use an agile development model 26 holding live demonstrations of functioning software, developed using 27 incremental user research, held at the end of every two-week sprint; 28 (h) The project solution must be capable of being continually 29 updated, as necessary; and 30 (i) The agency and project must deploy usable functionality into 31 production for users within 180 days from the date of an executed 32 procurement contract in response to a competitive request for 33 proposal. 34 (9) The office of the chief information officer must evaluate the 35 project at each stage and certify whether the project is putting 36 functioning software into production that addresses user needs, is 37 projected to be completed within budget, is in compliance with the 38 quality assurance plan, and meets a defined set of industry best 39 practices for code quality, and whether the project is planned, 40 p. 617 ESSB 5187.SL