This is the best agile umbrella I was able to find.

What I like about this umbrella is the idea that scrum is just one of many, many things you can do to increase a team's agility. Of course, scrum itself is a subset of the items under the umbrella. I think we all have a tendency to lean towards scrum because that's what we've all been trained in. Because to train agility without a strict framework like scrum would be too abstract. There's just too many facets to agility, and how do you train "courage" and "simplicity". And what does "flexibiltiy mean? Scrum is a nice subset that can get teams started.

That said, we've all tested the waters and we have enough experience now to understand more than we would have before training / experimentation in our own groups. Just focus on a few of the things under the umbrella and consider if your teams are using any of them.

Same with the principles, I think we all read through them before we knew anything. But now that we know more, now that we've "tried agile", reading through them again can be an eye opening experience.

(I'm just sharing some of the things I'm currently thinking about, I hope you all can find some use in it.)

  • No labels


  1. I really like this umbrella Jazahn, thank you for looking for one and posting it.  What I really like about it is that it illustrates both options as well as where agile can be applied (it really is all encompassing).

  2. Agreed, really like the idea of test driven development (I've learned about it through Behavior Driven Development)

    BDD focuses on first developing requirements & specifications that can easily evolve into automated tests.  In a world where every team is lean on QA resources BDD requirements writing can help in establishing solid test cases in a language that works for both the business and development teams.

    1. One of the things you have to understand about BDD, before you can even start to do it, unit tests have to be extremely good. Often, BDD tests are written as borderline functional tests – which means complete units and integrations with mocks. 

      TDD allows developers to plan their development more effectively through testing. BDD adds another layer to that, so TDD is the logical step before BDD if you want to go in that direction. However, in order for TDD to happen, the developers have to get into it. So, as with most best practices, the motivation really has to come from them. 

  3. Another thing I want to note is the idea that you can cut scrum out entirely. Just by focusing on some of the smaller, more abstract items (small releases, simple design, collaboration, coding standard) you can call that being more agile.

  4. I think this is a really good thing to keep in mind as we craft our vision, objectives and guiding principles.  For my group's software development team the Scrum practice was easy to adopt but I am also accountable for a vendor implementation that doesn't have an internal software development team.  I've been listening to the LeanBlog podcast lately and getting some good inspiration to explore different Agile methods.