RSS

Project Scope Statement

22 Apr

I recently created a project scope for one of my projects, so I wanted to take an opportunity and share with you some helpful items on why you would create a project scope statement and how you would develop a Project Scope Statement.

First off, you may ask “What exactly is a Project Scope?”  A project scope is an agreement made between the project team members, the project sponsor, and key stakeholders that help define the project scope and what needs to be accomplished to meet the project’s objectives.  “Why would I create a Project Scope?”  This agreement helps to represent a common understanding of the project for the purpose of facilitating communication among the stakeholders and for setting authorities and limits for the project manager and team members.   “What does the Project Scope include?” The Project Scope includes relating the project to meet the needs of the business objectives and to help define the boundaries of the project in multiple dimensions, including approach, deliverables, milestones, and budget.

The main highlights in a project scope statement include:

  1. Project Justification: How the problem is to be resolved
  2. Identify Project Product: Define possible solutions to your problem
  3. Project Deliverables: List of deliveries that need to be completed for the project
  4. Project Objectives: Quantifiable project objects, such as: cost, schedule, and quality measures
  5. Authorization/Sign off: This is an important step to make sure you receive sign off from upper management or your customer, that you understand the project needs, so your project is setup for success at the initial stages of managing your project

Example: Project Scope Statement

 Do you have any helpful hints to share that would be helpful when preparing a Project Scope Statement?  Please share your comments below! Thank you. 

Image Credit

Advertisements
 

3 responses to “Project Scope Statement

  1. Vinish Garg

    September 27, 2012 at 8:28 am

    Intersting post. An important part of scoping process is to clarify the scope for functional details. It may involve iterations, discussions, preparing high level use cases before the functional scope is frozen. We move to other elements of a scope document only after the requirements are discussed, clarified and frozen. Right?

     

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: