OCIRIS GLOBAL

Continual value assessment techniques: how to compare the value expected from the use of digital products with the value realized? Read this article to discover some of these techniques... #ocirisglobal #valuemanagement #continualvalueassessment

Quote from the ITSM Value Streams book: keep options open as long as possible Concept It is expensive in terms of time, effort, resources and cost to change a decision when it is in a later stage of development and implementation than when it is on the design board. Aspects to consider Solution development is an inherently uncertain process. There are various factors that could contribute to change in scope due to changing business needs or technology changes. Also, innovative new systems have, by definition, never been developed before, so there is no guaranteed path to success. There is wastage to roll back an implemented decision and to remove the footprints of a wrongly deployed solution. The new solution may require change in working practices, retraining staff and support teams and educating end users on how to use the service. Traditional, sequential, stage-gated development practices drive developers to quickly converge on a single option – an agreed point in the requirements and design solution space – and then modify the design until it eventually meets the full system intent. Everyone feels good that they have the right requirements and the right design. At least for a while. Indeed, this can be an effective approach – unless, of course, one picks the wrong starting point. Then subsequent iterations that are done to refine that solution can waste time and lead to significant delivery problems. Possible practices To avoid this issue, a set-based design (SBD) approach could be used in which developers cast a wider design net initially, considering multiple design choices at the start. After that, they continuously evaluate economic and technical trade-offs, they eliminate the weaker options over time and ultimately converge on a final design, based on the knowledge gained to that point. This process leaves the design options open for as long as possible, converges when necessary and produces more optimal technical and economic outcomes. You can get the book with a discount by ordering it at: https://lnkd.in/e-N6Qkws The co-authors of the ITSM Value Streams book that I had the pleasure to work with are Akshay Anand, Mark Smalley and Rajiv Dua #itsmvaluestreams #bcspublishing

SLA vs XLA vs VLA: what are the main differences and why should I care? Watch our new video on that topic at: https://lnkd.in/eWCXjxAc Stay tuned. #ocirisglobal #valuemanagement

Differences between a backlog and a register ? We are all familiar with the concepts of risk register, continual improvement register or product backlog but what is basically the difference between a register and a backlog? ? Backlog: Purpose: A backlog typically lists tasks or initiatives that are planned or in progress, often prioritized for action. It’s dynamic, updated frequently, and reflects an evolving roadmap. Nature: Backlogs are inherently actionable; they include items that are intended for future implementation or development. Application: Common in agile and iterative environments, backlogs are used to drive progression toward specific outcomes. Register: Purpose: A register is more of a catalog or log, documenting items for reference and tracking purposes. It may capture historical or current information without necessarily prioritizing or planning for immediate action. Nature: Registers are often static or semi-static, updated less frequently and typically used for monitoring, governance, or compliance. Application: Registers are widely used for items that need long-term documentation (like risk registers or asset registers), focusing on recording information rather than planning execution. Follow OCIRIS GLOBAL for insights on service and value management #register #backlog #ocirisglobal

??Exploiter les capacités de gestion des services informatiques (ITSM) pour la gestion des services d'entreprise (ESM) Avec l'aide de notre expert ESM/ITSM David Billouz ??, explorons comment l'ESM ?? aide les départements non informatiques à utiliser les mêmes cadre et outils ITMS pour améliorer ??la prestation de services ??la collaboration et ??l'efficacité à l'échelle de l'entreprise. Lisez-en plus dans notre blog?? https://zurl.co/bY3d OCIRIS GLOBAL

Dear all, We are delighted to offer you this free webinar on ProSolvr : Visual AI-powered Root Cause Analysis to resolve problems, forever ?? In this webinar our speaker David Billouz will conduct a demo to showcase how prosolvr can help solving the following issues related to the use of Ishikawa technique: ? Lack of collaboration between team members ? Loss of knowledge on the results of previous Ishikawa analysis ? Lack of automation for Root Cause Analysis ? Loss of time to find root causes that have been already applied in another part of your organization ? Lack of digital support to share the Root Causes among the organization So join us for this free webinar on 31st of October at 11:00 AM UTC/GMT Time. #ocirisglobal #prosolvr #fishbone #rca #ishikawa #ai

??Exploiter les capacités de gestion des services informatiques (ITSM) pour la gestion des services d'entreprise (ESM) Avec l'aide de notre expert ESM/ITSM David Billouz ??, explorons comment l'ESM ?? aide les départements non informatiques à utiliser les mêmes cadre et outils ITMS pour améliorer ??la prestation de services ??la collaboration et ??l'efficacité à l'échelle de l'entreprise. Lisez-en plus dans notre blog?? https://zurl.co/Mqx3 OCIRIS GLOBAL

The Grey Zone of Value Measurement in ITSM In IT Service Management (ITSM), the distinction between output-based and outcome-based metrics is clear. Service providers focus on delivering outputs—availability, response times, or system uptime. Meanwhile, the customer is responsible for realizing the value from these IT services through their consumption. But here’s the catch: neither the IT service provider nor the customer is truly measuring that value. This is the grey zone of accountability in ITSM. Value in ITSM often remains abstract, with no clear ownership of how it’s measured or tracked. The IT provider delivers outcomes, but the ultimate value—the business impact of those services—often goes unquantified. Without a collaborative approach to measuring this, organizations miss out on capturing the full picture of value realization. Bridging this grey zone requires new frameworks, shared accountability, and metrics that go beyond technical outcomes to reflect true business impact. Follow OCIRIS GLOBAL for new insights on service and value management

In this new article we explore the sources of declared value for products and services.

Upcoming ITIL? 4 Advanced Modules Public Classes in Sept '24 (G2R)! Check our upcoming ITIL? 4 Advanced Modules Public Classes (PeopleCert accredited training and exam) in September 2024 (Guaranteed to Run (G2R)): ? September 18-20 - ITIL? 4 Strategist Direct, Plan and Improve (DPI) ? September 23-25 - ITIL? 4 Specialist Drive Stakeholder Value (DSV) ? https://lnkd.in/gZ5b6Wqp ITIL? 4 is an integrated set of processes and best-practices for delivering IT services to customers. It's the most widely adopted approach to IT Service Management in the world. ITIL? 4 Advanced Modules classes include an exam voucher and prepaid voucher for retake exam (Take2). #career #itil #axelos #peoplecert