Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
ISO/IEC TR 29110-5-6-3: Very Small Entities — Service Deployment Package
Service management and delivery processes tailored for very small entities
ISO/IEC TR 29110-5-6-3 extends the VSE lifecycle framework to services. While earlier parts of 29110 focus on developing products (software, systems), this Deployment Package addresses the ongoing delivery, support, and improvement of services — an area where VSEs face unique challenges due to limited staffing for 24/7 coverage.
Service management is often an afterthought for VSEs. A team that successfully builds a product may struggle to support it, leading to customer dissatisfaction and churn. This Deployment Package provides a structured yet lightweight approach to service management that fits small organizations.
Service Management Processes for VSEs
The Service Deployment Package defines four core processes adapted from ITIL and ISO 20000, scaled to match VSE capabilities and resources.
| Service Process | Description | Work Products | VSE Adaptation |
|---|---|---|---|
| Service Request Management | Handle customer requests for information, changes, or new features | Service Request Log, Request Fulfillment Report | Single shared mailbox or ticketing system; triage by developer-on-duty |
| Incident Management | Restore normal service operation after disruption as quickly as possible | Incident Record, Known Error Database, Major Incident Report | Prioritized by impact; SLA tiers (critical/high/normal/low); on-call rotation |
| Service Level Management | Negotiate, document, and monitor service level agreements (SLAs) | Service Level Agreement (SLA), Service Report, SLA Review Minutes | Single SLA document covering all customers; reviewed quarterly |
| Continual Service Improvement | Identify and implement improvements to service quality and efficiency | Improvement Register, Customer Satisfaction Survey, Service Improvement Plan | Lightweight — one improvement item per quarter with measurable targets |
VSEs should resist the temptation to over-engineer their service management system. A full ITIL implementation with dozens of processes and roles will overwhelm a small team. The Deployment Package deliberately limits to four processes — adding more only when the team grows beyond 15 people.
Engineering Insights: Service Design for Small Teams
The Deployment Package introduces the concept of service maintainability by design. When a VSE builds a product, the architecture decisions directly impact the cost and quality of service delivery. Key architectural attributes that improve serviceability include: comprehensive logging (structured, searchable), health check endpoints, graceful degradation under load, and feature flags for remote configuration.
A particularly valuable recommendation is the runbook-first approach to service deployment. Before a service goes live, the team writes the runbook — a step-by-step document covering startup, shutdown, health verification, backup, restore, and common failure scenarios. The act of writing the runbook often reveals gaps in monitoring, error handling, or configuration management. The Runbook becomes a living document updated with every major release and every incident post-mortem.
On-Call Management for Very Small Entities
24/7 on-call coverage is one of the greatest challenges for a VSE. With only 3-5 engineers, a traditional weekly rotation creates unsustainable sleep disruption. The Deployment Package recommends several mitigations: follow-the-sun handoff if the team is distributed across time zones, automated incident escalation with clear severity thresholds, and a deliberate policy of reducing alert noise by tuning monitoring thresholds continuously. The goal is to ensure that every page is actionable and urgent.
A 6-person SaaS team adopted the Deployment Package’s incident management process with a simplified severity matrix. Critical incidents (system down, data loss) trigger immediate page to the entire team. High incidents (feature impaired, performance degradation) page the on-call engineer with a 30-minute response SLA. Normal incidents are handled during business hours. This stratification reduced after-hours pages by 70% while maintaining customer satisfaction above 95%.
FAQs
Q: How does 5-6-3 relate to ISO 20000?
A: ISO 20000 is the international standard for service management. ISO/IEC TR 29110-5-6-3 is a lightweight subset of ISO 20000 processes tailored for VSEs. It can serve as a stepping stone toward ISO 20000 certification.
A: ISO 20000 is the international standard for service management. ISO/IEC TR 29110-5-6-3 is a lightweight subset of ISO 20000 processes tailored for VSEs. It can serve as a stepping stone toward ISO 20000 certification.
Q: Can a product-only VSE use 5-6-3?
A: Yes. Even a VSE that builds products rather than providing managed services still needs to handle customer support, bug fixes, and version upgrades. These activities fall under the Service Request and Incident Management processes.
A: Yes. Even a VSE that builds products rather than providing managed services still needs to handle customer support, bug fixes, and version upgrades. These activities fall under the Service Request and Incident Management processes.
Q: Is a ticketing system mandatory?
A: Not necessarily. A shared email inbox with proper labeling can work for teams with very low service request volumes (fewer than 10 per week). As volume grows, a lightweight ticketing system (e.g., Trello, Jira Service Management, or a simple shared spreadsheet) becomes necessary.
A: Not necessarily. A shared email inbox with proper labeling can work for teams with very low service request volumes (fewer than 10 per week). As volume grows, a lightweight ticketing system (e.g., Trello, Jira Service Management, or a simple shared spreadsheet) becomes necessary.
Q: How do I measure service quality in a VSE context?
A: The Deployment Package recommends three key performance indicators: First Response Time (FRT), Mean Time to Resolve (MTTR), and Customer Satisfaction Score (CSAT). These three metrics provide a balanced view of service quality without excessive measurement overhead.
A: The Deployment Package recommends three key performance indicators: First Response Time (FRT), Mean Time to Resolve (MTTR), and Customer Satisfaction Score (CSAT). These three metrics provide a balanced view of service quality without excessive measurement overhead.
