eleventh lecture hour 9:30 – 10:20 am, saturday, september 16 software management disciplines...
TRANSCRIPT
![Page 1: Eleventh Lecture Hour 9:30 – 10:20 am, Saturday, September 16 Software Management Disciplines Iterative Process Planning (from Part III, Chapter 10 of](https://reader030.vdocuments.net/reader030/viewer/2022013012/56649ed35503460f94be2ed7/html5/thumbnails/1.jpg)
Eleventh Lecture Hour9:30 – 10:20 am, Saturday,
September 16
Software Management Disciplines
Iterative Process Planning(from Part III, Chapter 10 of Royce’ book)
![Page 2: Eleventh Lecture Hour 9:30 – 10:20 am, Saturday, September 16 Software Management Disciplines Iterative Process Planning (from Part III, Chapter 10 of](https://reader030.vdocuments.net/reader030/viewer/2022013012/56649ed35503460f94be2ed7/html5/thumbnails/2.jpg)
Review –The Four Parts of the Course
• Software Management Renaissance
– The conventional software management process.
– Five improvements to make the waterfall process work.
• A Software Management Process Framework
– Phases
– Artifacts
– Workflows
– Checkpoints
• Software Management Disciplines– Planning– Organization– Automation– Process control and
instrumentation– Tailoring
• Looking Ahead– Modern project profiles– Next-generation software
economics– Modern process transitions
![Page 3: Eleventh Lecture Hour 9:30 – 10:20 am, Saturday, September 16 Software Management Disciplines Iterative Process Planning (from Part III, Chapter 10 of](https://reader030.vdocuments.net/reader030/viewer/2022013012/56649ed35503460f94be2ed7/html5/thumbnails/3.jpg)
Review - Typical Minor Milestones
![Page 4: Eleventh Lecture Hour 9:30 – 10:20 am, Saturday, September 16 Software Management Disciplines Iterative Process Planning (from Part III, Chapter 10 of](https://reader030.vdocuments.net/reader030/viewer/2022013012/56649ed35503460f94be2ed7/html5/thumbnails/4.jpg)
Review - Checkpoints
![Page 5: Eleventh Lecture Hour 9:30 – 10:20 am, Saturday, September 16 Software Management Disciplines Iterative Process Planning (from Part III, Chapter 10 of](https://reader030.vdocuments.net/reader030/viewer/2022013012/56649ed35503460f94be2ed7/html5/thumbnails/5.jpg)
Review - Summary for Checkpoints of the Process
• Checkpoints provide for control of the development process.
• Major Milestones are the Objectives, Architecture, Initial Operational Capability, and the Product Release Milestones.
• Minor Milestones are for iteration readiness and iteration results reviews.
• Periodic Assessment Reviews are for focusing management attention on the health of the project.
![Page 6: Eleventh Lecture Hour 9:30 – 10:20 am, Saturday, September 16 Software Management Disciplines Iterative Process Planning (from Part III, Chapter 10 of](https://reader030.vdocuments.net/reader030/viewer/2022013012/56649ed35503460f94be2ed7/html5/thumbnails/6.jpg)
Part III – Software Management Disciplines
– Planning
– Organization
– Automation
– Process control and instrumentation
– Tailoring
![Page 7: Eleventh Lecture Hour 9:30 – 10:20 am, Saturday, September 16 Software Management Disciplines Iterative Process Planning (from Part III, Chapter 10 of](https://reader030.vdocuments.net/reader030/viewer/2022013012/56649ed35503460f94be2ed7/html5/thumbnails/7.jpg)
Topic for TodayIterative Process Planning
• Work Breakdown Structures (WBS)
• Planning Guidelines
• The Cost and Schedule Estimating Process
• The Iterative Planning Process
• Pragmatic Planning
![Page 8: Eleventh Lecture Hour 9:30 – 10:20 am, Saturday, September 16 Software Management Disciplines Iterative Process Planning (from Part III, Chapter 10 of](https://reader030.vdocuments.net/reader030/viewer/2022013012/56649ed35503460f94be2ed7/html5/thumbnails/8.jpg)
Conventional WBS
![Page 9: Eleventh Lecture Hour 9:30 – 10:20 am, Saturday, September 16 Software Management Disciplines Iterative Process Planning (from Part III, Chapter 10 of](https://reader030.vdocuments.net/reader030/viewer/2022013012/56649ed35503460f94be2ed7/html5/thumbnails/9.jpg)
Problems With Conventional WBS
• No way to track ratio of productive activities to overhead activities.
• No tracking of percentage of effort expended in rework.
• No tracking of percentage of cost expended in software capital equipment.
• Noo tracking of productive testing versus unproductive integration.
• No tracking of cost of release N as a basis for planning release N+1.
![Page 10: Eleventh Lecture Hour 9:30 – 10:20 am, Saturday, September 16 Software Management Disciplines Iterative Process Planning (from Part III, Chapter 10 of](https://reader030.vdocuments.net/reader030/viewer/2022013012/56649ed35503460f94be2ed7/html5/thumbnails/10.jpg)
Recommended WBS
• First Level– Workflows for WBS elements. Can be
allocated to single teams.
• Second Level– Defined for each phase of the life cycle.
• Third Level– Focus on the activities that produce the artifacts
of each phase.
![Page 11: Eleventh Lecture Hour 9:30 – 10:20 am, Saturday, September 16 Software Management Disciplines Iterative Process Planning (from Part III, Chapter 10 of](https://reader030.vdocuments.net/reader030/viewer/2022013012/56649ed35503460f94be2ed7/html5/thumbnails/11.jpg)
Work Breakdown Structure
![Page 12: Eleventh Lecture Hour 9:30 – 10:20 am, Saturday, September 16 Software Management Disciplines Iterative Process Planning (from Part III, Chapter 10 of](https://reader030.vdocuments.net/reader030/viewer/2022013012/56649ed35503460f94be2ed7/html5/thumbnails/12.jpg)
WBS (cont’d)
![Page 13: Eleventh Lecture Hour 9:30 – 10:20 am, Saturday, September 16 Software Management Disciplines Iterative Process Planning (from Part III, Chapter 10 of](https://reader030.vdocuments.net/reader030/viewer/2022013012/56649ed35503460f94be2ed7/html5/thumbnails/13.jpg)
Tailoring of the WBS
• Scale– Larger projects have more levels.
• Organizational Structure– Subcontractors or associate contractors require additional
management subelements.• Degree of Custom Development
– Fully custom requires more in design and implementation to manage risks.
• Business Context– Large contractual projects generally require additional levels for
management and accounting purposes.• Precedent Experience
– Projects should exploit existing work and WBS development.
![Page 14: Eleventh Lecture Hour 9:30 – 10:20 am, Saturday, September 16 Software Management Disciplines Iterative Process Planning (from Part III, Chapter 10 of](https://reader030.vdocuments.net/reader030/viewer/2022013012/56649ed35503460f94be2ed7/html5/thumbnails/14.jpg)
WBS Budgeting
![Page 15: Eleventh Lecture Hour 9:30 – 10:20 am, Saturday, September 16 Software Management Disciplines Iterative Process Planning (from Part III, Chapter 10 of](https://reader030.vdocuments.net/reader030/viewer/2022013012/56649ed35503460f94be2ed7/html5/thumbnails/15.jpg)
Effort and Schedule By Phase
![Page 16: Eleventh Lecture Hour 9:30 – 10:20 am, Saturday, September 16 Software Management Disciplines Iterative Process Planning (from Part III, Chapter 10 of](https://reader030.vdocuments.net/reader030/viewer/2022013012/56649ed35503460f94be2ed7/html5/thumbnails/16.jpg)
Iterations
• Inception stage– Prototypes, critical use
cases, existing components, custom component prototypes.
• Elaboration stage– Architecture, initialization,
scenarios, peak load conditions, worst case control flow, fault tolerance.
• Construction stage– Alpha and beta releases,
execution of all critical cases, 95% of capabilities demonstrated.
• Transition stage– Resolve all defects,
incorporate beta feedback, incorporate performance improvements.
![Page 17: Eleventh Lecture Hour 9:30 – 10:20 am, Saturday, September 16 Software Management Disciplines Iterative Process Planning (from Part III, Chapter 10 of](https://reader030.vdocuments.net/reader030/viewer/2022013012/56649ed35503460f94be2ed7/html5/thumbnails/17.jpg)
Evolution of Planning
![Page 18: Eleventh Lecture Hour 9:30 – 10:20 am, Saturday, September 16 Software Management Disciplines Iterative Process Planning (from Part III, Chapter 10 of](https://reader030.vdocuments.net/reader030/viewer/2022013012/56649ed35503460f94be2ed7/html5/thumbnails/18.jpg)
Cost and Schedule Estimating Steps – Top Down
1. Software project manager characterizes overall size, process, environment, people and quality.2. Software manager makes a macro-level estimate of effort and schedule using software cost estimation model.3. Software manager partitions the effort in top-level WBS.4. Subproject managers decompose each WBS elemnt into lower levels.
![Page 19: Eleventh Lecture Hour 9:30 – 10:20 am, Saturday, September 16 Software Management Disciplines Iterative Process Planning (from Part III, Chapter 10 of](https://reader030.vdocuments.net/reader030/viewer/2022013012/56649ed35503460f94be2ed7/html5/thumbnails/19.jpg)
Cost and Schedule Estimating Steps – Bottom Up
1. Lower level WBS elements are elaborating into detailed tasks by responsible WBS element managers.
2. Estimates are combined and integrated into higher level WBS elements.
3. Comparisons are made with the top down budgets and schedule milestones. Large differences are reconciled to converge on agreements.
![Page 20: Eleventh Lecture Hour 9:30 – 10:20 am, Saturday, September 16 Software Management Disciplines Iterative Process Planning (from Part III, Chapter 10 of](https://reader030.vdocuments.net/reader030/viewer/2022013012/56649ed35503460f94be2ed7/html5/thumbnails/20.jpg)
Planning Balance Across Life-Cycle
![Page 21: Eleventh Lecture Hour 9:30 – 10:20 am, Saturday, September 16 Software Management Disciplines Iterative Process Planning (from Part III, Chapter 10 of](https://reader030.vdocuments.net/reader030/viewer/2022013012/56649ed35503460f94be2ed7/html5/thumbnails/21.jpg)
General Observations
• Top down budgets and schedules tend to be overly optimistic.
• Bottom up budgets and schedules tend to be overly pessimistic.
• During Engineering Stages, top down estimates dominate. During Production Stages, bottom up estimates dominate.
![Page 22: Eleventh Lecture Hour 9:30 – 10:20 am, Saturday, September 16 Software Management Disciplines Iterative Process Planning (from Part III, Chapter 10 of](https://reader030.vdocuments.net/reader030/viewer/2022013012/56649ed35503460f94be2ed7/html5/thumbnails/22.jpg)
Final Comments on Planning
• The book emphasizes three perspectives:– Planning, requirements, architecture.
• The end products with these perspectives are a software development plan, a requirements specification, and an architecture description document.
• On most successful projects, these thhree products are not very important once they have been produced.– Rarely used by performers on a day-to-day basis, they are
not very interesting to the end user, and the paper is just the tip of the iceberg with respect to the details that underlie them.
![Page 23: Eleventh Lecture Hour 9:30 – 10:20 am, Saturday, September 16 Software Management Disciplines Iterative Process Planning (from Part III, Chapter 10 of](https://reader030.vdocuments.net/reader030/viewer/2022013012/56649ed35503460f94be2ed7/html5/thumbnails/23.jpg)
Final Comments on Planning (cont’d)
• HOWEVER,– The act of planning is extremely important to project
success.– It provides a framework and forcing function for making
decisions.– It ensures buy-in by stakeholders and performers.– It transforms subjective, generic process frameworks into
objective processes.
• Finally, plans are not just for managers. An open and visible planning process results in more ownership among all team members who execute the plan.
![Page 24: Eleventh Lecture Hour 9:30 – 10:20 am, Saturday, September 16 Software Management Disciplines Iterative Process Planning (from Part III, Chapter 10 of](https://reader030.vdocuments.net/reader030/viewer/2022013012/56649ed35503460f94be2ed7/html5/thumbnails/24.jpg)
Assignment for Next Class Meeting
• Read Chapter 10 of Royce’ book, on iterative process planning.– Learn and discuss the similarities and the differences of top-level
organization of a conventional WBS and the top-level organization of a modern WBS.
– Learn and discuss the similarities and the differences between the four steps for a top-down cost and schedule estimate and the three steps for a bottom-up cost and schedule estimate.
– Learn and discuss the similarities and the differences of the contents of the iterations in each of the four development phases.