| Artifact: Project Plan |
 |
 |
|
The purpose of this artifact is to provide a central document where any project team member can find the information on how the project will be conducted. |
| Fulfilled Slots | ||
|---|---|---|
| Roles | Responsible: | Modified By: |
| Tasks | Input To:
| Output From: |
| Main Description | This artifact describes how the project is organized, and identifies what practices will be followed. Additionally, it defines the parameters for tracking project progress, and specifies the high-level objectives of the iterations and their milestones. The project plan allows stakeholders and other team members to understand the big picture and, roughly, when to expect a certain level of functionality be available. Update the plan as often as necessary, usually at the end of each iteration, in order to reflect changing priorities and needs, as well as record the lessons learned from the project. |
|---|
| Templates | |
|---|---|
| Reports | |
| Examples |
| Create and update the project plan in planning sessions that involve the whole team and appropriate project stakeholders in order to make sure that everybody agrees with it. |
| Impact of not having | Without this artifact, there can be a lack of clear boundaries of the project scope that can lead to:
|
|---|---|
| Reasons for not needing | This artifact is typically required in some form on all but the smallest projects. However, projects taking a purely evolutionary or maintenance approach to development may choose to omit this artifact. |
| Checklists |
|---|
This program and the accompanying materials are made available under the |