Progressive practices, technologies and the management mesh
Domain 4: Progressive practices, technologies and the management mesh
This domain tests your ability to choose and combine progressive practices and innovative technologies through the management mesh. Expect questions on Agile, DevOps, Lean, SIAM, cloud, automation, analytics and AI, and on why the mesh is context-dependent.
Core rules and concepts
- Progressive practices are modern ways of working that improve speed, flow, customer focus and integration. Examples include Agile, DevOps, Lean, SIAM, continuous delivery, customer experience and value stream mapping.
- Innovative technologies include cloud computing, automation, artificial intelligence, analytics, mobile and social platforms. They enable new service options but do not define the service outcome by themselves.
- The management mesh combines practices, technologies, people, partners and culture. It is deliberately flexible: the organization selects and blends elements to fit the service and its context.
- Selection should be driven by value and outcomes, not fashion. A small internal service may need only light practices; a high-risk digital service may need stronger controls.
- Progressive practices do not replace service management; they extend the organization's capability to respond and improve.
- Culture and people are part of the mesh. DevOps without collaboration or cloud without skills will not deliver the intended value.
Worked example
A retailer wants a same-day delivery promise. The mesh selects Agile for cross-functional planning, DevOps for frequent releases, cloud for elastic capacity, and analytics for delivery prediction. Governance sets the risk appetite for failed deliveries; service management defines the support and escalation path. Reasoning: no single practice or tool delivers the promise. The mesh combines practices, technology and people around the outcome. If the retailer copied a full DevOps toolchain without changing team culture or delivery partnerships, the mesh would be unbalanced and value would suffer.
Traps that cost marks
- Thinking progressive practices replace the VeriSM model or service management.
- Choosing technology first and defining the outcome later.
- Treating the management mesh as a fixed catalogue rather than a context-specific blend.
- Ignoring culture, skills and partners when adopting DevOps or cloud.
- Assuming every progressive practice must be adopted at maximum maturity.