Professional Documents
Culture Documents
1. Performance Reviews:
3. Gate Review
The main purpose of the gate review meeting (also called phase
gate review meeting) is to periodically (at the end of each gate)
ensure that the project is running smoothly, and take corrective
measures if it's not. These meetings are attended by a group of
stakeholders, the project sponso , and the project manager. These
are important meetings, so they can take up to a day (it is very rare
for such meetings to take more than a day, and often they take half
aday)
Essentially, what it is discussed during the GRM (Gate Review
Meeting) is how is the project doing so far (still adhering to the
business case? project is done according to the agreed upon quality
and scope?), and should we continue with the project or just cancel
it. This makes the GRM one of the most critical meetings for a
project manager, as his project can be easily cancelled or ideally,
any decision made during a GRM is by consensus. Again, GRMs are
held after finishing important milestones. For example, after
gathering the requirements, when finishing the planning, when
finishing the execution of the project (just before the testing), and
just before closing the project. Typically, you should never have less
than 3 GRMs in your project. But just make sure to keep the
number of these meetings small, they're not, after all, weekly status
meetings.
Post project reviews typically involve the project team and major
stakeholders meeting together and reviewing what went well and
what went badly during the project. This input can help participants
make the right decisions and plans so that the next project runs
better. It can also help clear up misunderstandings and other
issues.
Steering Committee:
Project Sponsor:
Project Manager
The Project Manager is the person responsible for ensuring that the
Project Team completes the project. The Project Manager develops
the Project Plan with the team and manages the team’s
performance of project tasks. It is also the responsibility of the
Project Manager to secure acceptance and approval of deliverables
from the Project Sponsor and Stakeholders. The Project Manager is
responsible for communication, including status reporting, risk
management, escalation of issues that cannot be resolved in the
team, and, in general, making sure the project is delivered in
budget, on schedule, and within scope.
Team Members:
The Project Team Members are responsible for executing tasks and
producing deliverables as outlined in the Project Plan and directed
by the Project Manager, at whatever level of effort or participation
has been defined for them. On larger projects, some Project Team
members may serve as Team Leads, providing task and technical
leadership, and sometimes maintaining a portion of the project plan.
Customers
Customers comprise the business units that identified the need for
the product or service the project will develop. Customers can be at
all levels of an organization. Since it is frequently not feasible for all
the Customers to be directly involved in the project, the following
roles are identified:
Record management
Ending relationships
Projects need a clear cut-off to signal the end of handover and the
transfer of full operational responsibility from the project team to
the customer.
• Doubt his or her ability to deliver the benefits from the product
or service on which the business case was built, and there will
no longer be anyone else with whom to share the blame.
Some benefits are easy to quantify and measure, such as sales and
revenue from a new line of products. Others are easy to quantify,
but less easy to measure, such as cost savings from an improved
interdepartmental business process. Still more are difficult both to
quantify and to measure, such as the benefits of company-wide
education in risk management.
Record management
Ending relationships