10 times better quality with agile transformation. How we did it!!!
In 2011 the Ladok section at ITS had serious quality issues, resulting in dissatisfied customers. At the beginning of 2012 the section started an agile transformation, in steps, throughout the whole section. One year later the whole section had transformed and currently the section now eats, sleeps and breathes Agile. The quality has improved remarkably and our customers are understandably much more satisfied. Besides satisfied customers, our employees are happier.
The ideas to try agile came from the people working in the project and we think that was an important factor for the success.
We are going to talk about our experiences of this transformation and how the transformation contributed to the remarkable increase of the quality. The talk will cover the background, our roadmap, the result of the transformation and the factors of success.
We have identified two key factors of our success that we will promote a little extra during our talk.
We are going to perform this presentation in an agile way, in the way we interpret scrum. This means that we are going to interact with the audience and we expect them to influence our presentation.
The point is to not just talk of how we did, but also show it on stage. We also think that this is a good way for the audience to really get the most out of the presentation.
We want you to prioritize the presentation parts
We consider the different parts of the presentation as the presentation backlog. We want the audience to prioritize the parts of our presentation, in advance. Prioritize here.
Outline/Structure of the Experience Report
Short introduction 1 min
Short introcution of the presenters
Presentation technique - 4 min
Short description of the presentation
Presentation sprint 1 - 18 min
This is the first part of the presentation, with parts from the presentation backlog below.
Reflection and reprioritization - 1 min
Short reflection of sprint 1 and possible reprioritization before sprint 2. If it's needed.
Presentation sprint 2 - 18 min
This is the second part of the presentation, with parts from the presentation backlog below.
Q&A - 3 min
Help us make the best presentation for you
In the presentation backlog below we list the possible different parts of the presentation. The sum of the parts makes more time then we have for the presentation. Therefore we want you to help us pick the parts you want to heare more about. Prioritize here.
We think of you, the audience, as the Product Owner of the presentation. It's up to you to prioritize the presentation backlog so that we can put together the best presentation for you.
Introduction of speakers 3 min
A longer introduction of the speakers.
Our company 5 min
Here we will describe our company and our product portolio.
Problem description 5 min
In this part we will describe what was our quality issues and the situation back then.
Roadmap 6 min
We will talk about the roadmap of the transformation. What we did in what order and so on.
Now and then (basic differences) 6 min
Here we will show you and talk about the basic differences before and after the agile transformation.
Practical example 8 min
In this part we will show an example of how we actually work. It is a practical example of how we perform a sprintplaning session together with our product owners.
Effects of the transformation 4 min
There are many positive effects of the change. In this part we show them to you.
Result of the transformation 2 min
The result is 10 times better quality!!! We will explain it in more detail.
Key factors 2 min
And the key factors are...
We will give the audience our two key factors for success. We believe that these two factors can be used to improve the outcome in every project.
Our goal with the presentation is that the audience not just will learn from our experiences but also that they will remember it.
We believe that the best way to achieve that is to get the audience involved and make the presentation somewhat different from the regular powerpoint shows.
Scrum masters and Product owners, Developers and Testers, Project/Product managers, Leaders