Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/IEC 26555:2015 — Software Engineering — Product Family Engineering — Technical Management
Managing the technical aspects of software product family development, from planning to measurement and improvement
Overview of ISO/IEC 26555:2015
ISO/IEC 26555:2015 addresses technical management of software product family engineering — the management processes that ensure the technical success of the product family initiative.
While the other ProdFab standards focus on specific engineering disciplines (requirements, design, configuration, information), this standard deals with the cross-cutting management activities that coordinate and govern the entire product family engineering effort.
The standard covers technical planning, risk management, measurement and analysis, technical reviews, and process improvement — all adapted to the unique context of product families.
It recognizes that product family engineering requires a different management mindset than single-system development: managers must balance platform investment against product-specific needs, coordinate multiple product derivations, and continuously evaluate the economic viability of the product family approach.
ISO/IEC 26555 provides the ‘management overlay’ that connects the technical engineering standards (26551-26554, 26556) with organizational decision-making. Without effective technical management, even the best-engineered platform can fail due to poor planning or misaligned incentives.
Core Technical Management Processes
The standard defines several key management processes adapted for product family contexts:
Technical Planning for Product Families
Technical planning in product family engineering encompasses platform roadmap development, product derivation scheduling, and resource allocation across the family.
The standard emphasizes the need for a two-level planning approach: long-term platform evolution planning (typically 3-5 year horizons) and short-term product release planning (typically 3-12 month horizons).
| Management Process | Product Family Focus | Key Practices |
|---|---|---|
| Technical Planning | Platform roadmap, product derivation sequencing | Two-level planning, capability roadmaps |
| Risk Management | Platform risks, cross-product dependency risks | Variability risk analysis, portfolio risk assessment |
| Measurement & Analysis | Product family productivity, reuse rates | Staged measurement framework, product line metrics |
| Technical Reviews | Architecture reviews across the family | Platform-level reviews, product derivation reviews |
| Process Improvement | Product family process capability | CMMI for product lines, process tailoring |
| Organizational Management | Team structures for product families | Platform teams vs. product teams, coordination |
Risk Management in Product Families
ISO/IEC 26555 identifies several risk categories specific to product family engineering:
- Platform obsolescence risk: The platform may become outdated, making products uncompetitive.
- Variability explosion risk: Uncontrolled growth of variability leads to unsustainable complexity.
- Product-platform mismatch risk: A specific product’s needs may not align well with the platform.
- Organizational resistance risk: Teams accustomed to single-system development may resist platform adoption.
- Economic sustainability risk: The platform investment may not deliver expected returns.
The standard’s risk management framework requires regular reassessment. Product family risks change as the platform matures and as market conditions evolve. A risk that was acceptable at platform inception may become critical as the family grows.
Measurement and Analysis
A significant contribution of ISO/IEC 26555 is its measurement framework for product family engineering.
The standard defines a staged approach to measurement, progressing from basic project-level metrics to sophisticated business-value analysis.
Key measurement categories include:
- Reuse metrics: Reuse percentage, reuse cost avoidance, asset utilization rates.
- Productivity metrics: Time-to-market for new products, effort per product derivation, platform velocity.
- Quality metrics: Defect density in platform vs. products, defect propagation rates, variability-related defects.
- Economic metrics: Platform investment ROI, breakeven analysis, cost of delay for platform improvements.
- Strategic metrics: Product family coverage, market responsiveness, technology currency.
Organizations implementing the measurement framework from ISO/IEC 26555 report being able to quantify the ROI of their product family investment within 6-12 months. The staged approach allows organizations to start with simple metrics and mature their measurement capability over time.
Engineering Design Insights
Key management insights from the standard for engineering managers and technical leaders:
- Establish clear platform governance: The standard recommends a product family steering committee with representatives from all product lines. This body makes decisions about platform investments, prioritizes shared capabilities, and resolves conflicts between product needs.
- Invest in platform economics modeling: Understanding the costs and benefits of platform investments is critical. The standard provides guidance for developing ROI models that account for both tangible benefits (reduced development cost) and intangible benefits (faster time-to-market).
- Plan for platform evolution, not just initial development: Product families typically outlive their initial architectures. Technical management must include strategies for architecture evolution, technology refresh, and retirement of obsolete platform elements.
- Foster a product family culture: Technical management extends beyond processes and metrics to include organizational culture. The standard emphasizes the importance of rewarding reuse, collaboration across product teams, and long-term thinking.
The most common cause of product family failure is not technical — it’s managerial. Insufficient platform investment, short-term thinking that prioritizes product delivery over platform health, and organizational silos between product teams are the leading contributors to product family decline.
Frequently Asked Questions
Q: How does ISO/IEC 26555 relate to CMMI or other process maturity models?
ISO/IEC 26555 aligns with CMMI concepts but extends them for product family contexts. For example, CMMI’s measurement and analysis process area is specialized in 26555 to include product-family-specific metrics like reuse rates, platform productivity, and variability management effectiveness.
ISO/IEC 26555 aligns with CMMI concepts but extends them for product family contexts. For example, CMMI’s measurement and analysis process area is specialized in 26555 to include product-family-specific metrics like reuse rates, platform productivity, and variability management effectiveness.
Q: What is the recommended organizational structure for product family engineering?
The standard describes several organizational models: platform team + product teams (most common), domain engineering unit separate from application engineering, and matrix organizations. The choice depends on organizational size, product family scope, and strategic priorities.
The standard describes several organizational models: platform team + product teams (most common), domain engineering unit separate from application engineering, and matrix organizations. The choice depends on organizational size, product family scope, and strategic priorities.
Q: How do we handle the transition from single-system development to product family engineering?
ISO/IEC 26555 recommends a phased transition approach: (1) conduct a product family feasibility study, (2) establish the initial platform with 2-3 pilot products, (3) expand the family while refactoring the platform, and (4) institutionalize product family practices across the organization.
ISO/IEC 26555 recommends a phased transition approach: (1) conduct a product family feasibility study, (2) establish the initial platform with 2-3 pilot products, (3) expand the family while refactoring the platform, and (4) institutionalize product family practices across the organization.
Q: What metrics should we track in the first year of product family adoption?
The standard recommends starting with basic reuse metrics (percentage of code shared across products), productivity metrics (time to derive a new product), and quality metrics (defect density in reused vs. new code). As the program matures, add economic metrics like platform ROI and strategic metrics like market coverage.
The standard recommends starting with basic reuse metrics (percentage of code shared across products), productivity metrics (time to derive a new product), and quality metrics (defect density in reused vs. new code). As the program matures, add economic metrics like platform ROI and strategic metrics like market coverage.
