1. (1) This rule establishes the Florida Information Technology Project Framework (FL-ITPF), a comprehensive framework for the management, oversight, and Independent Verification and Validation (IV&V) of State and Cabinet Agencies’ (collectively, “Enterprise Agencies”) Information Technology (IT) Projects. The FL-ITPF consists of four phases: Initiating, Planning, Executing, and Closing. This rule sets forth standards, procedures, and documentation requirements to ensure IT Projects are executed effectively, efficiently, and in accordance with state statutes, rules, and best practices.

2. (2) This rule chapter establishes:

   1. (a) In Rule 60GG-1.002, F.A.C., project management standards for State Agencies when implementing IT Projects as outlined in sections 282.0051(1)(c) and (n), F.S., and for Cabinet Agencies as outlined in sections 282.0051(1)(m), (n), and 282.00515(1), F.S.,
   2. (b) In Rule 60GG-1.003, F.A.C., oversight standards for State Agency IT Projects as outlined in section 282.0051(1)(d), F.S., and Cabinet Agency IT Projects as outlined in sections 282.0051(1)(m) and (n), F.S.; and requirements for IV&V.
3. (3) The Department of Management Services, through the Florida Digital Service (“FLDS”), will advise from both planning and technical perspectives within the FL-ITPF and throughout the Project Management lifecycle of IT Projects when performing oversight, as required by law, and upon Enterprise Agency request. Advisement is intended to enhance the Enterprise Agencies' capabilities in Project planning, Risk and Issue management, compliance, and execution, thereby facilitating successful Project outcomes that align IT Projects with the strategic objectives of the state and its citizens. Project management standards and best practices promote transparency, accountability, the optimal use of technology resources, and enhancement to digital services and infrastructure.
4. (4) Documentation requiring submission in accordance with this rule chapter must be submitted to FLDS using the FLDS Gateway which can be accessed at https://www.gateway.digital.fl.gov/.
5. (5) FLDS-03, Calculating Acceptable Variance and Risk Assessment Guidelines, effective 06/2026, and available at HYPERLINK "http://flrules.org/Gateway/reference.asp?No=Ref-19254"
   http://flrules.org/Gateway/reference.asp?No=Ref-19254, is hereby incorporated by reference.

