Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
PD ISO IEC TR 29110 โ Lifecycle Profiles for Very Small Entities (VSEs) Standard Series
Systems and software engineering โ Lifecycle profiles for Very Small Entities (VSEs) (PD ISO/IEC TR 29110)
๐ PD ISO IEC TR 29110 is the British Standards Institution’s Published Document (PD) adoption of ISO/IEC TR 29110, “Systems and software engineering โ Lifecycle profiles for Very Small Entities (VSEs)”. The overwhelming majority of software organisations worldwide are small teams of 1โ25 people, which can neither adopt heavyweight process models such as CMMI or ISO/IEC 12207 nor work without structured engineering processes to assure delivery quality. This series provides VSEs with a set of “scaled-to-size” process methods: it defines lifecycle profiles of varying maturity and the corresponding management/engineering guides and assessment methods. It is maintained by Technical Committee IST/15 (Software and systems engineering).
๐ก The core idea of 29110 is “process must match scale”: rather than making a small team squeeze into a large-enterprise process, it offers a set of processes that are already light enough, so that a 10-person team can “work to a standard” and be assessed.
1. Series Overview and the VSE Profile System ๐
Part 1 (Overview) explains the definition of a VSE, the relationship of the parts, the concept of a profile, and how a VSE selects a profile โ the gateway to the whole system. A profile is composed of the Generic Profile Group and extension profiles (e.g. system engineering and management extensions): the Entry, Basic, and Intermediate profiles add process-element complexity in turn, letting a VSE raise its maturity step by step. Part 3-1 (Assessment guide) specifies how to assess a VSE’s conformance to its process set in the spirit of ISO/IEC 15504; Part 3-4 (Autonomy-based improvement method) serves organisations lacking assessment resources, providing a self-service continuous-improvement path; the Part 5 series gives the management and engineering guides for the various profiles.
โ ๏ธ Profile selection must match the organisation’s current state: blindly targeting the “Intermediate” profile can burden a team beyond its capacity, and it is better to start from the “Entry” profile. The value of a profile is “just enough, evolve step by step”.
2. Series Composition and Key Points ๐ง
| Part | Subject | Key Content | Readability |
|---|---|---|---|
| PD ISO/IEC TR 29110-1 | Overview | Overview: VSE definition, series structure, and the profile system (supersedes the earlier edition) | Readable |
| PD ISO/IEC TR 29110-3-1 | Assessment guide | Assessment guide: conformance assessment of VSE processes | Readable |
| PD ISO/IEC TR 29110-3-4 | Autonomy-based improvement method | Autonomy-based improvement method | Readable |
| PD ISO/IEC TR 29110-5-1-1 | Management and engineering guide (Entry profile) | Management and engineering guide โ Generic profile group: Entry profile | Readable |
| PD ISO/IEC TR 29110-5-1-3 | Management and engineering guide (Intermediate profile) | Management and engineering guide โ Generic profile group: Intermediate profile (scanned, summarised from public-domain knowledge) | Scanned |
| PD ISO/IEC TR 29110-5-2-1 | Organisational management guidelines | Organisational management guidelines (scanned, summarised from public-domain knowledge) | Scanned |
| PD ISO/IEC TR 29110-5-6-1 | System engineering guide (extension) | System engineering related guide (scanned, summarised from public-domain knowledge) | Scanned |
| PD ISO/IEC TR 29110-5-6-2 | System engineering guide (extension) | System engineering related guide (scanned, summarised from public-domain knowledge) | Scanned |
๐จ Scanned-version note: Parts 5-1-3, 5-2-1, 5-6-1, and 5-6-2 are derived from scanned originals. The descriptions in this article are written from public-domain knowledge; the official BSI published version takes precedence for process elements and clauses.
3. Key Technical Requirements: Project Management and Software Implementation ๐ฅ
Part 5-1-1 (Entry profile management and engineering guide) defines the two basic processes a VSE should execute when implementing a software project:
- Project Management process: project start-up, planning, execution, monitoring, and closing, with emphasis on scope control, schedule/cost tracking, and communication;
- Software Implementation process: requirements analysis and definition, architectural and detailed design, coding, integration, verification, and delivery, with emphasis on configuration management and product delivery.
Each process is accompanied by Roles, Activities, Tasks, Work Products (inputs/outputs), and product descriptions, designed for “ease of use and tailorability”. Part 3-1 further specifies how to check an organisation’s conformance to its profile using the ISO/IEC 15504 process-assessment framework; Part 3-4 gives the improvement initiative to the organisation itself, through a self-assessment and improvement-plan cycle, gradually evolving towards higher profiles.
โ
For a small software team, the Entry profile already covers the essentials of project survival: traceable requirements, controlled versions, and recorded delivery. Starting habits from the Entry profile and then evolving to Basic and Intermediate via the Part 3-4 improvement method is the lowest-cost path to formalisation.
4. Engineering Practice ๐ ๏ธ
- ๐ Software start-ups: use the Entry profile to establish a minimal requirements-development-testing-delivery flow, avoiding rework and delivery chaos from “process-free improvisation”.
- ๐ง Small teams doing outsourced work: use the 29110 profile as a process baseline to demonstrate process capability to the buyer, supported by the Part 3-1 assessment to pass supplier audits.
- ๐ Organisational improvement: run self-assessment and improvement per Part 3-4, gradually transitioning from Entry to Basic/Intermediate, so process improvement grows in step with the team.
- ๐ Education and training: higher-education and vocational-training institutions use the 29110 profiles as the process template for software-project practical courses, linking to industry standards.
5. Frequently Asked Questions โ
โ Q: What is the relationship between TR 29110 and ISO/IEC 12207?
A: 29110 is the “lightweight implementation” of 12207 for VSEs: it is also based on lifecycle-process thinking, but tailors the process elements to what a small team can execute. Large organisations still use 12207; VSEs use the 29110 profiles.
A: 29110 is the “lightweight implementation” of 12207 for VSEs: it is also based on lifecycle-process thinking, but tailors the process elements to what a small team can execute. Large organisations still use 12207; VSEs use the 29110 profiles.
โ Q: How does a VSE choose its profile?
A: Generally choose “Entry โ Basic โ Intermediate” by team size and process maturity; you may also consider customer requirements and organisational goals, optionally using a 3-1 assessment first to establish the current state, then decide the target profile.
A: Generally choose “Entry โ Basic โ Intermediate” by team size and process maturity; you may also consider customer requirements and organisational goals, optionally using a 3-1 assessment first to establish the current state, then decide the target profile.
โ Q: How does the Part 3-4 “autonomy-based improvement” differ from a formal assessment?
A: A formal assessment (3-1) is performed by a qualified assessor per the framework and its result can be used for inter-organisational demonstration; autonomy-based improvement (3-4) is executed by the organisation itself, with lower cost and faster feedback, suitable for the starting phase โ the two can be used in sequence.
A: A formal assessment (3-1) is performed by a qualified assessor per the framework and its result can be used for inter-organisational demonstration; autonomy-based improvement (3-4) is executed by the organisation itself, with lower cost and faster feedback, suitable for the starting phase โ the two can be used in sequence.
๐ Q: Can the scanned parts be used?
A: The descriptions of the scanned parts in this article are written from public-domain knowledge and marked “scanned version”. For specific process elements (roles, tasks, products), follow the official BSI published version.
A: The descriptions of the scanned parts in this article are written from public-domain knowledge and marked “scanned version”. For specific process elements (roles, tasks, products), follow the official BSI published version.