And So In Closing...
The end is near! Well, at least the end of your project.
With the completion of its other phases, it’s now time for a number of activities that help bring the project some closure. While finishing these extra details at the end may turn into a rush job by the team in order to move on to the next project, the process should be completed properly so that other groups in the future can learn from your experience.
In particular, the closing meeting of the project team should include an appropriate amount of time for reminiscing about what occurred, what solutions were provided and what could be done differently in the future. While many of us may want this disclosure to happen in one meeting, it may be necessary to schedule many gatherings with different participants in order to gather enough detailed information.
When you think of the time and effort spent in setting up, planning, executing and verifying all the actions taken in the project, you owe it to yourself, any support teams and project teams that follow to go through the process of identifying these situations and documenting specific lessons learned from the endeavor.
Where to Begin?
For the project team, everything begins at the creation of the scope.It may seem like ancient history, but does anyone in the group remember what the original scope looked like? Were there any changes to it along
Please log in or sign up below to read the rest of the article.