Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC TR 29110-2-2: Systems and Software Engineering — VSE — Part 2-2: Framework
ISO/IEC TR 29110-2-2 is a Technical Report that defines the framework for Very Small Entities (VSEs) in systems and software engineering. A VSE is defined as an enterprise, organization, department, or project having up to 25 people. The framework provides a structured approach for VSEs to develop and maintain systems and software products using tailored process profiles that are aligned with international standards while being appropriate for their size and resource constraints.
💡 Key Insight: The VSE framework recognizes that “one size fits all” process standards do not work for small organizations. By defining process profiles at different capability levels, VSEs can progressively adopt best practices without overwhelming their limited resources.
1. Framework Architecture and Process Profiles
The ISO/IEC TR 29110-2-2 framework is built around the concept of process profiles. A process profile is a set of processes selected from ISO/IEC 12207 (software lifecycle processes) and ISO/IEC 15288 (system lifecycle processes), tailored specifically for VSEs. The framework defines multiple profile groups, each targeting different types of VSEs based on their business context, product complexity, and risk profile.
The Technical Report defines four profile groups: Generic (for VSEs that do not develop critical software), Basic (for VSEs developing multiple products from the same organization), Intermediate (for VSEs requiring project management and product development integration), and Advanced (for VSEs with complex product portfolios or higher risk profiles). Each profile group specifies a minimum set of required processes and outcomes, with the flexibility to add optional processes as needed.
| Profile Group | Target VSE Type | Key Processes | Capability Level |
|---|---|---|---|
| Generic | Small projects, non-critical | Project Management, Software Implementation | Level 1 (Performed) |
| Basic | Single-project VSEs | PM + SI + Configuration Management | Level 1 (Performed) |
| Intermediate | Multi-project VSEs | PM + SI + CM + Quality Assurance | Level 2 (Managed) |
| Advanced | High-risk/complex products | Full lifecycle processes | Level 3 (Established) |
⚠️ Engineering Consideration: Selecting the right profile group is critical. An overly ambitious profile (e.g., Advanced for a 3-person team) leads to process overhead that negates the benefits of standardization. Conversely, a Generic profile for a safety-critical product may result in inadequate process rigor. Conduct a risk-based profile selection assessment before adoption.
2. Deployment and Implementation Guidance
ISO/IEC TR 29110-2-2 provides comprehensive deployment guidance for VSEs adopting the framework. The deployment process consists of four stages: initiation (understanding VSE needs and selecting appropriate profiles), planning (defining process implementation roadmap), execution (implementing processes and training personnel), and evaluation (assessing effectiveness and identifying improvements).
The deployment guidance emphasizes pragmatic considerations specific to VSEs. For example, it recognizes that personnel in VSEs typically wear multiple hats — the same individual may serve as project manager, developer, tester, and quality assurance officer. The framework provides role merging guidance that maps process responsibilities to available personnel while managing potential conflicts of interest (e.g., separating execution and verification roles).
Tool support for VSE process deployment is another key consideration. The Technical Report recommends lightweight, affordable tooling that can be implemented incrementally. Spreadsheets, shared document repositories, and basic issue tracking systems are often sufficient for VSEs at the Generic or Basic profile levels, while more capable tooling becomes necessary at Intermediate and Advanced levels.
| Deployment Stage | Key Activities | Typical Duration (VSE) |
|---|---|---|
| Initiation | Needs analysis, profile selection, gap assessment | 2-4 weeks |
| Planning | Roadmap definition, resource allocation, training plan | 2-3 weeks |
| Execution | Process implementation, tool deployment, training delivery | 8-16 weeks |
| Evaluation | Process assessment, feedback collection, improvement planning | 2-4 weeks |
✅ Best Practice: Implement processes incrementally rather than attempting a big-bang deployment. Start with the Basic profile group, stabilize it over two to three project cycles, and then consider advancing to the Intermediate profile. This evolutionary approach builds organizational competence and buy-in.
3. Engineering Design Insights and Practical Applications
ISO/IEC TR 29110-2-2 has found significant practical application in startups, small consulting firms, and in-house IT departments of small to medium-sized organizations. For startups developing software products, the framework provides a lightweight governance structure that satisfies investor due diligence requirements without impeding development velocity. The Basic profile group, requiring only six management processes and five implementation processes, can be adopted within weeks.
Another important application is in the context of subcontracting and supply chains. Large enterprises increasingly require their VSE suppliers to demonstrate process capability. ISO/IEC TR 29110-2-2 provides a practical alternative to full ISO 9001 or CMMI certification for VSEs, enabling them to qualify as trusted suppliers while maintaining operational flexibility. The framework’s explicit mapping to ISO/IEC 12207 ensures that processes implemented by VSEs are compatible with those of their larger customers.
From a process engineering perspective, the Technical Report demonstrates how to apply the concept of process tailoring systematically. Rather than requiring VSEs to interpret how to scale down large-process standards, the framework provides pre-tailored profiles that represent a consensus view of what is minimally necessary for effective systems and software engineering in a VSE context.
🚨 Critical Warning: Process adoption without organizational buy-in is counterproductive. VSE leaders must understand that the framework is a tool for improving outcomes, not a bureaucratic exercise. Framing process implementation in terms of concrete benefits — fewer defects, shorter cycle times, reduced rework — is essential for sustained adoption. Avoid creating process documentation that is disconnected from daily work.
Frequently Asked Questions
Q1: What is the difference between ISO/IEC 29110 and ISO/IEC 12207?
ISO/IEC 12207 is the international standard for software lifecycle processes, designed for organizations of any size. ISO/IEC 29110 is a family of standards and technical reports specifically for VSEs (up to 25 people). The 29110 framework tailors the processes from 12207 into pre-packaged profiles that are immediately usable by VSEs without requiring extensive interpretation or customization.
Q2: Can a VSE be certified against ISO/IEC 29110?
ISO/IEC 29110 does not have a formal certification scheme like ISO 9001. However, organizations can undergo third-party assessments to demonstrate conformity with the framework. Some national accreditation bodies offer recognition programs for VSEs that successfully implement ISO/IEC 29110 profiles.
Q3: How does the VSE framework handle product development across multiple teams?
For VSEs with multiple teams, the Intermediate and Advanced profile groups include coordination and integration processes. The framework recommends establishing a lightweight program management function that handles cross-team dependencies, shared resource allocation, and integrated release planning.
Q4: Is the framework applicable to non-software products?
Yes. ISO/IEC TR 29110-2-2 addresses both systems engineering and software engineering. The framework references ISO/IEC 15288 (system lifecycle processes) alongside ISO/IEC 12207, making it applicable to VSEs developing hardware-software systems, embedded systems, or purely hardware products with embedded firmware.
