8/25/99 - Jack Harich - Go Back
1. As the sample process diagram shows, it's based on 4 standard phases and numerous overlapping workflows. The workflows produce various work products, which include the product itself. This excellent diagram gives a quick, clear conceptual overview. It's known as the Phase and Workflow Diagram.
2. The process is based on Barry Boehm's "spiral model", in addition to Jacobson's Objectory. Each phase has one or more iterations. The top goal of each iteration is to reduce the largest remaining risk for that phase. Thus as the end of a phase is reached, all phase risk has been resolved by a series of small iterations. Quality Assurance occurs in parallel with the entire project, and so there is no piling up of surprises (read lots of defects) for resolution near the end. The process reduces scrap and rework immensely.
3. It's possible to start small and simple with the Unified Process:
A. Pick you work products. Start with only a few at first. See SPM page 85 or SPSG page 138 for suggestions, or have the Process Manager recommend what's appropriate for your project.
B. Stretch out your work products on the above diagram so that they overlap each other and span the necessary phases. Plan the key milestones for each and the approvals required.
C. Plan the project iterations and key milestones. The most important milestone is the executable architectural prototype which signals the end of the Elaboration Phase. Your milestones can be as simple as what work products and approvals are required for the end of each iteration and phase.
D. In some cases consider having the whole team figure all this out. What a great way to kick off a project, jell the team and/or learn about the mysteries of process!!!
4. Be sure to tune the process to what your needs.
5. We've saved the best news for last. According to Barry Boehm, the Unified Process does this: (SPM page xxi)
"...gives you managmenent control of the key software economics leverage points.... These are:
1. Reducing the amount of software you need to build.
2. Reducing rework via improved process and teamwork.
3. Reducing the labor-intensiveness of the remaining work via automation."Now that's thinking at a high level of abstraction! As you study the SPM book, the recurrent themes of process, reuse, components and tools are used to reduce, reduce, reduce what needs to be done, and so projects finish sooner, better and more predictably. What more can we ask for? :-)