Phase Review Meetings
Describe the structure and importance of a project phase review meeting. Select three areas that need to be
reviewed by the project manager and explain why. Create a list of stakeholders that should be invited to the
meeting. Why did you choose these stakeholders? What should all the meeting participants be able to walk away
from the meeting with? Respond to at least two of your fellow classmates’ postings.
While a project review meeting occurs at the end or close of a project, a project phase review meeting occurs at the
end of each phase of the project. Typically there are seven project phases: strategy and business case; preparation;
design; develop and test; training and business; support and benefits; and finally project close. In addition there are
seven project processes: phase management; planning; control; team management; communication; procurement;
and integration. Phases are important, because “you can ensure that deliverables produced at the end of each phase
meet their purpose, and that project team members are properly prepared for the next phase,” (“Project
Management,” 2013, para 5). It’s important to conduct these phase reviews, to receive approval before moving onto
the next phase, and to clearly define the work breakdown structure for the upcoming phase. This helps to keep the
entire project on track.
The preparation phase should be reviewed by the project manager, because this is the phase where a high-level work
breakdown structure is established, and milestones defined. Key stakeholders that should attend are the sponsor,
customer, and managers who will be responsible for assigning resources to the project. These people should attend,
so that the project begins with everyone having the same expectations and agreeing to the work that will be done
including the end deliverable.
Design is another phase that should be reviewed with a project manager and key stakeholders. This is the phase in
which the work is actually started. The customers should be part of this meeting as this is when the end deliverable
is carefully crafted and signed off upon. As a result the project sponsor should also be involved in this
meeting. Initial project team members could also be present, so that they can offer their expertise on the processes
being defined. “Problems are almost always easier and cheaper to fix at design stage than they are once the detailed
work of implementation has started,” (“Project Management,” 2013, para 15). If subject matter expert team
members are there, they can help head off design issues.
Development and testing is another stage that should be reviewed by the project manager and stake holders. Just as
the preparation and design phases are so critical, so is the development and testing phase. This is when the actual
product or work is being done. If a project is the implementation of a new software system, then every aspect of
that software system needs to be tested prior to the launch date. The project team members are the key people that
should be at this meeting to ensure that their piece in the development and testing is on track with the overall project
plan. It also allows for time for issues and solutions to be discussed.
References
Kerzner, H. (2005). Using the Project Management Maturity Model: Strategic planning for project management
(2nd ed.). [Kindle DX version]. Retrieved from Amazon.com
Project Management Phases and Processes. (2013). Retrieved January 16, 2014, from
http://www.mindtools.com/pages/article/newPPM_63.htm