Читать книгу Microsoft Project Fundamentals - Teresa S. Stover - Страница 58

Whereas the project charter is a high-level project overview that authorizes project implementation, the project scope is a more detailed version of much of the same information, laying out the parameters of the project.

In a waterfall project, the scope defines the boundaries of a project, not only saying what the project will accomplish but also indicating what the project will not do. Articulating these boundaries is essential to preventing scope creep, a common problem for waterfall projects. Throughout a project, team members and managing stakeholders often see opportunities for innovations or enhancements related to the work being done. The temptation is great to include these changes, which often seem inconsequential and easy to manage. These small changes beyond the specified scope can gradually creep up and have a cumulative effect, which results in project delays and cost overruns. Defining the scope well and keeping a close eye on its boundaries throughout the project is a key to project management success.

In an agile project, on the other hand, scope is continually refined throughout the life of the project with its iterative sprints. Because scope is expected to change and adjust throughout an agile project, scope creep is not an issue.

While the project charter is finished and “locked in” as soon as it's signed and therefore authorized, the project scope is a living document. Expect to update the project scope as conditions change and decisions are made throughout the project life cycle.

The project scope should include the following:

 Project Scope Specifies what is and is not included in the project. In this way, this section indicates the boundaries of the project.

 Requirements Define the conditions that must be met for the project sponsor to accept the project's deliverables.

 Deliverables List and describe all tangible or intangible goods or services produced for the project.

 Project Constraints Indicate any limitations on the project such as time, money, or resources.

 Assumptions Enumerate anything assumed but not definitely known about the project parameters.

The project scope statement defines the project's goals, requirements, and boundaries. It's typically presented to not only the project sponsor but also to the team leads and other project stakeholders as the “what” of the project. The “how” of the project is presented in the next step as the project plan and schedule.

Because the project scope defines the requirements and deliverables, it helps stakeholders determine where the project is in the process and whether the project is complete and has satisfied its objective.