The 'science' of project management differs on the exact naming and number of phases, but in general it should look something like:
- Conception - somebody launches the project. Maybe it's a client deliverable or an internal systems upgrade or a move to a new office. The project has a goal and an owner (the person accountable for the success or failure of the project).
- Recruiting - In some companies project teams are formed as needed from available personnel. That means that the project owner or manager needs to figure out what basic skills are required and tries to find people with matching (or near-matching) skills. In companies delivering well-defined services to multiple customers, projects may be given to already existing teams or departments.
- Kick-off or sunrise meeting - This is probably the most important part of the project lifecycle, especially if the teams are formed ad hoc (that means as necessary with available personnel). Before starting work, I've always found it important for the team members to get to know each other. They should talk a little about their experience and what they see as their role in the project. One thing that is really helpful is for people to talk about previous projects they've been on and what was really successful and what really sucked. This is also a good time to voice any concerns about the project goals, timeline and skills.
- Project Planning - So the next couple of items really can be done iteratively. Members of the project team should all contribute to the project plan in their given areas of expertise. Concerns about the timing of the plan should be resolved as best as possible. The project plan and timeline should be owned by the whole team.
- Milestones, goals and progress meetings - You're off and running. Get the work done. Overcome problems. Adjust the people, deliverables and timetable as necessary (and as possible).
- Delivery - Ship it.
- Post-mortem or sunset - This is the second-most important part of the lifecycle and one which is too rarely done. At the end of the project have one last interaction among the team. What worked? What didn't? What would you do differently? Is there anything you produced on the way to the deliverable that you should share with other project teams or others in the company? Without a sunset meeting, the next projects are doomed to repeat the mistakes of the past and they don't get to take advantage of innovative solutions.
