With the start of a new year, it seems appropriate to reexamine the essential features of the project management lifecycles. Before getting into the details, however, it may be helpful to compare project lifecycles with the cycles and experiences of parenting. For example, an infant is born, but much is not known about the infant, so parents and others spend lots of time studying and assessing the needs and activities of the infant. There is often a lot of commotion, hard work, and long hours associated with the bundle of joy. As the infant grows and matures over time, parents continue to try and meet the needs of the child by observation, asking questions, discussions, and sometimes, using investigative means. Depending on the nature of the child, parents often have to really "dig" to finding out what is really going on. The parental role continues until the child reaches adulthood, and finally, the parents' job is completed. Throughout these phases, there is much risk and let's face it, children cost a lot of money in the process.

Projects start out in a similar fashion; sometimes there is a lot of commotion surrounding the earliest stage of a project. A project begins with an idea that eventually gains enough support to be approved as a project. In the early phase, or initiation of the project, little is know about the details, so more questions and discussions are needed until enough information is understood to start defining and planning the project in detail. Plans are implemented and simultaneously tracked and controlled to ensure high risk events do not occur and the final deliverable is completed on time. There too is a lot of hard work and dollars spent when Initiating, Planning, Executing, Controlling, and Closing a project. Projects, like children, can provide unexpected surprises, but the more a Project Manager plans and anticipates the less impact these surprises will have on a project.

PMBOK identifies five phases of project management: Initiation, Planning, Execution, Controlling, and Closing. Each phase is interrelated and interdependent on the other, and each phase contains numerous processes. The phases and processes collectively make-up what is considered a lifecycle.

Initiation

Project Initiation is the official indicator that an organization has approved resources to begin working on what is now a project. Initiation occurs at the very beginning of the project, and as the name implies, it is the phase where the project is officially launched. The Project Manager and stakeholders are immersed in pertinent information about the project. This information is often high-level and provided by the project sponsor.

Planning

Within the Planning phase is a detailed Definition process. A project scope, or definition document, must be written to ensure project goals, objectives, and criteria are identified. A working scope should define enough written detail so the Project Manager and team members can plan the details of the work, identify deliverables, staff, risk, and budget appropriately.

The process of Planning requires the Project Manager and team develop a WBS, forecast tasks, identify critical path, develop a timeline, budget, and complete detailed risk management plans. During this phase, attention is paid to identifying project stakeholders and determining a stakeholder communication plan. Much time and attention is required to develop an effective plan. The Execution, Controlling, and Closing phases all rely on the Planning phase and the associated documentation to carry out their functions effectively. In order to achieve a solid project Plan document, a Project Manager must go through several iterations of planning before a baseline plan can be approved.

Execution

Execution is about putting the project plan into action. The Project Manager is charged with keeping the project on track as identified in the baseline plan which includes the project Scope or Project Definition Document. Much time, energy, and focus is required to ensure the project stays on track with the objectives of the Plan.

Controlling

The Controlling phase of a project requires that performance measurements be captured and compared to the "planned" metrics. It is during this phase that a Project Manager can determine if she or he is staying on plan or if there are significant variances in the actual work. When variances do occur, it is up to the Project Manager and team members to analyze the impact, take corrective action, and realign the project plan.

Closing

Closing a project is just as important as any of phase of a project, but unfortunately it is often skipped. Closing brings a formal and orderly end to a project by bringing together all pertinent documents and archiving them for future reference. In addition, the Project Manager should evaluate stakeholder performance through a formal analysis of "lessons learned" as well as ensuring all contracts are closed. And last but not least, congratulate and appreciate team members for a job well done!