Week 2 - Lecture

Week 2 - Lecture - Week 2: Project Scope and Schedule -...

Info iconThis preview shows pages 1–2. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: Week 2: Project Scope and Schedule - Lecture Defining the Project Defining Project Scope | Deliverables | Establishing Project Priorities | Creating the Work Breakdown Structure | Integrating the WBS with the Organization | Developing the Project Network | From Work Package to Networks | Constructing a Project Network | Critical Path | Determining Slack | Study Guide We have now defined projects in generic terms, and we have seen how they fit into accomplishing the strategic mission, goals, and objectives of organizations. We will continue learning about tools and techniques for defining what is required from a specific project that we are to undertake, as well as tools for planning and controlling the work needed to achieve those project requirements. In this and the following week, the key elements of an integrated project planning and control system will be laid out. This project management system will be anchored by the idea of project scope, which expresses project requirements. Then, the idea of a work breakdown structure (WBS) will be developed; this basically expresses the work activities that must be performed to achieve or complete the project scope. The work breakdown structure becomes the basis for several project management elements, including: • cost estimation and development of a project budget • creation of a project schedule Defining the Project Scope According to the textbook, research clearly shows that a poorly-defined scope is the most frequently mentioned barrier to project success. As we will see, this means that, frequently, the fate of a project is cast right at the beginning when the scope should be laid out. Often, the project scope, and specifically a written scope statement, is not laid out in the clear and definitive terms that are necessary for ultimate project success. Scope Concepts The ideas presented this week can be cemented by reviewing a few definitions for terms we will use. Scope Concepts Scope: The sum of the products, services, and results to be provided as a project. ** Scope Statement: A definition of the end result or mission of a project. Scope statements typically include project objectives, deliverables, milestones, specifications, and limits and exclusions. * Deliverable: • Any unique and verifiable product result, or capability, to perform a service that must be produced to complete a process, phase, or project. Often used more narrowly in reference to an external deliverable, which is a deliverable that is subject to approval by the project sponsor or customer. ** • The expected outputs over the life of the project. * Milestone: Week 2: Project Scope and Schedule - Lecture...
View Full Document

This note was uploaded on 01/23/2011 for the course MGMT 404 taught by Professor Smith during the Spring '10 term at DeVry Arlington.

Page1 / 9

Week 2 - Lecture - Week 2: Project Scope and Schedule -...

This preview shows document pages 1 - 2. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online