6. (6) Definitions. The following definitions are applicable to all rules under Chapter 60GG-1, F.A.C., and Form FLDS-03, Calculating Acceptable Variance and Risk Assessment Guidelines.

   1. (a) Actual Project Cost – the amount Paid for the work performed on an activity or set of activities.
   2. (b) Baseline – the Enterprise Agency approved version of a Project’s Scope, Schedule, and budget identified in the Project Management Plan. The Baseline can be changed only through a formal Change Control Procedure, as described in the Enterprise Agency’s approved Project Management Plan and with the written approval of the Project sponsor designated by the Enterprise Agency.
   3. (c) Business Day – Monday through Friday, inclusive, excluding those holidays specified in section 110.117, F.S., from 8:00 a.m. to 5:00 p.m.
   4. (d) Cabinet Agency – the Department of Legal Affairs, Department of Agriculture and Consumer Services, and Department of Financial Services.
   5. (e) Change Control Procedure – process whereby modifications to Project documents, deliverables, or Baselines are identified, documented, reviewed, and approved or rejected.
   6. (f) Encumbered – the amount of money or funds obligated through contracts or purchase orders that have not yet been incurred. The date of encumbrance is the date the contract or purchase order is executed.
   7. (g) Enterprise Agencies – State Agencies and Cabinet Agencies to the extent they are subject to the requirements in this rule chapter.
   8. (h) Florida Information Technology Project Framework (“FL-ITPF”) – the series of phases of Information Technology Project Management that includes Initiating, Planning, Executing, and Closing. These phases may overlap.
   9. (i) Independent Verification and Validation (“IV&V”) Services – third-party support services that provide an independent and impartial assessment of progress and work products of an IT Project throughout the Project Management lifecycle. These services must be provided by an entity that does not have technical, managerial, or financial interest in the Project and may not have responsibility for, or participate in, any other aspect of the Project.
   10. (j) Information Technology Project (“Project”) – “information technology” “project” as those terms are defined in section 282.0041, F.S., which includes, but is not limited to, initiatives, programs (i.e.- a group of initiatives managed in a coordinated manner to obtain benefits not available from managing them individually), or portfolios (i.e.- a group of initiatives managed together to achieve strategic business goals).
   11. (k) Information Technology Project Management – the application of knowledge, skills, tools, and techniques to phased FL-ITPF activities to complete the work defined in the Project Management Plan to satisfy the IT Project requirements.
   12. (l) Invoiced – the amount of money or funds that have been billed for contracts and purchase orders but which payment has not yet been issued.
   13. (m) Issue ‒ a current condition or event that may have an impact on the project objectives. An Issue may originate as a Risk or may be previously unidentified.
   14. (n) Key Performance Indicator (KPI) – quantifiable measures used to gauge progress toward strategic or operational goals, to assess performance against expectations, and to make informed decisions. KPIs connect high-level objectives to project activities, helping to track performance, understand areas needing improvement, and determine if the project is achieving its intended value.
   15. (o) Legislative Budget Request (“LBR”) – as defined in section 216.011, F.S.
   16. (p) Milestone – a significant, planned event in a project that marks the completion of a major deliverable or phase, or a critical decision point, rather than the completion of a specific task or duration of time. Milestones have zero duration and require no resources in the project schedule to signify important progress and aid in communication with stakeholders.
   17. (q) Operations and Maintenance – ongoing or recurring activities or efforts performed to sustain, support, operate, or enhance an existing system, service, or capability.
   18. (r) Planned Project Cost – the amount of money or funds that have been budgeted for project expenses. This is also commonly referred to as projected amounts.
   19. (s) Project Management Professional – a certification administered by the Project Management Institute that demonstrates experience, education, and competency to lead and direct projects.
   20. (t) Project Management Plan – the document that describes how the phased Project Management lifecycle activities are performed and governed throughout the Project. The approved Project Management Plan establishes the Scope, Schedule, and budget for completing the work product. The Project Management Plan also includes a detailed breakdown of tasks, requirements and deliverables, and spend plan.
   21. (u) Project Oversight – an independent review and analysis of an IT Project that provides information on the Project’s Scope, status, task completion, timeframes, and budget, and that identifies and quantifies Issues or Risks affecting the successful and timely completion of the Project.
   22. (v) Risk – an uncertain condition or event that, if it occurs, has a positive or negative effect on the IT Project’s Baselined Scope, Schedule, or budget. Once a Risk has been realized, it becomes an Issue.
   23. (w) Schedule – a component of the Project Management Plan that presents time-based and linked activities with planned dates, duration, Milestones, and resources.
   24. (x) Schedule IV-B – the Schedule IV-B form required to be submitted by an Enterprise Agency for IT projects with a Total Project Cost of one million dollars or more as part of an Enterprise Agency’s legislative budget request pursuant to section 216.023, F.S.
   25. (y) Scope – the combined objectives and requirements needed to complete an IT Project. The Scope impacts the critical success factors defined for the IT Project and, when a Schedule IV-B is submitted, must trace the Project charter to the Project Management Plan.
   26. (z) State Agency – as defined in section 282.0041(34), F.S.
   27. (aa) Total Project Cost – any expenditures made or estimated to be made or monetary obligations to be incurred or estimated to be incurred throughout the IT Project as defined in the approved Project Management Plan.
   28. (bb) Variance – as defined in section 282.0041(38), F.S.

Rulemaking Authority 282.0051(6) FS. Law Implemented 282.0041, 282.0051, 282.00515 FS. History‒New 7-16-15, Amended 8-1-16, Formerly 74-1.001, Amended 6-17-26.