10 times better quality with agile transformation. How we did it!!!

schedule Mar 27th 05:15 - 06:00 PM place Grand Ballroom 2


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.


Presentation technique

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. 

Presentation backlog:

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...

Learning Outcome

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.   

Target Audience

Scrum masters and Product owners, Developers and Testers, Project/Product managers, Leaders

schedule Submitted 5 years ago

Public Feedback

comment Suggest improvements to the Speaker
  • Naresh Jain
    By Naresh Jain  ~  4 years ago
    reply Reply


    This is an important topic, I'm sure many companies would be interested in hearing your experience. I'm trying to find what specific practices helped your team? Can you please update your proposal with the specifics of the practices used and how they helped your team.

    Also I really like the format of your talk. It is applying agile principles to your presentation style itself. I've seen some people present this really well, while some have struggled with this format. To help the committee gain confidence in your presentation skills, can you please share a short video of your past presentation?

    Thank you.

    • Naresh Jain
      By Naresh Jain  ~  4 years ago
      reply Reply

      Mikael/Fredrik, any update on the previous comment?

      • Fredrik Hedlund
        By Fredrik Hedlund  ~  4 years ago
        reply Reply

        Hi Naresh

        Sorry for the delay. Both Mikael and I have been on holidays, celebrating Christmas/New Years.

        How we did it: We have found, and also believe in, self organizing teams by setting a structure and goals to reach to be the most important factor for us. Each team define their own goals based on the project goals and the structure defines how we work together within the project.

        Number one practice: We banned top-down leadership. No leader should tell the project how they should solve a problem. Believe in your coworkers

        Number two practice: Evolution instead of revolution. We take one step at a time and evaluate the outcome of the alteration before we change something else. We almost always use pilots (often one of the teams) to evaluate a change before deciding how to move on.

        Regarding a video we don´t have one at the moment. We can record one if you want.

        • Naresh Jain
          By Naresh Jain  ~  4 years ago
          reply Reply

          Thanks for the clarification Fredrik. So far I'm liking what I'm hearing. The video will really help us make the final decision. Can you please upload a short video recording. May be do an quick overview of your topic (like a trailer of the movie.)

          • Mikael Lundquist
            By Mikael Lundquist  ~  4 years ago
            reply Reply

            Hi Naresh

            Ok, we will record a video and upload it. It will probably be uploaded in the beginning of next week.

            • Fredrik Hedlund
              By Fredrik Hedlund  ~  4 years ago
              reply Reply

              Hi Naresh!

              We just updated the proposal with a link to a short video. We are not video producers, as you can see :-). Enjoy!

  • Prasad
    By Prasad  ~  4 years ago
    reply Reply


    It will be useful if we can throw lights on what was interprtation of Quality? key factors influencing that.  TVs comment is very relvant..


    • Fredrik Hedlund
      By Fredrik Hedlund  ~  4 years ago
      reply Reply


      Mikael and I work within the higher education area in Sweden and nation wide study administration tools for the higher education area are among the systems we develop and maintain. Our customers definition of quality in priority list are: 1. A useful product. 2. No stopping errors in production. 3. No serious errors 4. Cost effective maintenance and development.

      The problems we faced was to many stopping errors in production. One year when we had reached 80 stopping errors the customer told us it was enough. We had to do something. Until then we had tried to solve the problem by pointing out the importance of quality within the organisation, we launched a quality assurance program and successfully went through a ISO-cerfification program, but to no use, since the problem with many stopping errors in production didn´t go away. We have always used some level of agile development, coming from DSDM, but it was when we launched the idea with goals and self organising teams we felt we had found the right buttons to press. Four years after our agile transformation we reached zero (0) stopping errors in production during a year and the product is more usefull than ever.

      Please keep asking if you want to know more!


  • Tathagat Varma
    By Tathagat Varma  ~  4 years ago
    reply Reply

    Mikael - the review panel gets many proposals that talk about agile transformation efforts. Just so we have a better understanding of it, can you share a bit more information about the kind of problem you were facing, what were some of the earlier approaches tried and what was its effectiveness, what kind of organization are we talking about, and so on. That will help us get more data points and decide on the proposals that are most likely to resonate with audience.


  • Joel Tosi
    By Joel Tosi  ~  5 years ago
    reply Reply

    Hi Mikael,

        The link you posted goes to a conference website, was there something inside that site you wanted us to see?

    While your approach is interesting, what happens if the backlog gets prioritized and it makes no sense in order?  Have you done this presentation before?  I'm concerned because when I see timings that aren't round numbers, you need to stay more accurate and with what you are trying, that could be super challenging.



    • Mikael Lundquist
      By Mikael Lundquist  ~  5 years ago
      reply Reply

      Hi Joel,

      The audience will have an impact on the backlog, but it's still up to Fredrik and me to present it in a way that makes sense. We have done this presentation before, but not exactly like this. You have the opportunity to be first :-).

      Im not sure if i understand your worry. Can you be more specifik? I'll be happy to update the proposal.



      • Joel Tosi
        By Joel Tosi  ~  5 years ago
        reply Reply

        Hi Mikael,

            Good to hear that you and Fredrik will coordinate it, I was concerned you would just do a sort rank and start presenting which could be wildly confusing ;)

        My other concern around the timings is usually people would group topics into slightly larger, rounder timeframes - i.e. problem introduction is 5 minutes, exercise is 20 minutes, etc - that way if something is off by a minute or two, you are still fine.  Your timings of 2 minutes and 3 minutes - if you are off by a little bit, you are off by a large %.  If your 3 minute session goes 4 minutes - do you get rid of the 2 minute one (assuming it was chosen).

        If this isn't a concern, please let me know.  



        • Mikael Lundquist
          By Mikael Lundquist  ~  5 years ago
          reply Reply

          Hi again Joel

          You have a good point there. But we would like to keep the figures in non round timeframes to be able to showcase real world problems, where the figures seldom fit into the boxes we want to place them in. In fact, this is a real world problem in the ICT world. We dont think this is a concern.

          This way of present our talk serves two purposes:

          1. By letting the audience influence our talk, we think they will learn more. Its a key factor of a successfull presentation.

          2. We know the the audience learn more if we both "do" and "talk" what we want to say.


          Regards Mikael and Fredrik