May 10, 2010

In its simplest form, Implementation is generally considered by team members as when the project starts. In a phase-controlled project, project team members are only minimally involved prior to the implementation phase. At this point, the scope should be approved and the project is starting in earnest. Implementation is very often the longest phase in the project lifecycle.

From a software perspective the traditionally agreed upon sub-phases include requirements, design, develop/build, and test. These can be extrapolated in many different ways and approached using different methodologies such as Agile, XP or countless others. But, at the core of the project you are managing these four things:

  • Understanding in a documented way what the end customer needs/wants (Requirements)
  • Extrapolating the understanding of the requirements into a technical specification to prove that the wants and needs of the customer can be addressed (Design)
  • Making the requirements a reality (Development/Build)
  • Test the results for accuracy/completion (Quality Assurance or Testing)

Read the rest of this entry »

The Big Picture – Project Lifecycle Overview

March 22, 2009

Project LifecycleClick Here for Larger Image

A picture is worth a thousand words so I thought I would start with a diagram. I recently had the need to explain an overview of the Project Lifecycle within the context of software development so I thought it would be worth sharing here. This diagram is by no means original or even possibly unique. The initiating, planning, executing (implementation), monitor and control and closing match the PMBOK definition for project process and the sub-processes are generally agreed upon across the industry, but everyone enjoys a good picture and so here is mine for explaining how things work.

Read the rest of this entry »