CHAPTER 6How to Scope a TPM Project
Prediction is very difficult, especially about the future.
—Neils Bohr
Define the problem before you pursue a solution.
—John Williams, CEO, Spence Corp.
CHAPTER LEARNING OBJECTIVES
After reading this chapter, you will be able to:
- Understand what managing client expectations really means
- Explain the Conditions of Satisfaction (COS) development process
- Develop the COS document
- Plan and conduct the Project Scoping Meeting
- Use brainstorming, interviews, Facilitated Group Sessions, Prototyping, and Requirements Workshops to elicit requirements from business needs
- Build the Requirements Breakdown Structure (RBS)
- Define and write the basic parts and function of the Project Overview Statement (POS)
- Understand the role of the POS in the project management life cycle (PMLC)
- Discuss attachments to the POS and their role in project approval
- Understand the approval process for the POS
The Scoping Process Phase defines all of the tools, templates, and processes needed to answer two questions: “What will you do?” and “How will you know you did it?” If you don't know where you are going, how will you know when and if you ever get there? If I had to pick the Process Phase where most of the project failures originated, it would be the Scoping Process Phase. Not only is it the most difficult of the five Process Phases, but it is also the most sloppily executed of the five Process Phases. It probably has a lot to do with the desire to get going and anything ...