π Lecture 36 β People Capability Maturity Model β 1
π Overview: This lecture introduces the People Capability Maturity Model (People CMM), a framework for managing and developing an organization's workforce. It explains how the People CMM applies the process maturity framework from the SW-CMM to workforce practices, helping organizations attract, train, deploy, and retain talent. The lecture covers the principles of the People CMM, the critical success factors for managing human capital, and the five maturity levels that guide an organization from ad hoc workforce practices to continuous improvement.
ποΈ Topics Covered
The lecture begins by introducing the People CMM as a tool for addressing critical people issues, based on best practices from human resources, knowledge management, and organizational development. It explores the philosophy behind the model through ten principles and seven principles of workforce management from Jeffrey Pfeffer. The lecture then examines four human capital cornerstones for strategic management, the process maturity framework adapted from Humphrey, and a detailed breakdown of each of the five maturity levels from Initial (Level 1) to Optimizing (Level 5). Finally, it lists types of organizations using People CMM globally.
π Lecture Summary
People Capability Maturity Model β 1
The People Capability Maturity Model (People CMM) is a tool that helps organizations successfully address critical people issues in managing and developing their workforce. It employs the process maturity framework of the Capability Maturity Model for Software (SW-CMM) as a foundation for best practices in fields like human resources, knowledge management, and organizational development. The People CMM helps organizations characterize the maturity of their workforce practices, establish a program of continuous workforce development, set priorities for improvement, integrate workforce development with process improvement, and establish a culture of excellence. Since its release in 1995, it has been used worldwide by organizations like IBM, Boeing, and Tata Consultancy Services. The primary objective of the People CMM is to improve the capability of the workforce.
π Definition β Workforce Capability: The level of knowledge, skills, and process abilities available for performing an organizationβs business activities. It indicates an organizationβs readiness for performing critical business activities, likely results from these activities, and potential for benefiting from process improvement or advanced technology.
π Definition β Workforce Competency: A unique integration of knowledge, skills, and process abilities acquired through specialized education or work experience. The workforce must be divided into its constituent workforce competencies to measure and improve capability.
π‘ Why this matters: The People CMM provides an evolutionary improvement path from ad hoc, inconsistently performed workforce practices to a mature infrastructure for continuously elevating workforce capability, directly linking workforce capability to business performance.
Principles of People CMM β 1
The philosophy of the People CMM is summarized in ten principles:
- In mature organizations, workforce capability is directly related to business performance.
- Workforce capability is a competitive issue and a source of strategic advantage.
- Workforce capability must be defined in relation to the organizationβs strategic business objectives.
- Knowledge-intense work shifts the focus from job elements to workforce competencies.
- Capability can be measured and improved at multiple levels, including individuals, workgroups, workforce competencies, and the organization.
- An organization should invest in improving the capability of those workforce competencies critical to its core competency.
- Operational management is responsible for the capability of the workforce.
- The improvement of workforce capability can be pursued as a process composed from proven practices and procedures.
- The organization is responsible for providing improvement opportunities, and individuals are responsible for taking advantage of them.
- Because technologies and organizational forms evolve rapidly, organizations must continually evolve their workforce practices and develop new workforce competencies.
The People CMM narrows the scope of improvement activities to the vital few practices that provide the next foundational layer for developing the organizationβs workforce.
Seven Principle of Workforce Management
Jeffrey Pfeffer, in his book The Human Equation, identified seven principles of workforce management that distinguished companies with the largest percentage stock market returns:
- Employment security
- Selective hiring of new personnel
- Self-managed teams and decentralization of decision making
- Comparatively high compensation contingent on organizational performance
- Extensive training
- Reduced status distinctions and barriers
- Extensive sharing of financial and performance information
These principles characterize organizations where employees act as independent centers of intelligent action coordinated toward a common purpose. Deep technical and business knowledge is required for rapid, consistent decisions.
Critical Success Factors for Managing Human Capital Strategically
Four Human Capital Cornerstones are identified:
- Leadership: Commitment to Human Capital Management; Role of the Human Capital Function.
- Strategic Human Capital Planning: Integration and Alignment; Data-Driven Human Capital Decisions.
- Acquiring, Developing, and Retaining Talent: Targeted Investments in People; Human Capital Approaches Tailored to Meet Organizational Needs.
- Results-Oriented Organizational Cultures: Empowerment and Inclusiveness; Unit and Individual Performance Linked to Organizational Goals.
Process Maturity Framework
Humphrey designed the process maturity framework to enable an organization to achieve a state of continuous process improvement in five stages. This framework is more than a process standard; it integrates improved practices into a staged model that guides an organization through a series of cultural transformations. Over a dozen years of experience demonstrates this framework is applicable to the management and improvement of workforce practices.
First Level of Maturity
At the Initial Level (Level 1), an organization has no consistent way of performing its work. Work processes are ad hoc, constantly reinvented, and frequently appear chaotic. Managers have no reliable basis for estimating effort, leading to overly aggressive deadlines, cutting corners, and mistakes that are costly to fix. Projects lose control of schedule, costs, and product quality. Results depend largely on the skills of exceptional individuals and excessive overtime.
Second Level of Maturity
At the Repeatable Level (Level 2), organizations must establish a foundation for deploying common processes. Management must first establish a stable environment for professional work, ensuring people are not constantly rushing or fighting fires. The primary objective is to enable people to repeat practices they have used successfully.
Third Level of Maturity
At the Defined Level (Level 3), the organization identifies its best practices and integrates them into a common process. Once people can perform work using practices that work, the organization identifies which practices work best. These practices are documented and integrated into a common process in which the entire organization is trained. Measures of critical practices are defined and collected into a repository for analysis.
Fourth Level of Maturity
At the Managed Level (Level 4), the organization begins managing its processes through data that describes its performance. The performance of the organizationβs critical processes is characterized statistically so that historical performance can be used to predict and manage future performance.
Fifth Level of Maturity
At the Optimizing Level (Level 5), the organization uses its profound, quantitative knowledge to make continuous improvements. Based on data, the organization identifies which processes can benefit most from improvement actions. The maturity framework builds an environment where:
- Practices can be repeated.
- Best practices can be transferred rapidly across groups.
- Variations in performing best practices are reduced.
- Practices are continuously improved to enhance their capability.
Types of organizations around the world using the People CMM
Industries using the People CMM include: Business Process Outsourcing, Information Technology, Hospitality Consulting, Construction, Defense Contractors, Insurance Pharmaceuticals, Government Agencies/Defense Agencies, Energy/Utilities, Software Development, Banking/Financial Services Management, and Information Systems.
Maturity Levels of the People CMM
The People CMM applies the principles of the process maturity framework to the domain of workforce practices. Each of its five maturity levels represents a different level of organizational capability for managing and developing the workforce. Each maturity level provides a layer in the foundation for continuous improvement. When institutionalized, these workforce practices create new capabilities within the organization.
β Key Takeaways
The People CMM is a staged framework based on the process maturity model, designed specifically to improve workforce capabilityβthe level of knowledge, skills, and process abilities in an organization. Its philosophy is rooted in ten principles, including that workforce capability is a competitive issue directly linked to business performance, and that improvement can be pursued as a process. The five maturity levels guide an organization from an ad hoc, chaotic Initial Level through Repeatable, Defined, Managed, and finally to an Optimizing Level where data-driven continuous improvement occurs. A key concept is the division of the workforce into competencies, and the identification of critical success factors like leadership, strategic planning, talent management, and results-oriented culture. Finally, the lecture emphasizes that the People CMM provides an evolutionary path, not just a list of best practices, to build a mature infrastructure for workforce excellence.
π§ Quick Revision Questions
- What is the primary objective of the People Capability Maturity Model (People CMM)?
- Define "workforce capability" and explain why it is important for an organization.
- List the four human capital cornerstones that are critical for managing human capital strategically.
- Describe the key difference in workforce management between an organization at Maturity Level 1 (Initial) and one at Maturity Level 5 (Optimizing).
- According to Jeffrey Pfeffer's seven principles, what are two specific practices that distinguish companies with the largest stock market returns?
π Lecture 37 β People CMM β 2
π Overview: This lecture continues the exploration of the People Capability Maturity Model (People CMM) by detailing the characteristics and process areas of its five maturity levels. It explains how organizations progress from ad hoc workforce practices at the Initial Level to a culture of continuous improvement at the Optimizing Level. Understanding these levels is critical for systematically improving an organization's workforce capability and strategic alignment.
ποΈ Topics Covered
This lecture covers the five maturity levels of the People CMM: Initial Level (Level 1), Managed Level (Level 2), Defined Level (Level 3), Predictable Level (Level 4), and Optimizing Level (Level 5). For each level, the key characteristics, focus, and specific process areas are defined, with detailed explanations of how workforce practices evolve and become more sophisticated as maturity increases.
π Lecture Summary
The Initial Level: Maturity Level 1
Organizations at the Initial Level of maturity usually have difficulty retaining talented individuals. Even though many low-maturity organizations complain about a talent shortage, the inconsistency of their actions belies whether they actually believe it. Low-maturity organizations are poorly equipped to respond to talent shortages with anything other than slogans and exhortations. Despite the importance of talent, workforce practices in low-maturity organizations are often ad hoc and inconsistent. In some areas, the organization has not defined workforce practices, and in other areas, it has not trained responsible individuals to perform the practices that exist. Organizations at the Initial Level typically exhibit four characteristics: inconsistency in performing practices, displacement of responsibility, ritualistic practices, and an emotionally detached workforce. Generally, managers and supervisors in low-maturity organizations are ill-prepared to perform their workforce responsibilities and their management training is sparse. Low-maturity organizations implicitly assume that management skill either is innate or is acquired by observing other managers. Management capability should ultimately be defined as a competency, just like other critical skill sets that are required by the organization. Since low-maturity organizations rarely clarify the responsibilities of managers, inconsistencies are to be expected. Consequently, the way people are treated depends largely on personal orientation, experience, and the individual "people skills" of their managers, supervisors, or team leaders. Studies have consistently shown that one of the major causes for voluntary turnover is related to individuals' relationships with their managers or supervisors. The first step in changing this state of affairs is to get managers to take responsibility for the capability and development of those who report to them.
π Definition β Ritualistic Practices: [Not explicitly defined in the text, but inferred as] Performing workforce activities without genuine understanding or commitment, simply as a routine or ceremony, rather than for their intended purpose.
π Example: An organization that requires annual performance reviews but managers complete them superficially without providing meaningful feedback or development goals.
The Managed Level: Maturity Level 2
The first step toward improving the capability of the workforce is to get managers to take workforce activities as high-priority responsibilities of their job. They must accept personal responsibility for the performance and development of those who perform the unit's work. The practices implemented at Maturity Level 2 focus a manager's attention on unit level issues such as staffing, coordinating commitments, providing resources, managing performance, developing skills, and making compensation decisions. Building a solid foundation of workforce practices in each unit provides the bedrock on which more sophisticated workforce practices can be implemented at higher levels of maturity. Maturity Level 2 focuses on establishing basic practices in units that address immediate problems and prepare managers to implement more sophisticated practices at higher levels. In a Maturity Level 2 organization, managers are vigilant for problems that hinder performance in their units. These problems include work overload, environmental distractions, unclear performance objectives or feedback, lack of relevant knowledge or skill, poor communication, and low morale. The effort to ensure that workforce practices are performed in each unit begins when executive management commits the organization to continuously improve the knowledge, skills, motivation, and performance of its workforce. Executive management manifests these commitments in policies and provides the resources needed to support unit-level implementation of basic workforce practices. Through policies and accountability, executive management communicates that managers are to accept personal responsibility for ensuring that workforce practices are implemented effectively in their units. In applying the People CMM, it is important to distinguish between management and managers. There are responsibilities that need to be managed and there are people called managers, but there is no required one-to-one mapping between them. At Maturity Level 2, units become stable environments for performing work and are able to balance their commitments with available resources. At Maturity Level 2, an organization's capability for performing work is best characterized by the capability of units to meet commitments. This capability is achieved by ensuring that people have the skills needed to perform their assigned work and that performance is regularly discussed to identify actions that can improve it. Measurements of status and performance of these workforce activities provide management with a means of monitoring and ensuring appropriate performance of workforce practices. One of the first benefits organizations experience when they implement improvements guided by the People CMM is a reduction in voluntary turnover. At Maturity Level 2, the People CMM addresses one of the most frequent causes of turnoverβpoor relations with the immediate supervisor. The process areas of Level 2 include:
- Staffing: to establish a formal process by which committed work is matched to unit resources and qualified individuals are recruited, selected, and transitioned into assignments.
- Communication and Coordination: to establish timely communication throughout the organization and to ensure that the workforce has the skills to share information and coordinate activities efficiently.
- Work Environment: to establish and maintain physical working conditions and to provide resources that allow individuals and workgroups to perform their tasks efficiently without unnecessary distractions.
- Performance Management: to establish objectives related to committed work against which unit and individual performance can be measured, to discuss performance against these objectives, and to continuously enhance performance.
- Training and Development: to ensure that all individuals have the skills required to perform their assignments and are provided relevant development opportunities.
- Compensation: to provide all individuals with remuneration and benefits based on their contribution and value to the organization.
π Definition β Managed Level (Maturity Level 2): The maturity level where managers take personal responsibility for their unit's performance and development, and basic workforce practices like staffing, performance management, and training are established.
π Example: A unit manager at Level 2 ensures that each team member has clear performance objectives, receives regular feedback, and has the necessary skills and resources to meet their commitments.
The Defined Level: The Level 3
Once a foundation of basic workforce practices has been established in the units, the next step is for the organization to develop an organization-wide infrastructure building on these practices that ties the capability of the workforce to strategic business objectives. The primary objective of the Defined Level is to help an organization gain a competitive advantage by developing the various competencies that must be combined in its workforce to accomplish its business activities. These workforce competencies represent the critical pillars that support the strategic business plan; their absence poses a severe risk to strategic business objectives. In tying workforce competencies to current and future business objectives, the improved workforce practices implemented at Maturity Level 3 become critical enablers of business strategy. The concept of workforce competencies implemented in the People CMM differs from the concept of "core competency." Core competency refers to an organization's combination of technology and production skills that create its products and services and provide its competitive advantage in the marketplace. In the People CMM, workforce competencies reside one level of abstraction below an organization's core competency. Each workforce competency represents a distinct integration of the knowledge, skills, and process abilities required to perform some of the business activities that contribute to an organization's core competency. The range of workforce competencies an organization must integrate depends on the breadth and type of business activities that comprise its core competencies. Therefore, these workforce competencies are a strategic underpinning (foundation) of the organization's core competencies. By defining process abilities as a component of a workforce competency, the People CMM becomes linked with the process frameworks established in other CMMs and with other process-based methods, such as business process reengineering. A process ability is demonstrated by performing the competency-based processes appropriate for an individual's required workforce competency. To define the process abilities incorporated in each workforce competency, the organization defines the competency-based processes that an individual would be expected to perform in accomplishing his or her committed work. Within a workforce competency, a competency-based process defines how individuals apply their knowledge, perform their skills, and apply their process abilities in the context of the organization's defined work processes. At Maturity Level 3, the organization builds an organization-wide framework of workforce competencies that establishes the architecture of the organization's workforce. Each workforce competency is an element of the workforce architecture, and dependencies among competency-based processes describe how these architectural elements interact. The architecture of the organization's workforce must evolve as business conditions and technologies change. Because workforce competencies are strategic, the organization must develop strategic workforce plans for ensuring the required capability in each of its current or anticipated workforce competencies. When the processes to be performed by each workforce competency are defined, the organization has a new foundation for developing workgroups. Competency-based processes form a basis for defining workgroup roles and operating processes. Workgroups can now organize themselves by tailoring and applying standard competency-based processes. A common organizational culture typically develops as the organization achieves the Defined Level. This culture is best described as one of professionalism, since it is built from common understanding of the knowledge and skills that need to be developed to achieve superior levels of performance and a definition of the competency-based processes that such individuals perform. Since these workforce competencies are strategic to the business, the organization reinforces their importance by developing and rewarding them. As a result, the entire workforce begins to share responsibility for developing increasing levels of capability in the organization's workforce competencies. The workforce practices that were implemented at Maturity Level 2 are now standardized and adapted to encourage and reward growth in the organization's workforce competencies. The process areas of Level 3 include:
- Competency Analysis: to identify the knowledge, skills, and process abilities required to perform the organization's business activities so that they may be developed and used as a basis for workforce practices.
- Workforce Planning: to coordinate workforce activities with current and future business needs at both the organizational and unit levels.
- Competency Development: to enhance constantly the capability of the workforce to perform its assigned tasks and responsibilities.
- Career Development: to ensure that individuals are provided opportunities to develop workforce competencies that enable them to achieve career objectives.
- Competency-Based Practices: to ensure that all workforce practices are based in part on developing the competencies of the workforce.
- Workgroup Development: to organize work around competency-based process abilities.
- Participatory Culture: to enable the workforce's full capability for making decisions that affect the performance of business activities.
π Definition β Workforce Competency: A distinct integration of the knowledge, skills, and process abilities required to perform business activities that contribute to an organization's core competency and strategic objectives.
π Example: A software company might define a "Software Design" workforce competency that includes knowledge of design patterns, skills in using UML, and process abilities in performing design reviews. This competency supports the company's core competency of developing high-quality software products.
The Predictable Level: Maturity Level 4
At the Predictable Level, the organization manages and exploits the capability created by its framework of workforce competencies. This framework is sustained through formal mentoring activities. The organization is now able to manage its capability and performance quantitatively. The organization is able to predict its capability for performing work because it can quantify the capability of its workforce and of the competency-based processes they use in performing their assignments. There are at least three ways in which the framework of workforce competencies enables the organization to more fully use the capabilities of its workforce. First, when competent people perform their assignments using proven competency-based processes, management trusts the results they produce. This trust enables the organization to preserve the results of performing competency-based processes and develop them as organizational assets to be reused by others. In essence, people trust the asset because they trust the methods through which it was produced. When these assets are created and used effectively, learning spreads rapidly through the organization and productivity rises when reuse replaces redevelopment. Second, this trust also gives managers the confidence they need to empower workgroups. Managers will transfer responsibility and authority for committed work into workgroups only if they believe the members of the workgroup are competent to perform the work and use processes that have been proven effective. In achieving Maturity Level 4, management senses less risk in empowering workgroups and is willing to delegate increasingly greater levels of authority for managing day-to-day operations and for performing some of their own workforce practices. Increasingly free of managing operational details, managers at Maturity Level 4 are able to turn their attention to more strategic issues. Third, when members of each workforce competency community have mastered their competency-based processes, the organization is able to integrate different competency-based processes into a single multidisciplinary process. An example would be the integration of software and hardware design processes into a single product design process in which different competency-based processes are interwoven at every point where they share a potential dependency. Such multidisciplinary processes have proven to accelerate business results. In addition to exploiting the possibilities enabled by the competency framework, the organization begins to manage its capability quantitatively. Within each unit or workgroup, the performance of competency-based processes most critical for accomplishing business objectives is measured. These measures are used to establish process performance baselines that can be used to manage competency-based processes and assess the need for corrective action. The combined availability of workforce capability baselines and process capability baselines for competency-based processes enables both unit and organizational performance to become more predictable. These data allow management to make more accurate predictions about performance and better decisions about tradeoffs involving workforce capability or process performance issues. The quantitative management capabilities implemented at Maturity Level 4 provide management with better input for strategic decisions, while encouraging delegation of operational details to people close to the processes. The process areas of Level 4 include:
- Competency Integration: to improve the efficiency and agility of interdependent work by integrating the process abilities of different workforce competencies.
- Empowered Workgroups: to invest workgroups with the responsibility and authority to determine how to conduct their business activities most effectively.
- Competency-Based Assets: to capture the knowledge, experience, and artifacts developed in performing competency-based processes for use in enhancing capability and performance.
- Quantitative Performance Management: to predict and manage the capability of competency-based processes for achieving measurable performance objectives.
- Organizational Capability Management: to quantify and manage the capability of the workforce and of the critical competency-based processes it performs.
- Mentoring: to transfer the lessons of greater experience in a workforce competency to improve the capability of other individuals or workgroups.
π Definition β Competency-Based Assets: The knowledge, experience, and artifacts developed from performing competency-based processes that are captured for reuse to enhance capability and performance.
π Example: A design team creates a reusable library of software components and design documents from a successful project. This asset, created using a proven design process, is trusted and reused by other teams, accelerating future development.
The Optimizing Level: Maturity Level 5
At the Optimizing Level, the entire organization is focused on continual improvement. These improvements are made to the capability of individuals and workgroups, to the performance of competency-based processes, and to workforce practices and activities. The organization uses the results of the quantitative management activities established at Maturity Level 4 to guide improvements at Maturity Level 5. Although several individuals may be performing identical competency-based processes, they frequently exhibit individual differences in the methods and work styles they use to perform their assignments. At Maturity Level 5, individuals are encouraged to make continuous improvements to their personal work processes by analyzing their work and making necessary process enhancements. So is true for workgroups. Although individuals and workgroups continually improve their performance, the organization must be vigilant to ensure that performance at all levels remains aligned with organizational objectives. At Maturity Level 5, the process performance data collected across the organization is evaluated to detect instances of misalignment. Further, the impact of workforce practices and activities is evaluated to ensure that they encourage rather than discourage alignment. Corrective action is taken to realign performance objectives and results when necessary. The process areas of Level 5 include:
- Continuous Capability Improvement: to provide a foundation for individuals and workgroups to continuously improve their capability for performing competency-based processes.
- Organizational Performance Alignment: to enhance the alignment of performance results across individuals, workgroups, and units with organizational performance and business objectives.
- Continuous Workforce Innovation: to identify and evaluate improved or innovative workforce practices and technologies, and implement the most promising ones throughout the organization.
π Definition β Organizational Performance Alignment: The process of ensuring that performance results at all levels (individual, workgroup, unit) are aligned with organizational performance and business objectives.
π Example: An organization collects performance data from all teams and identifies that one team's focus on speed is causing quality issues, misaligning with the organization's strategic objective of high-quality products. Corrective action is taken to realign their performance objectives.
β Key Takeaways
The People CMM provides a structured path for organizations to systematically improve their workforce capability. The journey begins at the Initial Level (1), characterized by ad hoc and inconsistent practices, and progresses through the Managed Level (2) where managers take responsibility for unit-level practices like staffing and performance management. The Defined Level (3) shifts the focus to strategic alignment by identifying and developing workforce competencies that support core business objectives, creating an organization-wide infrastructure. The Predictable Level (4) enables the organization to manage capability quantitatively, using data to make performance predictions and empower workgroups, while the Optimizing Level (5) fosters a culture of continuous improvement where individuals and teams constantly enhance their processes, and all performance is kept aligned with strategic goals. Throughout this progression, each level builds upon the foundation of the previous one, transforming workforce practices from an afterthought into a strategic enabler.
π§ Quick Revision Questions
- What are the four typical characteristics exhibited by organizations at the Initial Level (Maturity Level 1)?
- What is the primary focus of the Managed Level (Maturity Level 2), and what is one of its first measurable benefits?
- How does the People CMM's concept of a "workforce competency" differ from an organization's "core competency"?
- What three key benefits does the framework of workforce competencies enable at the Predictable Level (Maturity Level 4)?
- What is the primary role of quantitative performance data at the Optimizing Level (Maturity Level 5)?
π Lecture 38 β Introduction to Measurements
π Overview: This lecture introduces the fundamental concepts of software measurement, explaining why it has become essential for good software engineering practice. It formally defines measurement, explores the distinction between entities and attributes, and discusses the consequences of neglecting measurement in software projects while outlining its key objectives and scope.
ποΈ Topics Covered
This lecture begins by establishing the pervasive nature of measurement in everyday life and technology, then formally defines measurement as the assignment of numbers or symbols to attributes of entities according to clearly defined rules. It explores the critical distinction between entities (objects/events) and their attributes (features/properties), raises difficult philosophical questions about what constitutes valid measurement, and distinguishes between direct measurement and indirect calculation. The lecture then addresses the neglect of measurement in software engineering, outlines objectives for software measurement from management and engineering perspectives, explains the importance of measurement for understanding, controlling, and improving processes and products, and finally surveys the broad scope of software metrics including cost estimation, productivity, quality, reliability, performance, complexity, and capability maturity assessment.
π Lecture Summary
Introduction to Measurements β Software measurement
Software measurement, once considered an obscure specialty, has become essential to good software engineering. Many of the best software developers measure characteristics of the software to get some sense of whether the requirements are consistent and complete, or whether the code is ready to be tested. Effective project managers measure attributes of process and product to tell when the software will be ready for delivery and whether the budget will be exceeded. Informed customers measure aspects of the final product to determine if it meets requirements and is of sufficient quality.
Measurement lies at the heart of many systems that govern our lives. Economic measurements determine price and pay increases. Measurements in radar systems enable us to detect aircraft when direct vision is obscured. Medical system measurements enable doctors to diagnose specific illnesses, and measurements in atmospheric systems form the basis for weather prediction. Without measurement, technology cannot function. Measurement is not solely the domain of professional technologists; each of us uses it in everyday life, such as using price as a measure of value, using height/weight/size for clothing, or calculating distance and speed for a journey.
In every case, some aspect of a thing is assigned a descriptor that allows us to compare it with others β we compare the price of one item with another, contrast clothing sizes, or compare distance travelled to distance remaining. The rules for assignment and comparisons are made according to a well-defined set of rules.
Measurement
Measurement is the process by which numbers or symbols are assigned to attributes of entities in the real world in such a way as to describe them according to clearly defined rules. Thus, measurement captures information about attributes of entities.
An entity is an object or an event in the real world, such as a person, a room, a journey, or the testing phase of a software project. We describe the entity by identifying characteristics important to us in distinguishing one entity from another. An attribute is a feature or property of an entity, such as the area or color of a room, the cost of a journey, or the elapsed time of the testing phase.
We often talk about entities and their attributes interchangeably in everyday speech ("it is cold today" actually means the air temperature is cold, or "Usman is taller than Ali" means his height is greater). This loose terminology is acceptable for everyday speech but is incorrect and unsuitable for scientific endeavors. It is wrong to say that we measure things or that we measure attributes; in fact, we measure attributes of things. It is ambiguous to say "we measure a room" since we can measure its length, area, or temperature. Similarly, it is ambiguous to say "we measure the temperature" since we measure the temperature of a specific geographical location under specific conditions.
We can describe entities by using attributes, often defining the attributes using numbers or symbols β price can be designated as Rupees or dollars, clothing size may be "small", "medium", or "large". These numbers and symbols are abstractions that reflect our perceptions of the real world. In defining them, we try to preserve certain relationships among entities, such that someone who is six feet in height is taller than someone who is five feet, and a "medium" T-shirt is smaller than a "large" T-shirt.
Measurement is a process whose definition is far from clear-cut, and many different authoritative views lead to different interpretations. To understand what measurement is, we must ask difficult questions:
- In a room with blue walls, is "blue" a measure of the color of the room?
- Is intelligence adequately measured by an IQ test score? Can soft drink quality be measured using expert ratings?
- Some measures are not likely to be accurate because the measurement is imprecise or depends on judgment β is this a reason to reject them as bona fide measurements?
- Even with reliable devices, there is a margin of error β how do we decide which error margins are acceptable?
- Different scales measure the same attribute (meters, inches, feet for height) β when is a scale acceptable for the purpose to which it is put?
- Why is it acceptable to say Fred is twice as tall as Joe, but not to say it is twice as hot today as yesterday? Why is it meaningful to calculate the mean of heights but not the mean of football jersey numbers?
π‘ Why this matters: The concepts of time, temperature, and speed, once unmeasurable by primitive peoples, are now commonplace and easily measured. To improve the rigor of measurement in software engineering, we need not restrict the type or range of measurements we can make. Measuring the unmeasurable should improve our understanding of entities and attributes, making software engineering as powerful as other engineering disciplines.
There are two kinds of quantification: measurement and calculation. Measurement is a direct quantification of something, as in measuring the height of a tree or weight of a shipment of bricks. Calculation is indirect, where we take measurements and combine them into a quantified item reflecting some attribute whose value we are trying to understand β for example, valuation of a house for tax purposes, or in the decathlon athletics event where measures of running times and jumping distances are combined into an overall score using a complex weighting scheme.
Neglect of Measurements in SE
Measurement has been considered a luxury in software engineering. We fail to set measurable targets for our software products, promising that the product will be user-friendly, reliable, and maintainable without specifying clearly what these terms mean. As a result, when the project is complete, we cannot tell if we have met our goals. Projects without clear goals will not achieve their goals clearly.
We fail to understand and quantify the component costs of software projects β most projects cannot differentiate the cost of design from the cost of coding and testing. Since excessive cost is a frequent complaint, we cannot hope to control costs if we are not measuring the relative components of cost. We do not quantify or predict the quality of the products we produce, so we cannot tell a potential user how reliable a product will be in terms of likelihood of failure, or how much work will be needed to port it to a different environment. We allow anecdotal evidence to convince us to try new technologies without doing carefully controlled studies to determine if the technology is efficient and effective.
Objectives for Software Measurements
Even when a project is not in trouble, measurement is not only useful but necessary β how can you tell if your project is healthy if you have no measures of its health? Measurement is needed at least for assessing the status of your projects, products, processes, and resources.
From managers' perspectives, key objectives include: What does each process cost? How productive is the staff? How good is the code being developed? Will the user be satisfied with the product? How can we improve?
Importance of Measurement
Measurement is important for three basic activities:
First, there are measures that help us to understand what is happening during development and maintenance. We assess the current situation, establishing baselines that help us set goals for future behavior. The measurements make aspects of process and product more visible to us, giving us a better understanding of relationships among activities and the entities they affect.
Second, measurement allows us to control what is happening on our projects. Using our baselines, goals, and understanding of relationships, we predict what is likely to happen and make changes to processes and products that help us meet our goals. For example, we may monitor the complexity of code modules, giving thorough review only to those that exceed acceptable bounds.
Third, measurement encourages us to improve our processes and products. For instance, we may increase the number or type of design reviews based on measures of specification quality and predictions of likely design quality. You can neither predict nor control what you cannot measure.
Scope of Software Metrics
Software metrics embraces many activities involving some degree of software measurement:
-
Cost and effort estimation: Managers provided original motivation for deriving and using software measures to predict costs during early phases. Many models are available to express cost and size.
-
Productivity models and measures: Numerous attempts have defined measures and models for assessing staff productivity during different software processes and in different environments.
-
Data collection: The quality of any measurement program depends on careful data collection. Consistent and accurate data collection is very difficult. Metrics data collection must be planned and executed in a careful and sensitive manner.
-
Quality models and measures: Productivity cannot be viewed in isolation without an accompanying assessment of product quality. A number of quality models have measurements that can be combined with those of productivity models.
-
Reliability models: Most quality models include reliability as a component factor, but the need to predict and measure reliability itself has led to a separate specialization in reliability modeling and prediction.
-
Performance evaluation and models: Performance evaluation includes externally observable system performance characteristics such as response times and completion rates, as well as investigation of internal workings including algorithmic efficiency and complexity.
-
Structural and complexity metrics: Desirable quality attributes like reliability and maintainability cannot be measured until operational code is available, yet we wish to predict which parts of the system are likely to be less reliable or more difficult to test. We measure structural attributes of software representations available in advance of execution, then try to establish empirically predictive theories for quality assurance, quality control, and quality prediction.
-
Management by metrics: Measurement is becoming an important part of software project management. Customers and developers rely on measurement-based charts and graphs to decide if the project is on track. It is important to collect measures in a standard format for comparisons and contrast.
-
Evaluation of methods and tools: To select a method or tool for adoption, investigations in the form of experiments, case studies, or surveys must be done before incorporation into an organization. These investigations cannot be done without careful, controlled measurement and analysis.
-
Capability maturity assessment: SEI proposed capability maturity assessments to evaluate contractors, in use since the 1980s using quality models. Capability maturity assessment is based on key practices that every good contractor should be using. Other organizations are using their own capability assessments.
β Key Takeaways
Measurement is the process of assigning numbers or symbols to attributes of entities according to clearly defined rules, distinguishing sharply between entities (objects/events) and their attributes (features/properties). Software engineering has historically neglected measurement by failing to set measurable targets, quantify costs, predict quality, and control processes, making measurement essential for understanding current status, controlling ongoing work, and improving future outcomes. The scope of software metrics is broad and includes cost estimation, productivity assessment, quality and reliability modeling, performance evaluation, structural complexity analysis, and capability maturity assessment. Students must remember that measurement and calculation are distinct β measurement is direct quantification while calculation is indirect combination of measures β and that the ultimate goal of software measurement is to make software engineering as rigorous and powerful as other engineering disciplines.
π§ Quick Revision Questions
- What is the formal definition of measurement, and why is it incorrect to say "we measure a room" or "we measure the temperature"?
- What is the difference between an entity and an attribute, and why must this distinction be maintained in scientific measurement?
- What are the three basic activities for which measurement is important in software engineering, and how does each contribute to process and product success?
- What are the consequences of neglecting measurement in software engineering, particularly regarding project goals, cost control, and quality prediction?
- List and briefly describe at least five different areas within the scope of software metrics, explaining what each area aims to measure or predict.