Peter will be presenting the following session
  • Peter Maddison

    Peter Maddison - 4 Maps of DevOps

    Peter Maddison
    Peter Maddison
    schedule 1 year ago
    Sold Out!
    20 Mins
    Experience Report

    Although DevOps practices deliver incredible benefits to organizations looking to improve their software delivery practices, the larger positive impact of DevOps to delivering value is often harder to realize. A set of practices we’ve found to help organizations is something we call the 4 Maps of DevOps. 

    Fitting nicely in between the 3 ways and 5 ideals, the 4 maps consist of Outcome Mapping, Value Stream Mapping, Dependency Mapping and Capability Mapping. They help you create a powerful roadmap that is outcomes-focused and targeted at the most important problems.

    Through this talk, I’ll walk through the benefits these maps produce, how they relate to one another and the problems you can target with them.  I’ll go through some real-life examples of using these maps to help organizations.

    This talk is for anybody who is struggling to work out where to start or where to go next with their adoption of DevOps.

1. What got you started/interested in modern software development methods?

I was automating infrastructure and operations since the late 90's. I got more involved in software when helping organizations with DevOps strategy.

2. What do you think is the biggest challenge faced by the software product engineering community today?

Tackling bigger and broader problems as the complexity of systems grows and the role of traditional IT begins to change.

3. What do you think are the most exciting developments in software product engineering today?

The no-code/low-code isn't new but it is getting more momentum and has more capability this time around. Application of AI tooling to augment out capabilities. 

4. Why did you choose the topic(s) you will be speaking about at the conference?

My key focus these days is on helping organizations adopt new ways of working. The method I'm presenting is one I use in that practice.

5. What are some of the key takeaways from your session(s) at Agile India?

An approach to being to understand the flow of work and design a list of improvements.

6. Which sessions are you particularly looking forward to attending at Agile India this year?

Sadly I won't have any time

7. Any personal remarks/message you want to share with the software community?

Keep learning and solving interesting problems.