In a typical software development environment, project closures mark the end of a project.
- Project records are completed and archived,
- resources released,
- issues and lessons are documented, and
- a formal dinner/party held for celebration.
Last step is optional, though is very motivating for participants. :-)
Contrast this with Scrum. I know that scrum runs on stories from backlogs. So, technically, every iteration closes certain stories. So, there are two questions here.
- For a group that works on multiple simultaneous projects, how do project closures fit in?
- For a project that involves multiple groups, how does this concept apply?
Or, does project closure term not apply to T&M projects at all?