Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Implementing CAN/CSA ISO/IEC TR 29110-5-6-2-18: Management and Engineering Guide for Very Small Entities
Guidelines for organizational management and engineering processes tailored to VSEs adopting the Generic Profile Group
Scope and Introduction
CAN/CSA ISO/IEC TR 29110-5-6-2-18 is the Canadian adoption of the International Standardization Organization / International Electrotechnical Commission Technical Report ISO/IEC TR 29110-5-6-2:2018, titled “Systems and software engineering – Lifecycle profiles for Very Small Entities (VSEs) – Part 5-6-2: Management and engineering guide: Generic profile group: Organizational management and engineering.” This technical report is part of the well-known ISO/IEC 29110 series, which aims to improve the process capability and business outcomes of very small entities (VSEs)—typically organizations with up to 25 people.
The guide specifically addresses the Generic profile group, which suits VSEs that do not develop critical software/systems but still require a disciplined approach to management and engineering. While the earlier 29110 guides focused on system and software implementation profiles, this TR targets the organizational level, covering processes that enable a VSE to manage projects, perform engineering activities, and continuously improve its processes.
Scope Note: This guide is applicable to any VSE developing either software or systems (including hardware and human interfaces). It does not prescribe a specific lifecycle model but provides process outcomes that can be mapped to agile, incremental, or waterfall approaches.
Technical Requirements and Process Structure
CAN/CSA ISO/IEC TR 29110-5-6-2-18 defines a set of processes, each with defined purposes, outcomes, and a list of work products. The overall framework is built around two primary process domains:
- Organizational Management Process (OM) – Covers planning, monitoring, control, and improvement at the enterprise level.
- Engineering Process (ENG) – Addresses the technical activities of elicitation, analysis, design, implementation, integration, and verification/validation.
The table below summarizes the core processes and their key objectives as prescribed in the Technical Report.
| Process | Purpose | Key Work Products |
|---|---|---|
| Organizational Management (OM) | Establish organizational policies, allocate resources, monitor performance, and manage improvement initiatives. | Business plan, process asset library, training records, performance metrics |
| Project Planning (within OM) | Define project scope, schedule, cost estimates, and risk management plan. | Project plan, work breakdown structure, risk register |
| Project Assessment and Control (within OM) | Track project progress, manage changes, and ensure corrective actions. | Progress status reports, change requests, issue log |
| Engineering (ENG) | Perform all technical life cycle stages from requirements to acceptance. | Specifications, design models, source code, test reports, user documentation |
The Engineering Process (ENG) in this TR extends the earlier Implementation profile by covering the full lifecycle, including operation and maintenance, and aligns with the ISO/IEC 12207 and ISO/IEC 15288 process models. Each process outcome must be achievable to claim conformance to the Generic Profile Group.
Key Distinction: Unlike the Basic Profile (Part 5-1-1 and Part 5-1-2), the Generic Profile Group defined in TR 29110-5-6-2-18 expects the VSE to manage not only a single project but also organizational resources and improvements. It is suitable for VSEs that handle multiple projects or require a higher degree of process maturity.
Implementation Highlights
Adopting this Technical Report requires careful tailoring to the VSE’s context. Below are essential implementation considerations based on the guide:
1. Tailoring and Scalability
The TR explicitly acknowledges that not all outcomes may be applicable to every product or service. VSEs are allowed to omit or combine outcomes while retaining the essential discipline. The organization must document their tailoring decisions and rationale.
2. Tooling and Documentation
Given the limited resources of VSEs, the guide encourages minimalistic yet effective documentation. A single integrated tool (e.g., a spreadsheet or lightweight project management platform) can cover multiple work products listed in the table above.
3. Organizational Enablers
A successful implementation relies on establishing a process asset library (PAL). The PAL can be as simple as a shared folder containing templates, checklists, and examples. The TR provides guidelines for creating and maintaining such assets.
4. Focus on Continuous Improvement
The Organizational Management process includes a Process Improvement outcome. VSEs are expected to collect metrics, conduct reviews, and plan corrective actions. This aligns with CMMI and ISO 9001 principles but is tailored for small teams.
Tip: Start with the Engineering Process (ENG) if your VSE already has project management practices in place. The Organizational Management process can be introduced in incremental phases to avoid overwhelming the team.
Compliance and Certification Notes
It is important to note that CAN/CSA ISO/IEC TR 29110-5-6-2-18 is a Technical Report (TR), not a normative International Standard. Therefore, it does not offer formal certification. However, many organizations use it as a basis for internal process improvement and for demonstrating conformity to ISO/IEC 29110-2 (the framework and taxonomy) requirements for the Generic Profile Group.
- Self-assessment: The TR provides an assessment model (Annex A) that maps process outcomes to capability levels. VSEs can self-assess using the provided indicators.
- Third-party appraisal: Some accreditation bodies recognize the 29110 series for auditing purposes, especially for VSEs that supply larger organizations. Conformance to this TR can be a stepping stone to ISO 9001 certification.
- Canadian Context: As a CAN/CSA standard, it supersedes the earlier adoption of ISO/IEC TR 29110-5-6-2:2018. Canadian VSEs may use this document to meet procurement requirements from government or large enterprises that mandate ISO/IEC 29110.
Important: This TR does not replace the mandatory requirements of ISO/IEC 29110-4-1 (the generic profile group specification). VSEs aiming for formal recognition must use Part 4-1 in conjunction with this guide.
Frequently Asked Questions
Q: What is the difference between the Basic Profile (Part 5-1-1) and the Generic Profile Group covered by this TR?
A: The Basic Profile targets a single project with limited organizational management requirements. The Generic Profile Group (Part 5-6-2) adds organizational management and improvement processes, making it suitable for VSEs that run multiple projects or need to manage their enterprise capabilities. It also covers the full lifecycle beyond software implementation, including operation and maintenance.
A: The Basic Profile targets a single project with limited organizational management requirements. The Generic Profile Group (Part 5-6-2) adds organizational management and improvement processes, making it suitable for VSEs that run multiple projects or need to manage their enterprise capabilities. It also covers the full lifecycle beyond software implementation, including operation and maintenance.
Q: Can a VSE claim certification to CAN/CSA ISO/IEC TR 29110-5-6-2-18?
A: No, because it is a Technical Report (TR) and not a normative standard. However, a VSE can demonstrate alignment with the ISO/IEC 29110 framework using this TR as a guide, and seek third-party assessment against the normative profile specification (ISO/IEC 29110-4-1) for the Generic Profile Group.
A: No, because it is a Technical Report (TR) and not a normative standard. However, a VSE can demonstrate alignment with the ISO/IEC 29110 framework using this TR as a guide, and seek third-party assessment against the normative profile specification (ISO/IEC 29110-4-1) for the Generic Profile Group.
Q: How does this TR support agile development in VSEs?
A: The TR does not prescribe a lifecycle model. Its process outcomes are compatible with agile practices. For example, the Engineering process outcomes for iterative development align with Scrum or Kanban. The Organizational Management process can be adapted to lightweight portfolio management. Many VSEs find the TR a natural complement to agile frameworks.
A: The TR does not prescribe a lifecycle model. Its process outcomes are compatible with agile practices. For example, the Engineering process outcomes for iterative development align with Scrum or Kanban. The Organizational Management process can be adapted to lightweight portfolio management. Many VSEs find the TR a natural complement to agile frameworks.
Q: What are the recommended next steps for a VSE starting adoption?
A: Begin by reading the guide entirely, then perform a gap analysis of current practices against the process outcomes in Annex A. Prioritize the Engineering Process (ENG) first, then incrementally add Organizational Management (OM) outcomes. Use the work product descriptions to create simple templates, and plan for a pilot project. Seek feedback from staff and iterate. For public recognition, consider a formal assessment against ISO/IEC 29110-4-1 once the processes are stable.
A: Begin by reading the guide entirely, then perform a gap analysis of current practices against the process outcomes in Annex A. Prioritize the Engineering Process (ENG) first, then incrementally add Organizational Management (OM) outcomes. Use the work product descriptions to create simple templates, and plan for a pilot project. Seek feedback from staff and iterate. For public recognition, consider a formal assessment against ISO/IEC 29110-4-1 once the processes are stable.
Published 2026 – This article is based on the CAN/CSA ISO/IEC TR 29110-5-6-2-18 Technical Report. All standard references remain the property of their respective standards organizations.