This standard will ensure accountability for the resources allocated to information technology (IT) projects and ensure that a consistent approach will be used to manage IT projects throughout the project management life cycle.
All information technology projects shall comply with the following directives:
1. The North Dakota Project Management Guidebook must be leveraged as guidance for best practices in how to manage a project.
2. A project repository must be maintained by the performing organization to manage and retain critical project documents. If the performing organization chooses to manage documents electronically, the following provisions must be followed:
2.1. Documents must be stored on a secured environment owned by the state.
2.2. Performing organizations may choose to allow vendors to manage documents on a privately owned project management/document management system if there is a contractual provision to provide the performing organization with a download of all relevant documentation in periodic increments not to exceed 30 days.
2.3. Documentation to be retained in repository includes:
2.3.1. All documents identified in this standard.
2.3.2. Products of project management which may include meeting minutes, scope changes, deliverable/project acceptance, risk logs, issue logs, quality related documents, budgets, variance reports, recovery plans, schedules, project status reports, RFI/RFP, and contracts (including all attachments/addendums), and relevant email communications.
2.3.3. Upon completion, all documentation must be retained for a period of no less than 3 years.
2.3.4. Agencies may choose to establish individual records retention policies that include the same or greater documentation requirements and a retention schedule of no less than 3 years.
All information technology projects with budgets of $250,000 and over shall comply with the following additional directives:
3. An executive steering committee (ESC) shall be established to provide management support to the project.
3.1. The committee members shall include at a minimum, the project manager, project sponsor, executive level business owners, and optionally, executive-level vendor representation.
3.2. The committee shall be responsible for reviewing the status at project milestones, authorizing significant changes to the project plan, and facilitating decision-making.
3.3. For projects with budgets of $500,000 and over (defined by Century Code as “Major Information Technology Projects”), the composition and responsibilities of the ESC are specifically defined in N.D.C.C. § 54-59-32.
3.4. The committee shall meet quarterly, or on a more frequent basis as defined by the membership of the ESC.
4. A Project Manager must be assigned to manage the project.
4.1. When assigning a project manager, agencies shall consider the qualifications necessary to manage the project’s size, scope, and complexity.
4.2. Project managers assigned to projects with budgets of $500,000 and over must meet qualifications established by the Information Technology Department and the Office of Management and Budget (N.D.C.C. § 54-59-32).
5. A project charter shall be developed and executed to initiate the project and to secure commitment for the resources (e.g., human, financial, equipment) necessary for the project.
5.1. The project charter shall minimally include the following information: project description/background, business need/problem, proposed solution, consistency/fit with the organization’s mission, cost/benefit analysis, risks, scope, objective(s), required planning resources, constraints, assumptions, and project authority. The project charter shall be completed prior to entering the planning or execution phases. Additional information and a template can be found in the ND Project Management Guidebook (see Guidance section).
5.2. The ESC shall formally approve the project charter.
5.3. For projects with budgets of $500,000 and over:
5.3.1. Prior to submission to the ESC, the ITD Oversight Analyst (OA) assigned to the project shall review the charter for general compliance with directive 5.1 and provide comments to the ESC.
5.3.2. After approval by the ESC, and prior to any planning or execution activities a copy of the project charter shall be submitted to the OA assigned to the project.
5.3.3. Prior to signing vendor contracts or accruing project expenditures for planning and execution phases, a copy (electronic) of the approved project charter shall be submitted to the OA assigned to the project.
6. A project plan shall be developed as the primary planning document for the project.
6.1. The project plan shall follow the guidelines of the Project Management Institute’s (PMI) Project Management Body of Knowledge (PMBOK), and address all management sections as defined in the ND Project Management Guidebook and Project Plan Template.
6.2. The project plan shall identify specific milestones throughout the project and their associated cost, schedule, and any associated phase and deliverables.
6.3. The ESC shall formally approve the project plan.
6.4. For projects with budgets of $500,000 and over:
6.4.1. Prior to submission to the ESC, the OA assigned to the project shall review the project plan for general compliance with directive 6.1 and 6.2, and provide comments to the ESC.
6.4.2. After approval by the ESC, a copy of the project plan shall be submitted to the OA assigned to the project.
6.4.3. A Project Startup Report shall be prepared.
126.96.36.199. The intent of this document is to convey information gleaned from the project charter and project plan to the Legislative IT Committee at the time when the project has completed the planning process and is entering the execution phase (the information contained in this document should not be new. It should be taken from the existing referenced documents).
188.8.131.52. The reported budget and schedule will be used to calculate variance during execution of the project.
184.108.40.206. This report is due within 30 days of submission of the final project plan and is submitted to the OA assigned to the project.
7. A project status report must be prepared at least monthly. The report should include an executive summary, budget and schedule (including progress against budget and schedule baselines), issues, risks, project accomplishments and upcoming activities.
7.1. Throughout the life of the project, if changes occur which would impact the project objectives as stated in the original project charter, or changes to cost, schedule, scope or quality as defined in the project plan, those impacts shall be included in the project status report.
7.2. Revised budget or schedule baselines will be based only upon scope changes (add or remove) that could not have reasonably been foreseen during the planning phase.
7.3. For projects with budgets of $500,000 and over:
7.3.1. Unless an alternative method is approved, all projects will utilize the most current version of the ND variance worksheet to calculate budget and schedule variance.
7.3.2. This baseline copy of the ND variance worksheet is due no later than 10 working days after the first day of project execution.
7.3.3. Variance to budget or schedule will be measured for the duration of the execution phase of the project and will not include initiation, planning, or closing phases.
7.3.4. The project status report and variance worksheet shall be submitted to the OA on a quarterly basis.
8. The Chief Information Officer shall create a Major Project Summary Report (for projects with budgets of $500,000 and over), which summarizes the performance of Major IT projects, and submit it to the State Information Technology Advisory Committee and the Legislative Council once per quarter.
9. A Post Implementation Review (PIR) shall be performed by the agency within six months of reaching the execution complete milestone in order to assess the success of the project and to capture historical information.
9.1. The PIR shall minimally include a review and summary of lessons learned, success stories, product effectiveness, CSSQ management, risk management, communications management, acceptance management, organizational change management, issues management, project implementation and transition, performance of the performing organization, and key project metrics (e.g., cost, schedule, scope, quality).
9.2. The ESC shall formally approve the PIR.
9.3. For projects with budgets of $500,000 and over:
9.3.1. Prior to submission to the ESC, the OA assigned to the project shall review the PIR for general compliance with directive 9.1 and provide comments to the ESC.
9.3.2. After approval by the ESC, a copy of the PIR shall be submitted to the OA assigned to the project.
10. For projects with budgets of $500,000 and over, a Project Closeout Report shall be created.
10.1.The intent of this document is to convey information gleaned from the Post Implementation Report to the Legislative IT Committee at the time when the project has completed the closeout phase (the information contained in this document should not be new. It should be taken from the existing referenced documents).
10.2.Variance to both the original planned and final approved budget and schedule will be calculated.
10.3.This report is due within 30 days of submission of the post implementation report.
10.4.The ESC shall formally approve the closeout report.
10.5.Prior to submission to the ESC, the OA assigned to the project shall review the closeout reports for general compliance with directive 10.1 and provide comments to the ESC.
10.6.After approval by the ESC, a copy of the PIR shall be submitted to the OA assigned to the project.
Projects are by definition a temporary endeavor undertaken to create a unique, technology-based product, service, or result. Due to the nature and scale of the projects defined as IT projects, it is critical that project management practices be employed and that processes are in place, increasing the probability of delivering quality products, on time and within budget.
According to North Dakota Century Code this standard applies to all executive, legislative, and judicial branch agencies. Applicable code includes: NDCC 54-10-28, NDCC 54-35-15, NDCC 54-59-05.7-8, NDCC 54-59-09, NDCC 54-59-23, NDCC 54-39-32.
The State Board of Higher Education will maintain a separate standard in accordance with NDCC 15-10-44.
1. Acceptance Management – (Post Implementation Report) – This section of the report is intended to capture how the acceptance processes were managed during the project.
2. Assumptions – (Project Charter) A list of factors, for planning purposes, which are known to be true, real, or certain without proof or demonstration. Assumptions generally involve a degree of risk. (PMI – CSG 3rd Ed)
3. Authority – (Project Charter) The right to apply project resources, expend funds, make decisions, or give approvals. (PMI – CSG 3rd Ed)
4. Business Need/Problem – (Project Charter) Those issues identified as driving the proposed project.
5. CSSQ Management – (Post Implementation Report) – This section of the report is intended to capture how the cost, schedule, scope, and quality processes were managed during the project.
6. Closing Phase – The process of finalizing all activities to formally close the project or phase.
7. Communications Management Plan – (Project Plan) The document that describes: the communications needs and expectations for the project; how and in what format information will be communicated; when and where each communication will be made; and who is responsible for providing each type of communication. (PMI – CSG 3rd Ed)
8. Consistency/Fit within the Organization’s Mission – (Project Charter) How the proposed project will fit within the agency’s mission and/or strategic plan.
9. Constraints – (Project Charter) The state, quality, or sense of being restricted to a given course of action or inaction. An applicable restriction or limitation, either internal or external to the project, that will affect the performance of the project or a process. (PMI – CSG 3rd Ed)
10. Cost/Benefit Analysis – (Project Charter) A dynamic review of the estimated cost, anticipated benefits, and a quantitative analysis justifying the costs for the anticipated benefits.
11. Cost Management Plan– (Project Plan) The document that sets out the format and establishes the activities and criteria for planning, structuring, and controlling the project costs. (PMI – CSG 3rd Ed)
12. Deliverable - Any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project. Often used more narrowly in reference to an external deliverable, which is a deliverable that is subject to approval by the project sponsor or customer. (PMI – CSG 3rd Ed)
13. Execution Phase – The processes performed to complete the work defined in the project management plan to satisfy the project objectives.
14. Human Resource/Staffing Management Plan – (Project Plan) The process of identifying and documenting project roles, responsibilities and reporting relationships, as well as creating the staffing management plan (staffing management describes when and how human resource requirements will be met). (PMI – CSG 3rd Ed)
15. Initiation Phase – The processes performed to define a new project or a new phase of an existing project by obtaining authorization to start the project or phase.
16. Integrated Change Control Plan – (Project Plan) The process of reviewing all change requests, approving changes and controlling changes to deliverables and organizational process assets. (PMI – CSG 3rd Ed)
17. Issues Management – (Post Implementation Report) - This section of the report is intended to capture how project issues were managed during the project.
18. Issues Management Plan – (Project Plan) - The document describing how issues management will be structured and performed on the project. The issues management plan is different from the issues log that contains the list of ongoing issues to be managed during the execution of the project.
19. Key Project Metrics (Cost, Schedule, Scope, Quality, Objectives) – (Post Implementation Report) – This section of the report is intended to capture specific data related to the original and final metrics of cost, schedule, scope, quality, and objectives as related to the project plan.
20. Milestone – A significant point or event in the project. (PMI – CSG 3rd Ed)
21. Objectives – (Project Charter) Something toward which work is to be directed, a strategic position to be attained, or a purpose to be achieved, a result to be obtained, a product to be produced, or a service to be performed. (PMI – CSG 3rd Ed)
22. Organizational Change Management Plan – (Project Plan) – includes processes and tools for managing the people side of the change at an organizational level. These tools include a structured approach that can be used to effectively transition groups or organizations through change.
23. Performance of the Performing Organization – (Post Implementation Report) – This section is intended to capture information related to the performance of the organization as it relates to the success of the project.
24. Planning Phase – Processes performed to establish the total scope of the effort , define and redefine the objectives, and develop the course of action required to obtain those objectives.
25. Planning Process – The planning process is considered complete when the sponsor, project manager, and project team agree that the work to be completed has been decomposed to a level wherein the scope can be delivered and the business objectives of the project met. Management plans should allow the execution of the work to be managed in a controlled manner. Execution related work may not begin until the planning process is complete.
26. Procurement Management Plan – (Project Plan) The document that describes how procurement processes from developing procurement documentation through contract closure will be managed. (PMI – CSG 3rd Ed)
27. Project Background – (Project Charter) - This section describes, in a manner that the typical Executive Steering Committee member will be able to understand, the history of the project to date. Inputs to this section include information gathered from the business case (if one exists), from previous, related projects, business strategy documents and any other relevant business documentation.
28. Project Description – (Project Charter) - An initial review of the project objectives.
29. Product Effectiveness – (Post Implementation Report) – This section contains a general review of how the product is performing during post implementation. Success stories may be outputs of this portion of the review.
30. Project Implementation and Transition Plan – (Project Plan) - This section includes a description of the high level elements required to successfully transition the project.
31. Project Management – The application of knowledge, skills, tools, and techniques to project activities to meet the project requirements. (PMI – CSG 3rd Ed)
32. Project Management Life Cycle – A collection of sequential project phases that detail specific processes to be performed within each phase, and define the tasks that comprise each process. The life cycle phases include: Initiation, Planning, Execution and Control, Closing.
33. Project Management Plan – (Project Plan) – A formal, approved document that defines how the project is executed, monitored and controlled. It may be summary or detailed and may be composed of one or more subsidiary management plans or other planning documents. (PMI – CSG 3rd Ed)
34. Proposed Solution – (Project Charter) The product of the project that would resolve the Business Need/Problem.
35. Quality Management Plan – (Project Plan) The quality management plan describes how the project management team will implement the performing organization’s quality policy. (PMI – CSG 3rd Ed)
36. Required Resources – (Project Charter) Skilled human resources (specific disciplines either individually or in crews or teams), equipment, services, supplies, commodities, materials, budgets, or funds. (PMI – CSG 3rd Ed)
37. Risks – (Project Charter) An uncertain event or condition that, if it occurs, has a positive or negative effect on a project’s objectives. (PMI – CSG 3rd Ed)
38. Risk Management – (Post Implementation Report) – This section of the report is intended to capture how project risks were managed during the project.
39. Risk Management Plan – (Project Plan) The document describing how risk management will be structured and performed on the project. The risk management plan is different from the risk register that contains the list of project risks, the results of risk analysis, and the risk responses. (PMI – CSG 3rd Ed)
40. Scope – (Project Charter) The sum of the products, services, and results to be provided as a project. (PMI – CSG 3rd Ed)
41. Sponsor – The person or group that provides the financial resources, in cash or in kind, for the project. (PMI – CSG 3rd Ed)
42. Schedule Management Plan – (Project Plan) The document that establishes criteria and the activities for developing and controlling the project schedule. (PMI – CSG 3rd Ed)
43. Scope Management Plan – (Project Plan) The document describing how scope will be managed and controlled on the project.
44. Trained Project Manager – All project managers must have a minimum of 24 contact hours of project management specific training. Holding the PMP, CompTIA Project + or CAPM certification will substitute for the minimum training requirement.
ND Project Management Guidebook: http://www.nd.gov/itd/files/legacy/services/pm/project-management-guidebook.pdf; http://www.nd.gov/itd/content/north-dakota-project-management-guidebook
The Project Management Body of Knowledge (PMBOK), Project Management Institute (PMI): http://www.pmi.org
N.D.C.C. § 54-59-32 Major Information Technology Projects – Appointment of executive steering committees
Non-compliance of this standard shall be reported to the State Auditor’s Office and the Legislative Council. Non-compliance may result in non-approval of any IT expenditures associated with the project.
Project Management Office
Project Management Oversight monitors and guides information technology projects with a budget in excess of $100,000.
Project Management as a contracted service provides customers with qualified project managers that will lead agency IT projects using Customized Project Management Tools and Templates.
A project is a temporary endeavor undertaken to create a unique product, service, or result. Project Management is the application of knowledge, skills, tools, and techniques to project activities to meet the project requirements.