Collective Wisdom from the Experts 103
expecting two. The scope statement helps you manage stakeholder expecta-
tions. More than once, I have been knee-deep in the project life cycle, usu-
ally after a few key deliverables are in prototype stage, and had a stakeholder
say, “I thought we were getting two bedrooms.” This is where the scope state-
ment comes to the rescue. You certainly don’t want to wield it as though it is
a weapon, but it is a great way to gently remind your stakeholders what they
agreed to back at the beginning of the project.
It’s a good idea to periodically review your scope statement with your stake-
holders. Project status meetings or steering committee meetings are a logical
place to conduct this review. Devote some time every other meeting, or at
intervals that make sense given the size and scope of your project, to reviewing
the deliverables listed in the scope statement.
If you’re conducting regular status meetings, you’re likely doing this to some
extent already. Status meetings typically address the work accomplished last
period, and the anticipated work to be completed during the next work period.
Occasionally take the time to go beyond the next work period and remind every-
one of the key deliverables that are scheduled to be delivered later in the project.
Regularly reviewing the project scope statement can increase your chances for
a successful project and keep your stakeholder’s expectations aligned with the
goals of the project.