VeriSM Foundation flashcards
VeriSM Foundation · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- VeriSM definition of value
- Value is co-created with the consumer at the moment of consumption; it is judged by the outcomes the consumer experiences, not by the outputs the provider produces.
- VeriSM principles
- Focus on value, co-create with consumers, work iteratively, keep it simple, be transparent, and evolve continuously; these guide how the approach is applied.
- Service (VeriSM)
- A means of delivering value to consumers by facilitating outcomes they want to achieve, without the consumer owning the specific costs and risks involved.
- Three E's of VeriSM
- The why is governance, the what is service management, and the how is progressive practices and technologies; together they frame the VeriSM model layers.
- Practice-agnostic integration
- VeriSM does not replace Agile, DevOps, Lean or ITIL; it integrates whichever practices fit the service promise, making it a flexible umbrella approach.
- Ecosystem in VeriSM
- The organization operates within a wider network of consumers, suppliers and partners; their capability is part of the management mesh and shapes delivered value.
- VeriSM model loop
- A cycle of define, produce, provide and respond, driven by consumer needs and feedback, which returns to define for continuous improvement.
- Define stage
- Establishes the service promise and requirements by understanding consumer needs and the environment; it sets what the service must achieve before production begins.
- Produce stage
- Builds or assembles the product or service using the management mesh, selecting the resources, practices and technologies needed to meet the service promise.
- Provide stage
- Delivers the service to consumers in the agreed way, making the value available and ensuring the consumer can actually realize the intended outcome.
- Respond stage
- Captures feedback, handles incidents and changes, and feeds lessons back into the next define stage, closing the continuous improvement loop.
- Management mesh
- The bottom layer of the VeriSM model where resources, emerging technologies, management practices and the environment are combined to deliver a service.
- Mesh element: resources
- People, processes, information, tools and finances that the organization combines differently for each product or service according to its needs.
- Mesh element: environment
- The internal and external context including culture, market conditions, regulation and consumer expectations that shapes how services are produced and provided.
- Product versus service
- A product is the tangible or intangible output, while a service is the co-created experience of consuming that product's value with the consumer.
- Iterative, not linear
- The VeriSM model runs as repeating loops; different services may cycle at different speeds, and feedback from respond re-enters define.
- Governance in VeriSM
- Sets direction, defines the service promise and ensures accountability; it is distinct from day-to-day delivery, which is managed through the mesh.
- Governing body role
- Provides the why by defining purpose, values and required outcomes, then holds delivery accountable without dictating how teams execute the work.
- Governance components
- Direction, accountability, oversight and decision rights; these are exercised through the operating model to connect intent with delivery.
- VeriSM operating model
- Connects governance to delivery by defining how work flows through the management mesh and who holds decision rights at each point.
- Separation of governance and execution
- Governing bodies set constraints and outcomes; delivery teams choose how to meet them, preserving accountability while enabling local autonomy.
- Transparent governance
- Policies, risk appetite and compliance requirements are made visible to delivery teams so decisions can be made consistently and evidence can be shown.
- Non-delegable accountability
- Governance may assign roles and decision rights, but the governing body remains answerable for outcomes and cannot transfer that responsibility away.
- Operating model evolution
- Governance periodically reviews the service promise and mesh composition as the environment changes, adjusting the operating model rather than freezing it.
- Progressive practices
- Current, evolving ways of working such as Agile, DevOps, Lean, CI/CD, site reliability and design thinking that the mesh combines as needed.
- Mesh is not a fixed stack
- Practices and technologies are selected and combined per product or service based on environment and requirements, not adopted as one universal set.
- Agile and DevOps in mesh
- Agile practices give iterative delivery and feedback; DevOps practices integrate development and operations for flow, reliability and faster response.
- Lean in the mesh
- Focuses on the value stream, waste elimination and flow, informing how work is produced and how the respond stage improves it.
- Emerging technologies
- Cloud, automation, AI, analytics and containerization enable new ways of working; they support practices but do not substitute for them.
- Balancing mesh elements
- Over-reliance on technology without matching changes in practices, resources and environment undermines outcomes; the four elements must stay aligned.
- Practice selection driver
- The service promise set in the define stage determines which practices and technologies the mesh needs, not habit or vendor preference.
- Continuous improvement in mesh
- Feedback from the respond stage adjusts mesh composition and practice adoption, so the mesh evolves with the service and its environment.