Loading presentation...

Present Remotely

Send the link below via email or IM


Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.


Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Scope Management

The Scope Management Plan details how the project scope will be defined, developed, and verified.

Michael Bacani

on 10 October 2014

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Scope Management

Scope Michael Bacani
Chuck Benger
Richard Blais
Sean Gannon
Sanjay Master 1. Collect Requirements
2. Define Scope
3. Create Work Breakdown Structure
4. Verify Scope
5. Control Scope In order to have successful project it is crucial for the project to implement proper scope management. This will assure that the project is doing the work it needs to do to succeed and only that work. A properly implemented and documented scope change management plan will protect the team from scope creep and will help to ensure that the team has the resources and budget required to succeed. Sources Haughey, D. (2009). Stop Scope Creep Running Away With Your Project. Retrieved January 18, 2013, from projectsmart: http://www.projectsmart.co.uk/stop-scope-creep-running-away-with-your-project.html

Mochal, Tom. "Define project scope to include deliverables, boundaries, and requirements | TechRepublic." TechRepublic - A Resource for IT Professionals. N.p., 18 Sept. 2007. Web. 17 Jan. 2013. <http://www.techrepublic.com/blog/project-management/define-project-scope-to-include-deliverables-boundaries-and-requirements/151>.

"Project Management Knowledge." Scope Planning. N.p., n.d. Web. 17 Jan. 2013. <project-management-knowledge.com/definitions/s/scope-planning/>.

"Project Management Core Competencies." Project Scope Management. N.p., n.d. Web. 21 Jan. 2013. <www.tbs-sct.gc.ca/emf-cag/project-projet/documentation-documentation/pmcc-cbgp/pmcc-cbgp-eng.pdf>.

"Project Scope Management." Project Scope Management. N.p., n.d. Web. 17 Jan. 2013. <ww2.cs.mu.oz.au/443/443Lec4.pdf>.

"Scope Management Plan Template." Free Project Management Templates - PMBOK Templates. N.p., n.d. Web. 6 Feb. 2013. <http://www.projectmanagementdocs.com/project-planning-templates/scope-management-plan.html>.

Stallswort, Eric. "How to Write A Scope Statement - With Sample MS Word Template." Project Management Strategies, How-To Articles, Reviews of Project Planning Tools & More at BrightHubPM.com . N.p., 24 Aug. 2012. Web. 22 Jan. 2013. <http://www.brighthubpm.com/templates-forms/2491-writing-a-scope-statement/>.

Tolbert, Lee. "Project Management Institute." Preliminary Scope Statement. N.p., n.d. Web. 21 Jan. 2013. <www.pmi.org/pmief/learningzone/KCMA_Curricula_Documents/Lesson_1-Preliminary_Scope_Statement.pdf>.

Vincent, Phil . "How Should a Business Analyst Define "Project Scope?" :: White Papers & Articles :: Resource Center :: Corporate Education Group." Corporate Education Group. N.p., n.d. Web. 17 Jan. 2013. <http://www.corpedgroup.com/resources/ba/HowShouldBADefineScope.asp>.

Wikipedia. (n.d.). Scope creep. Retrieved January 18, 2013, from Wikipedia: http://en.wikipedia.org/wiki/Scope_creep Define Scope In the Define Scope step the project charter and the gathered requirements are used to create a detailed description of the project and its major deliverables. This definition will be in the form of a Project scope statement. The Project Scope Statement will include these criteria:

Project Justification Information
Identify the project product
Identify the project deliverables
Identify the project objectives Verify Scope Process of verifying that all identified project deliverables have been completed correctly and satisfactorily and obtaining formal acceptance of the project scope from the stakeholders. Work Breakdown Structure Process of breaking down project deliverables and project work into smaller, more manageable components. Planned work are called work packages, work packages can be scheduled, cost estimated, monitored, and controlled. Objectives Project Scope Management Process Summary Scope
Scope Management Approach
Roles & Responsibilities
Project Scope Management Process
Summary Control Scope Monitoring and controlling the project scope and managing any changes are crucial to the success of completing the project on time. Changes are imperative to any successful project but proper control and integrated techniques need to be in order to prevent scope creep.

Changes to the project scope is required the process for changes to the scope need to occur.

Scope creep can be a result of poor requirements, lack of change control, weak project managers and poor communications. What is Scope? Project Scope Scope Management Approach The Scope Management Approach is a summary of the Scope Management Plan that will be used to complete the project. The chosen approach will be influenced by the project objectives, timeline, costs and the roles and responsibilities of the project members. Roles & Responsibilities It is important to clearly establish the roles and responsibilities of everyone that will be involved in scope management. Each member must understand what their part in the project is to ensure that work is being done properly. Collect Requirements In order to fully understand the criteria for success the requirements must be gathered from all pertinent stakeholders. Many techniques can be utilized to gather these requirements, including (but not limited to):

•One on one interviews
•Group Interviews
•Following people around
•Use Cases

Outputs of this step will include Requirements documentation, Requirements management plan, and Requirements traceability matrix. Questions? Main stakeholders should verify the scope formally. Less involved stakeholders can give implicit approval. Other interested parties only need a copy of the project plan for information purposes. Who has authority/responsibility for scope management.
How scope is defined(Scope statement, WBS), measured and verified (Quality Checklist, Scope Baseline).
Who initiates and who authorizes scope change.
Who is responsible for the deliverables and who approves acceptance of project scope. The work that needs to be accomplished to deliver a product, service, or result with the specified features and functions. Product Scope Features and functions that characterize a product, service, or result. Sponsor Approve or deny scope change requests as appropriate.
Evaluate need for scope change requests. Project Manager Facilitate impact assessments of scope change requests.
Organize and facilitate scheduled change control meetings.
Update project documents upon approval of all scope changes. Team Lead Team Member Participate in impact assessments of scope change requests.
Communicate outcomes of scope change requests to team. Participate in defining change resolutions.
Evaluate the need for scope changes and communicate them to the project manager as necessary. The following rules should be used when verifying scope: The Scope Management Approach is a summary of the Scope Management Plan that will be used to complete the project. The chosen approach will be influenced by the project objectives, timeline, costs and the roles and responsibilities of the project members.
Full transcript