Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
CAN CSA ISO IEC TR 29110-5-1-2-18: A Technical Guide for Very Small Entities in Software and Systems Engineering
Understanding the Management and Engineering Guide for the Basic Profile (Generic Profile Group)
This technical article provides a comprehensive overview of the CAN CSA ISO IEC TR 29110-5-1-2-18, the Canadian adoption of the ISO/IEC TR 29110-5-1-2:2018 technical report. It focuses on the Management and Engineering Guide for the Basic Profile within the Generic Profile Group. Designed specifically for Very Small Entities (VSEs) – organizations with up to 25 people – this guide offers a tailored set of project management and software implementation processes that enable VSEs to achieve international recognition for their software engineering capabilities without the overhead of larger standards.
Scope and Target Audience
The standard applies to VSEs undertaking software development projects. It defines a subset of ISO/IEC 12207 (Software Life Cycle Processes) activities and tasks, scaled down for VSEs. The Basic Profile is for VSEs that are not necessarily using any formal process but need a minimal yet effective approach. The standard covers two primary processes:
- Project Management (PM) – Planning, execution, assessment, and closure.
- Software Implementation (SI) – Requirements, design, construction, integration, and delivery.
The target audience includes developers, project managers, quality assurance personnel in small software companies, as well as consultants and educators training VSEs.
Technical Requirements – Processes and Activities
The core of the guide lies in the definition of the PM and SI processes. Each process consists of key activities with specific tasks and work products. The table below summarizes the main activities and their associated outcomes.
| Process | Activity | Description | Key Work Products |
|---|---|---|---|
| Project Management (PM) | Project Planning | Define scope, schedule, cost, risks | Project Plan |
| Project Plan Execution | Implement the plan and monitor progress | Progress Reports, Change Requests | |
| Project Assessment & Control | Evaluate performance and take corrective actions | Meeting Records, Corrective Actions | |
| Project Closure | Formalize acceptance and archive | Acceptance Record, Project Repository | |
| Software Implementation (SI) | Initiation | Prepare the environment and review plan | Project Plan Review |
| Requirements Analysis | Elicit and specify stakeholder requirements | Software Requirements Specification | |
| Architecture & Detailed Design | Define software architecture and components | Architecture/Design Document | |
| Software Construction | Code and unit test | Code, Unit Test Records | |
| Integration & Tests | Integrate components and perform verification | Test Report, Integrated Software | |
| Product Delivery | Deliver final product and obtain acceptance | Software Product, User Guide |
Implementation Highlights
Successfully implementing the Basic Profile requires commitment to documented processes even in small teams. Below are some practical insights:
Tip: Customize work products to match your project scale. The guide explicitly allows merging roles; a single person can serve as both project manager and developer.
Warning: Do not neglect the planning and closure activities. Even minimal documentation of lessons learned can drive continuous improvement.
Success Strategy: Use the self-assessment checklists provided in the annexes of the standard to evaluate your implementation before seeking external validation.
Common Pitfall: Underestimating configuration management. Establish a simple version control system early in the project to avoid integration issues.
Compliance Notes
Compliance with CAN CSA ISO IEC TR 29110-5-1-2-18 is usually a self-declaration. VSEs can claim conformity to the Basic Profile if they have implemented the processes as described, incorporating the defined activities and producing the required work products. However, for formal recognition, organizations may seek third-party assessments from accredited certification bodies that specialize in small entity process assessments.
It is crucial to note that this technical report is not intended to replace comprehensive standards like ISO/IEC 12207 or ISO 9001. Instead, it serves as a stepping stone for VSEs to gradually adopt more rigorous process models. In Canada, the CSA adoption ensures alignment with domestic industry expectations, and VSEs using this standard can later transition to ISO/IEC 29110 full certification or use it as part of a quality management system.
For ongoing compliance, VSEs should maintain records of all activities and work products, perform periodic internal reviews, and adapt the processes as the organization grows.
Frequently Asked Questions
Q: What is the difference between the Basic Profile and the Entry Profile in the 29110 series?
A: The Entry Profile is tailored for VSEs with little or no formal process experience, providing a minimal set of practices. The Basic Profile adds more structure and depth in both project management and software implementation, making it suitable for organizations that have some maturity but still need a lightweight approach.
A: The Entry Profile is tailored for VSEs with little or no formal process experience, providing a minimal set of practices. The Basic Profile adds more structure and depth in both project management and software implementation, making it suitable for organizations that have some maturity but still need a lightweight approach.
Q: Can a VSE with fewer than 10 people effectively implement this standard?
A: Absolutely. The standard is explicitly designed for VSEs with up to 25 people, and its flexibility allows micro-enterprises to adopt only the necessary outcomes while scaling other elements as appropriate. The guidance suggests that in very small teams, one person may perform multiple roles.
A: Absolutely. The standard is explicitly designed for VSEs with up to 25 people, and its flexibility allows micro-enterprises to adopt only the necessary outcomes while scaling other elements as appropriate. The guidance suggests that in very small teams, one person may perform multiple roles.
Q: How does the Canadian version differ from the original ISO/IEC TR?
A: The CAN/CSA adoption is technically equivalent to the international version. It includes a Canadian foreword and possibly minor editorial modifications to reflect national preferences, but the process outcomes, activities, and work products remain identical.
A: The CAN/CSA adoption is technically equivalent to the international version. It includes a Canadian foreword and possibly minor editorial modifications to reflect national preferences, but the process outcomes, activities, and work products remain identical.
Q: What is the relationship between this standard and agile methods?
A: The standard is methodology-neutral. VSEs can implement its outcomes using any development life cycle, including iterative and agile approaches. As long as the specified outcomes are achieved, practices such as Scrum, Kanban, or XP are fully compatible.
A: The standard is methodology-neutral. VSEs can implement its outcomes using any development life cycle, including iterative and agile approaches. As long as the specified outcomes are achieved, practices such as Scrum, Kanban, or XP are fully compatible.
© 2026. This article is based on CAN CSA ISO IEC TR 29110-5-1-2-18 and the ISO/IEC TR 29110-5-1-2:2018 technical report.