Prediction is very difficult, especially about the future. -Neils Bohr
Define the problem before you pursue a solution. —John Williams, CEO, Spence Corp.
The Version Scope phase is the beginning of APF (see Figure 14.1). It is a formal set of activities that take place very soon after a request has been made. There are two major parts to version scope:
A defining part. The defining part can effectively be completed by two parties: a requestor and a provider. These may each be single individuals or small groups that represent the two parties. In either case, the critical factor is that they not only represent their constituency but they speak for their constituency and can make decisions for their constituency.
Chapter Learning Objectives
After reading this chapter, you will be able to:
♦ Describe the components of the Version Scope phase
♦ Conduct a Conditions of Satisfaction process
♦ Write a Project Overview Statement for an APF project
♦ Develop a mid-level WBS
♦ Prioritize version functionality using one of three methods
♦ Prioritize the scope triangle using success sliders
♦ Determine the number of cycles and the cycle timeboxes
♦ Assign functionality to cycles
A planning part. The planning part is not unlike the early stages of the TPM planning session. It should be attended by the stakeholders and core project team. The difference here is that the version plan is not a detailed plan. It does not provide a detailed definition of the work to be done or of a schedule to be followed. Those details are part of the cycle plans.
Figure 14.1 Version Scope phase.
Was this article helpful?
What you need to know about… Project Management Made Easy! Project management consists of more than just a large building project and can encompass small projects as well. No matter what the size of your project, you need to have some sort of project management. How you manage your project has everything to do with its outcome.