Standard for information technology project management

Project Management Methodology/Life Cycle Overview

Initiation Processes
  • Agree to a vision for the project, define the major goals & project justification (why do this project).
  • Bring together the core team members and the stakeholders.
  • Assign a project manager and establish others' roles and responsibilities.
  • As much as possible, identify the resources needed, the cost estimates, and a broad timeline.
  • Complete the IT Project Initiation Form.
  • Obtain approval to move forward with detailed planning.
Planning Processes
  • Collect requirements as needed. Some options include, focus group sessions, stated stakeholder requirements, and surveys.
  • Begin developing the project scope by describing, in sufficient detail, the projects deliverables and the work required to accomplish those deliverables.
  • Review the project level indicators to aid in assessing project risk level.
  • Use the project scorecard as an aid is assessing project complexity and risk level and thus the rigor and detail of planning, documentation, and approvals necessary.
  • Begin development of a work plan that details the activities or tasks required, including time and cost estimates.
  • Determine resources and staffing needs (resources can be special skills, hardware, software, services, etc.)
  • Identify special skills needed to accomplish project tasks.
  • Assess project procurement needs of goods and services and determine best course of action.
  • Develop a budget plan to include the life cycle cost or total cost of ownership, projected out 3-5 years.
  • Assess the communication needs and prepare a communication plan if required.
  • Perform a risk assessment, analysis, and plan, if required, and include mitigation options as appropriate.
  • Assess the security issues for the project and its deliverable(s). Send a completed IT project security initial review form to the IT Security Office.
  • Analyze testing needs and plan accordingly.
  • Assess training needs and develop a strategy or plan as appropriate.
  • Plan for project changes and how they are documented and submitted, responsibilities, and steering committee membership.
  • Plan for project quality management including a strategy, quality assurance, and quality control activities.
  • Analyze need for independent verification & validation (IV&V) and plan accordingly.
  • Complete the scope document that includes how to verify completion of deliverables and how to manage scope change requests.
  • Document any lessons learned up to this stage in the project.
  • Obtain approval to move forward with executing the project plan.
Executing Processes
  • Assemble and develop the project team (training, etc.).
  • Procure or secure required resources (hardware, services, software, etc.).
  • Review security plan with project team. Make sure security issues are prominent and addressed.
  • Implement quality assurance procedures.
  • Make project information and status available to stakeholders.
Monitoring/Controlling Processes
  • Change control and management - modifications of original project scope, cost, schedule and technical strategies.
  • Direct and lead the project team.
  • Manage project progress.
  • Implement quality control plan.
  • As required, implement independent verification & validation (IV&V) plan.
  • Measure project performance against the plan.
  • Ensure project progresses according to the plan.
  • Manage project issues and risks.
  • Conduct status review meetings.
  • Disseminate status reports.
  • Implement testing plan.
  • Plan for a final project security review. Send a completed IT project security final review form to the IT Security Office.
  • As appropriate, implement training plan.
  • Document any lessons learned up to this stage in the project.
  • Obtain approval to close the project.
Closing Processes
  • Obtain acceptance of project deliverables.
  • Outline the long-term operational implications then hand off operations and support responsibilities.
  • Document or summarize costs spent on project and close any purchase orders.
  • Document any timeline changes (schedule compression and/or overruns).
  • Document the lessons learned over the course of the project.
  • Formalize closure.
  • Obtain sign-off from project sponsor and project manager.
  • Archive project documentation.