DE|EN
Meetup "Let´s talk agile!"

‘Value Cycle Loop: Deciding and prioritising on the basis of measurable values’

Let´s talk agile! - Meetup No. 4

OUR ‘LET'S TALK AGILE!’ MEETUP SERIES CONTINUES!

In May 2021, we launched the digital lecture and discussion series ‘Let's talk agile!’ on the Meetup platform.

What motivated us to do this?

The key insight from our work in agile teams and organisations is that the idea of continuous development must also be applied to oneself. Ambiguity requires continuous learning, rethinking and reorganisation and increases the relevance of exchange and networking with others.

We know that successful work in an agile organisational environment requires courageous trial and error and experimentation. Anyone who engages with agile working is aware of the numerous benefits as well as the challenges, which can vary greatly depending on the environment. Working in an agile context is about continuous learning and having the courage to admit mistakes and draw new things from them.

The fourth discussion round with Klaus Wybranietz will deal with the topic ‘Value Cycle Loop and how it works’. Look forward to next year's Meetups!

Klaus Wybranietz

About the guest speaker Klaus Wybranietz

Klaus Wybranietz spent 12 years travelling around the world as an IT consultant for logistics projects - including in Japan, Singapore, the USA and, of course, Germany. After founding antagon AG, later EXXETA AG, he was active on the Management Board as owner for over fifteen years.

Since 2012, Klaus Wybranietz has focussed exclusively on his work as an agile coach and trainer. Today, he supports organisations and managers in agile transformation with the help of Scrum, Kanban, Design Thinking and Management 3.0. (Find out more about Klaus here)

Story points, T-shirt size... none of this is the language of my stakeholders' customers.
Klaus Wybranietz

Missed the event?
We summarise Klaus' key statements for you!

Story points and T-shirt sizes help agile teams to grasp the complexity of a user story and put it in relation to other stories. This categorisation helps the teams, but is not suitable for stakeholders, as story points do not take into account the value to be created.

How can the agile team create transparency about the value of a new requirement/user story for stakeholders?

    don't forget the backlog

    The value created by the fulfilment of requirements includes, in addition to pure implementation, topics such as

    • Updates to the standard software
    • Future security
    • Conformity
    • Security issues
    • Interfaces to other systems
    prioaritize your values and beliefs

    The view of the value generation of agile teams should therefore be expanded:

    The Value Cycle Loop model enables this expansion by evaluating and prioritizing user stories with the help of a value analysis within the gradations Low, Medium and High. In addition, the frequency of technical debts (e.g. necessary further development, installing updates) and incidents (e.g. rectification of errors) is highlighted. Although these are not assessed by the value analysis, the aim is to reduce their frequency in the long term.

    The model enables a 360-degree view and a detailed assessment.

    Value Cycle Loop - 4 simple steps to evaluate a user story:

    And this is how the value analysis works:

    • Step 1: Determining the frequency

    How often is the desired functionality required per month (selected as an example, other time units possible)? (Categorization from 1-10)

    • Step 2: Evaluation of the manual effort

    How much manual effort is required to control the process per month (selected as an example, other time units possible) without IT support? (Categorization from 1-10)

    • Step 3: Classification of the value

    The frequency determined in step 1 and the manual effort assessed in step 2 are categorized in relation to each other in a matrix. This matrix representation enables the values of the user stories to be derived as low, medium or high.

    • Step 4: Value reporting

    The number of values, technical debts and incidents are then shown for each cycle. This creates a framework from the stakeholders' perspective that creates more transparency with regard to the work of agile teams and makes it easier to understand the value of individual requirements.

    Would you like to find out more about how the Value Cycle Loop works?

    You can find more detailed information in the book “SAP, The Agile Way” by our guest speaker Klaus Wybranietz.
    to the book
    Any questions?
    Contact us!
    Carina Werner LETWERK Consulting
    Your contact person
    Carina Werner
    +49 89 189 235 96
    carina.werner@leitwerk-consulting.com
    ... or write us via our contact form
    Contact us!
    Search