π Lecture 21 β Implementing PSP
π Overview: This lecture explores the Personal Software Process (PSP) as a disciplined framework for individual software engineers to plan, measure, and manage their work. It covers practical implementation strategies focusing on time management and commitment management, then details the four progressive PSP Process Levels that build from baseline measurement to cyclic development for larger projects.
ποΈ Topics Covered
The lecture introduces the PSP as a personal framework for software engineers, then focuses on the logic and strategies of time management including how time is spent and tracked using logs. It defines commitments and their responsible management, outlines the consequences of poor commitment handling, and describes the four PSP Process Levels: Baseline Personal Process, Personal Project Management, Personal Quality Management, and Cyclic Personal Process. Finally, it covers the three basic PSP measures (time, defects, size).
π Lecture Summary
PSP
The Personal Software Process (PSP) provides engineers with a disciplined personal framework for doing software work. The PSP process consists of a set of methods, forms, and scripts that show software engineers how to plan, measure, and manage their work. The PSP extends the improvement process to the people who actually do the workβthe practicing engineers. The PSP concentrates on the work practices of the individual engineers. The principle behind the PSP is that to produce quality software systems, every engineer who works on the system must do quality work. The PSP is designed to help software professionals consistently use sound engineering practices. It shows them how to plan and track their work, use a defined and measured process, establish measurable goals, and track performance against these goals. The PSP shows engineers how to manage quality from the beginning of the job, how to analyze the results of each job, and how to use the results to improve the process for the next project.
Implementing Personal Software Process
Key parts of implementing personal software process include managing time and managing commitments. A key part of implementing personal software process is managing time accurately. The lecture discusses time management issues and ways to record and store time.
Logic of Time Management
- You will likely spend your time this week much the way you spent it last week
- To make realistic plans, you have to track the way you spend time
- To check the accuracy of your time estimates and plans, you must document them and later compare them with what you actually do
- To make more accurate plans, determine where your plans were in error and what you could have done better
- To manage your time, plan your time and then follow the plan
Product Planning
Product planning involves the size and important features of the product to be produced, an estimate of the time required to do the work, a projection of the schedule, and the relationship between product and period planning.
How Time is Spent?
To manage time effectively, engineers must categorize their major activities, record the time spent on each major activity, record time in a standard way, and keep the time data in a convenient place such as an Engineering Notebook or electronic hand-held devices.
Tracking Time in PSP
When tracking time in PSP, the following data must be recorded: Date, Start time, Stop time, Interruption time, Delta time, Activity, Comments, whether it is Completed (or not), and Units.
Hints on Logging Your Time
- Keep the engineering notebook/hand-held device with you at all times
- When you occasionally forget to record the start time, stop time, or interrupt duration, make an estimate as soon as you remember
- You may use a stopwatch to track interruptions
- Summarize your time promptly
Managing Your Time
Managing time involves deciding how you want to spend your time, making a time budget, tracking the way you spend time against this budget, and deciding what changes to make to bring your actions into agreement with the budget.
Time Stealers
Common time stealers include: Interruptions (Telephone, Personal visitors), Meetings, Tasks you should have delegated, Procrastination and indecision, Acting with incomplete information, Dealing with team members, Crisis management (fire fighting), Unclear communication, Inadequate technical knowledge, Unclear objectives and priorities, Lack of planning, Stress and fatigue, Inability to say 'No', and Desk management and personal disorganization.
Suggestion on Managing Variable Time
Engineers should ask: What are your highest priority items? Are there some tasks that should be done at specific times? Are there activities you want to do as soon as you have time?
Time Management Strategies
- Always define your objectives as clearly as possible: Written goals, which can be reviewed regularly. Long term goals should impact daily activities. Without a goal or object, people tend to just drift personally and professionally.
- Analyze your use of time: Ask "What is the most important use of my time, right now?"
- Have a plan: Successful people make lists constantly. Change priorities on a regular basis.
- Action plan analysis: Problems will occur. A good plan identifies them early and seek out solutions. Good time management enables you to measure the progress towards your goals. What you can measure, you can control.
Defining Commitments
A commitment defines what will be done, the criteria for determining that it is done, who will do it, when it will be done, the compensation or other consideration to be given in return, and who will provide this compensation or consideration.
Responsibly Made Commitments
To make responsible commitments, engineers should analyze the job before agreeing to the commitment, support the commitment with a plan, document the agreement, and if unable to meet the commitment, promptly tell the other party and try to minimize the impact on that party.
Consequences of Not Managing Commitments
Not managing commitments leads to work required exceeding time available, failure to meet commitments, misplaced priorities, poor quality work, loss of trust, and loss of respect for your judgment.
PSP Process Levels
PSP has four process levels: The Baseline Personal Process, Personal Project Management, Personal Quality Management, and The Cyclic Personal Process.
The Baseline Personal Process
The baseline personal process provides an introduction to the PSP and establishes an initial base of historical size, time, and defect data. Basic process measurement and planning are introduced here. Development time, defects, and program size are measured and recorded on forms. A simple plan summary form is used to document planned and actual results. A form for recording process improvement proposals (PIPs) is also introduced. This form provides engineers with a convenient way to record process problems and proposed solutions.
Steps in Baseline PSP
| Step | Phase | Description |
|---|---|---|
| 1 | Plan | Plan the work and document the plan |
| 2 | Design | Design the program |
| 3 | Code | Implement the design |
| 4 | Compile | Compile the program and fix and log all defects found |
| 5 | Test | Test the program and fix and log all defects found |
| 6 | Postmortem | Record actual time, defect, and size data on the plan |
Personal Project Management
Personal project management techniques are the focus at this level, introducing size and effort estimating, schedule planning, and schedule tracking methods. The estimated size of the newly developed code is the sum of all new objects, plus any modifications or additions to existing base code. Predicted program size and effort are estimated using the statistical method linear regression. Linear regression makes use of the historical relationship between prior estimates of size and actual size and effort to generate predicted values for program size and effort. Finally, a prediction interval is calculated that gives the likely range around the estimate, based on the variance found in the historical data. The prediction interval can be used to assess the quality of the estimate. PSP uses the earned value method for schedule planning and tracking. The earned value method is a standard management technique that assigns a planned value to each task in a project. A task's planned value is based on the percentage of the total planned project effort that the task will take. As tasks are completed, the task's planned value becomes earned value for the project. The project's earned value then becomes an indicator of the percentage of completed work. When tracked week by week, the project's earned value can be compared to its planned value to determine status, to estimate rate of progress, and to project the completion date for the project.
Personal Quality Management
Quality management methods are added to the PSP at this level. These include: personal design and code reviews, a design notation, design templates, design verification techniques, and measures for managing process and product quality. The goal of quality management in the PSP is to find and remove all defects before the first compile. The measure associated with this goal is yield. Yield is defined as the percent of defects injected before compile that were removed before compile. A yield of 100% occurs when all the defects injected before compile are removed before compile. Design and code reviews help engineers achieve 100% yield. These are personal reviews conducted by an engineer on his/her own design or code. They are structured, data-driven review processes that are guided by personal review checklists derived from the engineer's historical defect data.
π Definition β Yield: The percent of defects injected before compile that were removed before compile.
Engineers also begin using the historical data to plan for quality and control quality during development. Their goal is to remove all the defects they inject before the first compile. During planning, they estimate the number of defects that they will inject and remove in each phase. Then they use the historical correlation between review rates and yield to plan effective and efficient reviews. During development, they control quality by monitoring the actual defects injected and removed versus planned, and by comparing actual review rates to established limits. With sufficient data and practice, engineers are capable of eliminating 60% to 70% of the defects they inject before their first compile.
The Cyclic Personal Process
The cyclic personal process addresses the need to efficiently scale the PSP up to larger projects without sacrificing quality or productivity. Productivity is highest between some minimum and maximum size range. Below this range, productivity declines due to fixed overhead costs. Above this range, productivity declines because the process scalability limit has been reached. At this level, this scalability limit is addressed by introducing a cyclic development strategy where large programs are decomposed into parts for development and then integrated. This strategy ensures that engineers are working at their maximum productivity and product quality levels, with only incremental, not exponential, increases in overhead for larger projects. At this level high-level design, high-level design review, cycle planning, and development cycles are introduced based on the personal quality management processes.
π‘ Why this matters: The cyclic process allows PSP principles to scale from small exercises to real-world industrial projects.
PSP Measures
There are three basic measures in the PSP: Development time, Defects, and Size. All other PSP measures are derived from these three basic measures.
Development Time Measure
Minutes are the unit of measure for development time. Engineers track the number of minutes they spend in each PSP phase, less time for any interruptions such as phone calls, coffee breaks, etc. Using minutes is precise and simplifies calculations involving development time. Recording interruptions to work reduces the number of time log entries, provides a more accurate measure of the actual time spent, and a more accurate basis for estimating actual development time. Tracking interruption time separately can help engineers deal objectively with issues that affect time management, such as a noisy work environment or inappropriate mix of responsibilities (e.g., software development and help desk support). Time log entries take substantially less than a minute to record, but provide a wealth of detailed historical data for planning, tracking, and process improvement.
Defect Measure
A defect is defined as any change that must be made to the design or code in order to get the program to compile or test correctly. Defects are recorded on the Defect Recording Log as they are found and fixed. The example Defect Recording Log shows the information that is recorded for each defect: the date, sequence number, defect type, phase in which the defect was injected, phase in which it was removed, fix time, and a description of the problem and fix. When an engineer injects a new defect while trying to fix an existing defect, proper accounting of fix time becomes more complicated. A common mistake is to include the fix time for the new defect twice. Each defect is classified according to a defect type standard. A standard and easy to use classification scheme should be used.
π Definition β Defect: Any change that must be made to the design or code in order to get the program to compile or test correctly.
Size Measure
The primary purpose of size measurement in the PSP is to provide a basis for estimating development time. Lines of code or function points can be used. Size is also used to normalize other data, such as productivity (LOC per hour) and defect density (defects per KLOC).
PSP Derived Measures
PSP introduces new measures to help engineers manage and improve their performance. These measures are derived from the three basic PSP measures: development time, defects, and size.
Why PSP?
As Watts Humphrey states: "When you trust your life to someone, you want them to behave professionally. Now consider your professional life. Should you entrust it to someone who is out of date? If you are looking for career guidance, would you ask someone who has not cracked a technical book since college? Probably not. The skill, knowledge, and ability you bring to your job will determine your future. Your future is in your hands."
β Key Takeaways
The PSP is a disciplined personal framework emphasizing that quality software requires quality work from every individual engineer. Effective implementation requires mastering time management through logging, budgeting, and tracking time using a standard format, and commitment management through analysis, planning, and documentation. The four PSP process levels progressively build capability: from baseline measurement (Plan-Design-Code-Compile-Test-Postmortem) to project management (size/effort estimation via linear regression and earned value tracking), to quality management (achieving high yield through personal reviews before first compile), and finally to cyclic development for scaling to larger projects without sacrificing productivity. The three fundamental PSP measuresβdevelopment time (in minutes), defects (logged with type and phase information), and sizeβserve as the foundation for all derived measures like yield, productivity, and defect density.
π§ Quick Revision Questions
- What are the three basic PSP measures, and from which measure is "yield" derived?
- List the six steps in the Baseline PSP process in order.
- What is the definition of "yield" in PSP quality management, and what is the goal value for yield?
- How does the earned value method work for schedule planning and tracking in PSP?
- What is the cyclic personal process, and why does it become necessary for larger projects?
π Lecture 22 β Review Up To Mid-Term
π Overview: This lecture provides a comprehensive review of all topics covered up to the midterm in the Software Process Improvement course. It covers the fundamental concepts of processes, software process models, capability maturity models (CMM and CMMI), and the Personal Software Process (PSP), emphasizing their importance in improving software development practices and organizational maturity.
ποΈ Topics Covered
The lecture reviews the definition and examples of processes, the distinction between technical and systemic software problems, software process characteristics and examples, process improvement objectives and planning, six steps to software improvement, levels of software process models (Universal, Worldly, Atomic), process modeling (ETVX, IDEF0), CMM-SW maturity levels (Initial through Optimizing), CMMI as an integrated framework, model representations (staged vs. continuous), CMMI model structure, benefits of CMMI, and an introduction to the Personal Software Process (PSP) and its key process areas.
π Lecture Summary
Process
A process is a documented solution to a problem that helps others facing similar challenges. Once someone figures out how to solve a problem, they can document that solution as a process. This process then helps other people get started on their own solutions for similar problems. Examples include an instruction manual for a dishwasher, a cookery book, a bank's procedures manual, and a software development quality manual.
Software Problems
Software problems are categorized into two types. Technical problems need a technical solution and are easy to understand and solve. Systemic problems need a process or management solution and are difficult to understand and solve. The solution to software problems involves treating the software task as a process that can be controlled, measured, and improved, and relating the required tasks, tools, and methods with the skill, training, and motivation of the people involved.
Software Processes
Software engineering has many processes that help perform different activities in an organized manner. A software process is the set of tools, methods, and practices that people use to produce software and associated products, such as project plans, design documents, code, test cases, and user manuals. People are the most important part of an organization.
Characteristics of Software Processes
Characteristics of software processes include requiring creativity, interactions between a wide range of different people, engineering judgment, background knowledge, and experience.
Examples of Software Processes
Examples include the Software Development Life Cycle (SDLC) , the requirements engineering process, the design process, the quality assurance process, and the change management process.
Process Improvement Objectives
The objectives of process improvement are quality improvement, schedule reduction, and resource reduction.
Process Improvements Planning
Process improvement planning involves asking: What are the improvement goals? How can we introduce process improvements to achieve these goals? How should improvements be controlled and managed?
Six Steps to Software Improvements
The six steps are:
- Understand the current status of development processes.
- Develop a vision for the desired process.
- Establish a list of required process improvement actions in order of priority.
- Produce a plan to accomplish the required actions.
- Commit the resources to execute the plan.
- Start over at step 1.
Levels of Software Process Models
There are three levels of software process models:
- Universal or U Process Models: Provide a high-level overview. Traditional Waterfall and Spiral models fall in this category. They are typically task-oriented.
- Worldly or W Process Models: Most useful to practicing software engineers. They guide the sequence of working tasks and define task prerequisites and results. They look like procedures.
- Atomic or A Process Models: Enormously detailed. They are used to automate a specific process activity or use a standardized method or procedure to guide execution of a task.
Process Modeling
Process modeling techniques include ETVX and IDEF0.
CMM-SW Levels
The five levels of the Capability Maturity Model for Software (CMM-SW) are:
- Initial
- Repeatable
- Defined
- Managed
- Optimizing
CMMI
CMMI (Capability Maturity Model Integration) was developed because people were successfully using the Capability Maturity Model, which was designed for improving software processes. This success brought attention to model-based process improvement in other areas. Historically, the model to use depended on the discipline (e.g., Software Engineering, Systems Engineering, Software Acquisition, Systems Security).
What is CMM?
A Capability Maturity Model (CMM) is a reference model of mature practices in a specified discipline, used to assess a group's capability to perform that discipline. CMMs differ by discipline (software, systems, acquisition, etc.), structure (staged versus continuous), how maturity is defined (process improvement path), and how capability is defined (institutionalization). Common CMMs include the Software CMM, System Engineering CMM, System Engineering Capability Model, Software Acquisition CMM, System Security Engineering CMM, Personal Software Process, FAA-iCMM, IPD-CMM, People CMM, and SPICE Model.
System and Software Divide
Systems and software disciplines have traditionally not been well integrated. The importance of software in systems has increased dramatically, creating a need to make the systems/software interface more seamless. Having many models with different structures, formats, terms, and ways of measuring maturity causes confusion, especially when using more than one model, and makes it hard to integrate them in a combined improvement program or use multiple models in supplier selection. CMMI comes to rescue by integrating systems and software disciplines into one process improvement framework and providing a framework for introducing new disciplines as needs arise. Systems engineering and software engineering processes are integrated, bridging the divide.
Models directly influencing CMMI
CMMI models combine System Engineering and Software Engineering into one model. It can be applied to just the software engineering projects, just the system engineering projects, or both in an organization.
Comparing Model Representations
- Staged Representation: The approach used in the Software CMM. It uses predefined sets of process areas to define an improvement path for an organization, described by model components called maturity levels. A maturity level is a well-defined evolutionary plateau toward achieving improved organizational processes.
- Continuous Representation: The approach used in the SECM and the IPD-CMM. It allows an organization to select a specific process area and improve relative to it. It uses capability levels to characterize improvement relative to an individual process area.
Process Area Capability and Organizational Maturity
Process area capability deals with a set of processes relating to a single process area or specific practice. Organizational maturity pertains to a set of process areas across an organization. It is important to remember that a model is not a process; the model shows what to do, NOT how to do it or who does it.
Why Do we have Two Representations?
The two representations exist due to source model heritage (Software CMMβStaged, SECMβContinuous, IPD CMMβHybrid). Proponents for each type were part of the CMMI product development team, and selecting a single representation approach became "too hard," so a compromise was made to initially support two representations with equivalent content.
Advantages of Staged Representation
The staged representation provides a roadmap for implementing groups of process areas and sequencing of implementation. It has a familiar structure for those transitioning from the SW-CMM.
Advantages of Continuous Representations
The continuous representation provides maximum flexibility for focusing on specific process areas according to business goals and objectives. It has a familiar structure for those transitioning from the systems engineering community.
CMMI in a Nutshell
A CMMI model provides a structured view of process improvement across an organization. It can help set process improvement goals and priorities, provide guidance for quality processes, and provide a yardstick for appraising current practices.
CMMI Model Structure
The CMMI model structure includes Maturity Levels (for staged representation) or Capability Levels (for continuous representation), Process Areas, Goals (Generic and Specific), and Practices (Generic and Specific). The CMMI product suite provides the latest best practices for product and service development and maintenance, improving on the best practices of previous models.
Benefits of CMMI
CMMI best practices enable organizations to:
- More explicitly link management and engineering activities to their business objectives.
- Expand the scope of and visibility into the product lifecycle and engineering activities to ensure the product or service meets customer expectations.
- Incorporate lessons learned from additional areas of best practices (e.g., measurement, risk management, and supplier management).
- Implement more robust high-maturity practices.
- Address additional organizational functions critical to their products and services.
- More fully comply with relevant ISO standards.
Use CMMI in process improvement activities as a collection of best practices, a framework for organizing and prioritizing activities, a support for the coordination of multi-disciplined activities, and a means to emphasize the alignment of process improvement objectives with organization business objectives.
What is PSP?
The Personal Software Process (PSP) is a defined and measured software process designed to be used by an individual software engineer. Developed by Watts Humphrey, its intended use is to guide the planning and development of software modules or small programs, but it is adaptable to other personal tasks. While the CMM-SW focuses on improving organizational capability, the focus of the PSP is the individual engineer.
Key Process Areas for PSP
Key process areas for PSP include Software Project Planning, Software Project Tracking/Oversight, Software Process Focus, Software Process Definition, Integrated Software Management, Software Product Engineering, Peer Reviews, Quantitative Process Management, Quality Management, Defect Prevention, Technology Change Management, and Process Change Management.
PSP in a Nutshell
PSP involves baselining your existing personal software process, developing a planning process for your software development, measuring and estimating software size, estimating schedule and resources, conducting appropriate measures of one's process, conducting meaningful design and code reviews, performing software quality management, performing formal software design, verifying the design using methods such as object state machines and program tracing, and scaling up the PSP to larger problems.
β Key Takeaways
This lecture reviewed the entire course up to the midterm. The core concepts are that a software process is a defined set of tools and methods used by people to produce software, and that systematic improvement is essential, often following a six-step cycle. The CMM-SW provides a staged path for organizational maturity from Initial to Optimizing, while CMMI integrates this with other disciplines using both staged and continuous representations for maximum flexibility. Finally, the PSP applies these same improvement principles to the individual engineer to improve personal productivity and quality.
π§ Quick Revision Questions
- What are the three objectives of process improvement?
- Name the five levels of the Software CMM (CMM-SW) in order.
- What is the key difference between Universal (U) Process Models and Worldly (W) Process Models?
- What are the two representations of the CMMI model, and what is the primary advantage of each?
- How does the scope of the Personal Software Process (PSP) differ from that of the CMM-SW?