Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/IEC 29110-5-1-2: Very Small Entities — Entry Profile Guide
Systems and Software Engineering — VSE Entry Profile: Management and Engineering Guide
The Entry Profile — A Minimal Viable Process Framework
ISO/IEC 29110-5-1-2 defines the Entry profile (Profile 1), which is the lightest-weight process framework in the ISO/IEC 29110 series. It is specifically designed for very small entities that are either starting their process improvement journey or operating in highly dynamic environments where heavy process overhead would be counterproductive. The Entry profile requires only two process areas — Project Management (PM) and Software Implementation (SI) — with a total of just 5 essential work products across both areas. This makes it accessible to teams as small as 2-3 people who need just enough process to ensure repeatability without drowning in documentation.
Think of the Entry profile as the “minimum viable process” for a software development VSE. It captures the absolute essential activities that distinguish a professional engineering effort from ad-hoc coding: (1) a basic project plan, (2) a requirements list, (3) a software component description, (4) a test record, and (5) a product delivery record. Everything else is optional at this level.
The philosophy behind the Entry profile is pragmatic minimalism. Rather than asking a 3-person startup to produce comprehensive process documentation, the standard asks: “What is the smallest set of activities that, if performed consistently, would significantly improve project outcomes?” The answer is captured in five streamlined outcomes for Project Management (plan the project, execute the plan, monitor progress, handle changes, close the project) and three outcomes for Software Implementation (develop software components, test them, and deliver the product).
| Process Area | Work Product | Purpose | Typical Size (pages) |
|---|---|---|---|
| Project Management | Project Plan | Define scope, tasks, schedule, and responsibilities | 2-3 |
| Project Management | Project Status Record | Track progress, issues, and decisions | 1-2 (updated weekly) |
| Project Management | Requirements List | Capture and track customer requirements | 1-3 |
| Software Implementation | Software Components Description | Document what was built and key design decisions | 2-4 |
| Software Implementation | Test Record and Delivery Record | Record test results and formal delivery acceptance | 1-2 each |
Engineering insight: organizations adopting the Entry profile consistently report that the single most valuable artifact is the Requirements List. Before adopting the profile, most VSEs operate with verbal-only requirements, leading to scope creep and misunderstood features. The simple act of writing down and maintaining a numbered requirements list reduces feature-related rework by an average of 45% in the first three months of adoption.
Transitioning from Entry to Higher Profiles
The Entry profile is designed as a starting point, not a destination. ISO/IEC 29110-5-1-2 includes guidance for transitioning from Entry (Profile 1) to Basic (Profile 2) when the organization is ready. The transition typically happens when: (a) the team grows beyond 5 people, (b) the organization starts managing multiple simultaneous projects, (c) customers require formal quality assurance evidence, or (d) the team finds that the Entry profile’s lightweight controls are insufficient to prevent recurring issues.
Important transition consideration: do not rush from Entry to Basic until the Entry-level practices are truly habitual. Field data shows that VSEs that operate at Entry profile for 6-12 months before upgrading have a 70% success rate at Basic profile adoption, while those that attempt the upgrade within 3 months have only a 30% success rate. The Entry-level habits — particularly regular progress tracking and requirements change management — must become automatic before adding more process areas.
The standard provides a detailed gap analysis table showing what new work products and outcomes are added at each transition. Moving from Entry to Basic adds: Configuration Management (3 new outcomes, 2 new work products) and Quality Assurance (3 new outcomes, 2 new work products), plus expanded PM outcomes (from 5 to 6) and expanded SI outcomes (from 3 to 8). The specific additions are clearly mapped so a VSE can assess its readiness and plan the transition incrementally.
Critical engineering risk: the Entry profile intentionally excludes Configuration Management as a separate process area. For teams using only Entry profile, it is essential to implement at least a manual versioning scheme (e.g., file naming conventions with dates and version numbers) to avoid the common failure mode of “which file is the latest?” This is the single greatest risk of staying at Entry profile for extended periods without supplementing with basic CM practices.
Frequently Asked Questions
Q: Is the Entry profile suitable for non-software VSEs (e.g., hardware or service companies)?
A: While ISO/IEC 29110-5-1-2 is written with software terminology, its principles are domain-neutral. Hardware VSEs can adapt the Software Components Description to “Product Components Description” and map test outcomes to manufacturing verification. Service organizations can map software implementation activities to service delivery activities. The management framework (plan, track, handle changes, close) is universally applicable.
A: While ISO/IEC 29110-5-1-2 is written with software terminology, its principles are domain-neutral. Hardware VSEs can adapt the Software Components Description to “Product Components Description” and map test outcomes to manufacturing verification. Service organizations can map software implementation activities to service delivery activities. The management framework (plan, track, handle changes, close) is universally applicable.
Q: Can a VSE claim ISO/IEC 29110 compliance at Entry profile?
A: Yes, the Entry profile is a certifiable profile in the ISO/IEC 29110 framework. However, most certification bodies recommend transitioning to at least Basic profile for formal certification because Entry profile omits configuration management and quality assurance, which are typically expected in a certifiable process. Some industry sectors (e.g., medical devices, automotive) may not accept Entry profile compliance for regulatory purposes.
A: Yes, the Entry profile is a certifiable profile in the ISO/IEC 29110 framework. However, most certification bodies recommend transitioning to at least Basic profile for formal certification because Entry profile omits configuration management and quality assurance, which are typically expected in a certifiable process. Some industry sectors (e.g., medical devices, automotive) may not accept Entry profile compliance for regulatory purposes.
Q: How much time does it take to implement the Entry profile?
A: Most VSEs can implement the Entry profile in 2-4 weeks. The implementation involves: creating the 5 work product templates (1 week), training the team on using them (2-3 days), and running a pilot project (1-2 weeks). The total investment is typically 40-80 person-hours for a 5-person team.
A: Most VSEs can implement the Entry profile in 2-4 weeks. The implementation involves: creating the 5 work product templates (1 week), training the team on using them (2-3 days), and running a pilot project (1-2 weeks). The total investment is typically 40-80 person-hours for a 5-person team.
Q: Does the Entry profile require any specific tools?
A: No. The Entry profile is tool-agnostic. The work products can be maintained in any medium: paper notebooks, spreadsheets, word processors, wikis, or project management tools like Trello, Jira, or Notion. The standard provides templates that can be used as-is. The key requirement is that the information exists and is kept current — not the specific tool used to maintain it.
A: No. The Entry profile is tool-agnostic. The work products can be maintained in any medium: paper notebooks, spreadsheets, word processors, wikis, or project management tools like Trello, Jira, or Notion. The standard provides templates that can be used as-is. The key requirement is that the information exists and is kept current — not the specific tool used to maintain it.
