Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/IEC TR 29110-5-1-4: Very Small Entities — Entry Profile
A practical deployment package for very small entities adopting Entry Profile lifecycle processes
ISO/IEC TR 29110-5-1-4 is a Technical Report that provides a Deployment Package (DP) for the Entry Profile of the VSE (Very Small Entity) lifecycle standard. It targets organizations with up to 25 people that need a pragmatic, low-ceremony approach to software engineering without sacrificing fundamental good practices.
This Deployment Package bridges the gap between “no process” and “too much process.” It gives VSEs a tailored entry point into ISO/IEC 29110 that respects their limited resources and flat organizational structures.
Core Structure of the Entry Profile Deployment Package
The Deployment Package is organized around two primary processes: Project Management (PM) and Software Implementation (SI). Each process is broken into roles, activities, tasks, and work products that are lightweight yet auditable.
| Process | Key Roles | Core Activities | Essential Work Products |
|---|---|---|---|
| Project Management (PM) | Project Manager, Customer | Project Planning, Project Plan Execution, Project Assessment & Control, Project Closure | Project Plan, Progress Record, Change Request Log, Acceptance Record |
| Software Implementation (SI) | Analyst, Designer, Implementer | Software Requirements Analysis, Software Architectural & Detailed Design, Software Construction, Software Integration & Tests, Product Delivery | Software Requirements Specification, Architecture Document, Test Record, User Documentation, Software Product |
VSEs often skip requirements documentation because they believe “everyone knows what to build.” The Entry Profile explicitly requires a Software Requirements Specification — even if it is a single-page document — to prevent scope creep and misaligned expectations.
Engineering Design Insights for VSE Practitioners
The Entry Profile recognizes that a 5-person team cannot operate like a 500-person organization. Instead of mandating heavyweight deliverables, it defines outcome-based acceptance criteria. For example, the “Software Delivery” task is complete when the customer confirms the software meets the agreed requirements — formal sign-off is encouraged but a simple email confirmation suffices in low-risk contexts.
A critical design insight is the iterative feedback loop embedded in the PM process. The Project Plan is expected to be updated at least weekly, and the Progress Record tracks actual vs. planned effort in hours, not in abstract percentage points. This makes the Entry Profile compatible with Agile-inspired practices such as sprint planning and daily stand-ups.
Tailoring the Deployment Package for Your Context
The Deployment Package explicitly permits tailoring. A VSE developing internal IT tools may skip the formal Architecture Document, while a VSE building safety-related software for medical devices would retain all work products and add traceability matrices. The key is documenting the tailoring decisions in the Project Plan.
One of the most practical elements in the Deployment Package is the set of template documents provided as annexes. These include a Project Plan template, a Software Requirements Specification template, and a Test Record template — each is typically 2-4 pages long, directly usable in a word processor or spreadsheet.
FAQs
Q: Is ISO/IEC 29110-5-1-4 certifiable?
A: No, this is a Technical Report (TR), not an International Standard (IS). It provides guidance and deployment packages but is not intended for certification. The certifiable requirements are in ISO/IEC 29110-4-1.
A: No, this is a Technical Report (TR), not an International Standard (IS). It provides guidance and deployment packages but is not intended for certification. The certifiable requirements are in ISO/IEC 29110-4-1.
Q: Can a 2-person startup use this Entry Profile?
A: Yes, absolutely. The Entry Profile was designed for organizations with as few as 1 person. The key is to scale the work products proportionally — a one-person team may combine the Project Manager and Implementer roles.
A: Yes, absolutely. The Entry Profile was designed for organizations with as few as 1 person. The key is to scale the work products proportionally — a one-person team may combine the Project Manager and Implementer roles.
Q: How does this relate to ISO 9001?
A: ISO/IEC 29110-5-1-4 can serve as a stepping stone toward ISO 9001 certification. The process documentation and records required by the Entry Profile align with the “documented information” requirements of ISO 9001:2015.
A: ISO/IEC 29110-5-1-4 can serve as a stepping stone toward ISO 9001 certification. The process documentation and records required by the Entry Profile align with the “documented information” requirements of ISO 9001:2015.
Q: Is the Deployment Package compatible with Scrum?
A: Yes. The PM process maps naturally to the Scrum Master role, and the SI process aligns with the Development Team’s sprint activities. The Project Plan can be replaced by a Product Backlog and Sprint Backlog with appropriate tailoring documented.
A: Yes. The PM process maps naturally to the Scrum Master role, and the SI process aligns with the Development Team’s sprint activities. The Project Plan can be replaced by a Product Backlog and Sprint Backlog with appropriate tailoring documented.
