Project Lifecycle
Four Phases of a Project
Initiating
The Initiating Phase of a project is where every successful project begins. This is where a business case is made to state the purpose of the project and its value. Also worth considering is the current state / future state of whatever the project will be touching. Knowing the baselines and behaviors are imperative to how we handle projects at IMT, we have a history of getting deep into a project and having an issue crop up.
This is also where we put together the Project Charter (previously called requirements). This document, while containing requirements, is not limited to them. It also includes questions, assumptions, stakeholders, the sponsor, the client, and any information pertinent …show more content…
[Scrum/Agile piece here] Deliverables and the order in which they are accomplished should be agreed upon by the team. At this point in the project, the PM should be handling check-ins, risk management, any change control, and communication around the team. An executing project, in an ideal world, eats up less PM time day to day. [Anything else Bill wants to add]
Deliverables
Reporting
Status
Progress
Forecasting
Risk Management
Change Control
Revisions
Communications
Issues
Escalation
Priority
Problem Solving
Closing
Once a project has passed acceptance with the sponsor and/or client, it’s moved into the closing phase. Documents are finalized and archived for future reference, these include: scope, schedule, cost, resources, and risks. A post mortem should be run by the PM, and is a venue that the team can talk about Lessons Learned from the project.
Acceptance
Measurement
Future State
Final Documents
Scope
Schedule
Cost
Resources
Risks
Lessons Learned
Post
Four Phases of a Project
Initiating
The Initiating Phase of a project is where every successful project begins. This is where a business case is made to state the purpose of the project and its value. Also worth considering is the current state / future state of whatever the project will be touching. Knowing the baselines and behaviors are imperative to how we handle projects at IMT, we have a history of getting deep into a project and having an issue crop up.
This is also where we put together the Project Charter (previously called requirements). This document, while containing requirements, is not limited to them. It also includes questions, assumptions, stakeholders, the sponsor, the client, and any information pertinent …show more content…
[Scrum/Agile piece here] Deliverables and the order in which they are accomplished should be agreed upon by the team. At this point in the project, the PM should be handling check-ins, risk management, any change control, and communication around the team. An executing project, in an ideal world, eats up less PM time day to day. [Anything else Bill wants to add]
Deliverables
Reporting
Status
Progress
Forecasting
Risk Management
Change Control
Revisions
Communications
Issues
Escalation
Priority
Problem Solving
Closing
Once a project has passed acceptance with the sponsor and/or client, it’s moved into the closing phase. Documents are finalized and archived for future reference, these include: scope, schedule, cost, resources, and risks. A post mortem should be run by the PM, and is a venue that the team can talk about Lessons Learned from the project.
Acceptance
Measurement
Future State
Final Documents
Scope
Schedule
Cost
Resources
Risks
Lessons Learned
Post