• When Reality Hits - Project Managers Roll With It

  February 11, 2012

  
  

• When IT Is Your Company’s “Piggy Bank”

  February 10, 2012

  
  

• 4 Key Things a Project Manager Must Do

  February 10, 2012

  
  

• Essential Project Management

  February 10, 2012

  
  

• 8 Traits of Top Project Managers - Part 1

  February 9, 2012

  
  

• Agile Project Management - Engaging Your Customer!

  February 9, 2012

  
  

• 9 Tips to Avoid Traps in Project Planning

  February 9, 2012

  
  

• Why Projects Succeed - Executive Sponsorship

  February 8, 2012

  
  

• On Customer Participation in Agile Projects

  February 8, 2012

  
  

• A Project Charter for Lazy Teams

  February 8, 2012

  
  

Creating The Project Scope - Documentation Means Everything

April 18, 2008 | Author: PM Hut | Filed under: Project Scope Management, Scope Management

Creating The Project Scope - Documentation Means Everything (#3 in the series Creating The Project Scope)
By Joseph Phillips

After the project manager and the customer are in agreement about what the project will create, the project manager should create a scope statement, which is a document that captures everything that is considered in scope and defines the relevant things that are out of scope. For example, a project to push an application to 1,500 workstations might define the application, define the overview of the project work, and emphasize that the rollout doesn’t include visiting every machine to confirm the existence of the push. The scope statement clarifies the project and requires the project manager, the project sponsor, and sometimes the key stakeholders to sign off on the document.

The scope statement serves as the guide for all future project decisions. The following figure shows the timeline of the project and the relevant influence of the project manager and the stakeholders. Early in the project the stakeholders should have a bunch of influence—their input is essential. As the project progresses toward completion, notice that the stakeholders’ influence wanes as the project manager’s influence increases. The intersection of the two paths represents the creation of the scope statement.

In other words, once the scope statement has been agreed upon, the project manager owns the project and works to protect and deliver on the promises established in the scope statement.

Joseph Phillips is the author of five books on project management and is a, PMI Project Management Professional, a CompTIA certified Project Professional, and a Certified Technical Trainer. For more information about Project Management Training, please visit Project Seminars.

Related Articles

• Creating The Project Scope - Risk Management Planning
• Requirements Gathering and Documentation
• Minimise Your Project Management Documentation
• Creating the Project Scope - Conclusion
• Creating The Project Scope - Introduction

This entry was posted on Friday, April 18th, 2008 and is filed under Project Scope Management, Scope Management. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

feel free to leave a comment

Comment Guidelines: Basic XHTML is allowed (a href, strong, em, code). All line breaks and paragraphs are automatically generated. Off-topic or inappropriate comments will be edited or deleted. Email addresses will never be published. Keep it PG-13 people!

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

All fields marked with " * " are required.

Name: *
Email (will never be displayed): *
URL:
Your comments: *
Remember my information for the next time I visit.

• Agile Project Management
• Ask the Hut
• Certification
  • CAPM
  • ITIL
  • PgMP
  • PMP
• Change Management
• Communications Management
  • Communications Planning
  • Information Distribution
  • Performance Reporting
  • Project Closure
• Computer Based Information Systems
  • Latest Trends
  • Project Collaboration
• Concepts
  • Project Lifecycle Phases
  • Project Stakeholder Management
  • Role of the Project Manager
• Corporate Transformation
• Cost Management
  • Cost Estimating
  • Economic Evaluation
• Critical Chain Project Management
• Delegation
• History
• HR Management
  • Organizational Structures
  • Team Building
• Implementing Project Management
  • PM Implementation Plan
• Integration Management
  • Change Control
  • Project Management Framework
  • Project Plan Development
• Lessons Learned
• Management
• Miscellaneous
• People Issues
  • Conflict Management
  • Leadership
  • Motivation
• PMBOK
• PRINCE2
• Procurement Management
  • Contract Administration & Close-out
  • Procurement Plannning
  • Solicitation & Source Selection
• Program Management
• Project Lifecycle Phases
• Project Management Advantages
• Project Management Advantages
• Project Management as a Career
• Project Management Best Practices
• Project Management Charts
• Project Management Definitions
• Project Management Ethics
• Project Management for Beginners
• Project Management Guides
• Project Management Musings
• Project Management Office
• Project Management Proposals
• Project Management Templates
• Project Portfolio Management
• Project Workforce Management
• Quality Management
  • Principles
  • Techniques
• Requirements Management
• Risk Management
  • Risk Identification
  • Risk Quantification & Analysis
  • Risk Response & Control
• Scheduling
  • Normal and Crash Costs
  • Project Plan Refinement
  • Resource Constrained Projects
  • Resource Leveling
• Scope Management
  • Process of Change Control
  • Project Scope Management
  • Scope Change Control
• SCRUM
• Soft Management
• Time Management
  • Activity Definition
  • Activity Duration Estimate
  • Activity Sequencing
  • Critical Path
  • Network Planning
  • Project Milestones
• Training
• Uncategorized