Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/IEC 29110-4-3: Very Small Entities — Agile Extension Profile
Systems and Software Engineering — Agile Extension for VSE Profiles
Integrating Agile Practices with VSE Profiles
ISO/IEC 29110-4-3 provides the agile extension to the standard VSE profile framework, explicitly mapping agile practices and artifacts to the process outcomes defined in ISO/IEC 29110-5. This extension was developed in response to widespread adoption of agile methods in small software organizations and the need to reconcile agile flexibility with process maturity requirements. Rather than treating agile and process standards as contradictory approaches, this part of the standard shows how Scrum events, Kanban boards, extreme programming (XP) practices, and other agile techniques can satisfy the same process outcomes that traditional plan-driven methods address.
The agile extension does not create a separate process framework — it maps agile practices onto the existing VSE profile outcomes. This means a VSE using Scrum can demonstrate compliance with ISO/IEC 29110 Basic profile by mapping Sprint Planning to project planning outcomes, Sprint Review to validation outcomes, and the Definition of Done to quality assurance outcomes.
The extension covers three profile levels: Entry (Profile 1), Basic (Profile 2), and Intermediate (Profile 3). For each profile, the standard provides an agile mapping table that cross-references process outcomes with specific agile practices. At the Entry profile level, for instance, the software implementation outcome “Software components are developed and tested” maps to Test-Driven Development (TDD) and continuous integration practices. At the Basic profile level, configuration management outcomes align with automated build pipelines and version control workflows.
| VSE Process Outcome | Agile Practice Mapping | Agile Artifact | Verification Method |
|---|---|---|---|
| Project plan is established | Sprint Planning, Release Planning | Product Backlog, Sprint Backlog | Backlog refinement sessions, planning poker results |
| Requirements are defined | User Stories, Story Mapping | User Story repository, acceptance criteria | Story point estimation, Definition of Ready |
| Software components are implemented | TDD, Pair Programming, Continuous Integration | Test suite, CI pipeline configuration | Build status, test coverage reports, pair rotation logs |
| Configuration is managed | Branching strategy, CI/CD pipeline | Version control repository, deployment scripts | Pull request history, automated deployment records |
| Quality assurance is performed | Definition of Done, Sprint Review, Retrospective | DoD checklist, review meeting minutes, action items | Sprint burndown, velocity trend, defect escape rate |
| Verification and validation executed | Automated testing, Acceptance Testing, Demo | Test automation framework, demo recordings | Pass/fail rate, user acceptance sign-off |
Engineering insight: VSEs that adopt the agile extension report 40% faster time-to-market for new features compared to traditional plan-driven approaches within the same profile level. The key enabler is the reduction of documentation lead time — agile artifacts like acceptance criteria and automated test reports serve dual purposes as both engineering deliverables and compliance evidence.
Practical Implementation Strategies
For a VSE transitioning from ad-hoc development to a formalized profile with agile practices, the following implementation roadmap has proven effective in field studies. First, establish the Product Owner role (which maps to the customer/stakeholder responsibility in the standard) and define a simple Definition of Ready and Definition of Done — these two checklists alone cover nearly all quality assurance outcomes in the Basic profile. Second, implement a two-level planning structure: release planning (every 2-3 months) for strategic alignment with organizational goals, and sprint planning (every 1-2 weeks) for operational project management.
A common misconception: agile extension does not mean “no documentation.” The standard still requires evidence of process execution. The difference is that evidence takes agile-compatible forms — a well-maintained Product Backlog with acceptance criteria serves as both a requirements specification and a project tracking artifact. The danger is treating agile informality as a license to skip process outcomes entirely, which defeats the purpose of adopting the standard.
The extension also addresses the specific challenge of scaling agile practices within a VSE as it grows. A 5-person team might use simple Kanban with a shared board and daily stand-ups, while a 20-person VSE with multiple teams might need Scrum-of-Scrums, portfolio backlog management, and coordinated release planning. The profile structure naturally accommodates this scaling: the Entry profile supports single-team Kanban/Scrum, the Basic profile adds cross-team coordination, and the Intermediate profile introduces organizational-level process metrics and multi-team retrospectives.
Critical risk: agile extension adoption without adequate training in both agile methods AND the ISO/IEC 29110 framework frequently leads to “Scrum-but” scenarios where teams cherry-pick agile ceremonies without achieving the underlying process outcomes. Mandatory training on the mapping between agile practices and VSE profile outcomes is essential before beginning implementation. Organizations should budget at least 40 hours of training per key role.
Frequently Asked Questions
Q: Can a VSE claim compliance with both ISO/IEC 29110 Basic profile and Scrum at the same time?
A: Yes. The agile extension is designed precisely for this dual compliance. When a team runs Scrum ceremonies properly and maintains the agile artifacts listed in the mapping tables, they inherently satisfy the process outcomes of the Basic profile. No additional documentation is needed beyond what agile teams naturally produce.
A: Yes. The agile extension is designed precisely for this dual compliance. When a team runs Scrum ceremonies properly and maintains the agile artifacts listed in the mapping tables, they inherently satisfy the process outcomes of the Basic profile. No additional documentation is needed beyond what agile teams naturally produce.
Q: Does the agile extension support Kanban-only teams without fixed sprints?
A: Absolutely. The extension is methodology-neutral within the agile spectrum. Kanban teams map flow metrics (cycle time, WIP limits, cumulative flow diagrams) to measurement and process control outcomes. The key is demonstrating that process outcomes are achieved — the cadence (sprint-based vs. flow-based) is flexible.
A: Absolutely. The extension is methodology-neutral within the agile spectrum. Kanban teams map flow metrics (cycle time, WIP limits, cumulative flow diagrams) to measurement and process control outcomes. The key is demonstrating that process outcomes are achieved — the cadence (sprint-based vs. flow-based) is flexible.
Q: How does the agile extension handle distributed VSE teams?
A: The standard recognizes distributed teams as a common VSE reality. The agile extension maps distributed collaboration tools (e.g., digital Kanban boards, asynchronous stand-ups via Slack/Teams, remote pair programming via VS Code Live Share) to communication and coordination outcomes. The key requirement remains that these practices produce auditable evidence.
A: The standard recognizes distributed teams as a common VSE reality. The agile extension maps distributed collaboration tools (e.g., digital Kanban boards, asynchronous stand-ups via Slack/Teams, remote pair programming via VS Code Live Share) to communication and coordination outcomes. The key requirement remains that these practices produce auditable evidence.
Q: What is the recommended transition path from no process to Entry profile with agile extension?
A: Start with just three practices: (1) a visible task board (physical or digital), (2) daily 15-minute stand-up meetings, and (3) a simple Definition of Done checklist. Run these for 4-6 weeks until they become habit, then add sprint planning and review cycles. This gradual approach has the highest success rate (over 80%) for sustained adoption.
A: Start with just three practices: (1) a visible task board (physical or digital), (2) daily 15-minute stand-up meetings, and (3) a simple Definition of Done checklist. Run these for 4-6 weeks until they become habit, then add sprint planning and review cycles. This gradual approach has the highest success rate (over 80%) for sustained adoption.
