Avoiding the meeting menace for your development team

Have you ever heard members of a development team complain about too many meetings? And when you look in their calendar all you find is a couple of meetings spread out through the week. As a Manager, Scrum Master, Product Owner etc. you might have thought “That’s nothing – I have meetings a day long!”. This is a natural reaction but the point you are missing is that the nature of your work is radically different compared to that of the development team. While a lot of your work is done in meetings and your days are fragmented the teams work doesn’t work that way. Paul Graham describes it very well in his post from 2009 about the Maker’s Schedule and the Manager’s Schedule (I really recommend reading the whole post). He describes that a developers day may be blown to pieces if meetings are scheduled in a way that prevents them from getting some flow in their work. To remedy this I recommend talking about this within your team and adding it to your Teams Working Agreement (because you have one of those, right?).


Examples of how this could look in practice:

  • Do like Facebook and have a meeting free day per week. During that day the team can completely focus on the work at hand without interruptions.
  • Have something similar to visiting or opening hours for the team. During these hours it is ok to schedule meetings. When you choose these hours I recommend considering having your prime working hours (high energy) as your non-meeting time. On the Working Agreement this could be formulated something like:
    • “We are all in the office at least between 9 am and 4 pm. Meetings are scheduled after 2 pm.”
    • Or “We do meetings after 2 pm. All meetings have a clear agenda and purpose. We are on time.”

I really recommend trying this out. And who knows, maybe you as a non developer find value in getting some uninterrupted thinking time as well.

Ps. You should of course still talk to people if you need help getting unblocked or help someone else get unblocked. “People and interactions over processes and tools” is still what we strive for. This is merely a tool to help getting you meetings under control if that is a problem for your team. Ds.


Staying safe? Impressions after attending a SAFe training

I just attended the SAFe training “Scaled Agilist”. In this post I’ll describe my first impressions. To start off I need to say that I was skeptical about SAFe before taking the training. I wasn’t very impressed about what I had read about it on blogs/twitter and hearing about it in short presentations. But I wanted to learn more about it as I think it is something we will to get used to in the agile community. I wanted to give it a shot – perhaps it was something in there that was really useful that I just hadn’t seen.


I’ll start with the positives about the training.

  • It went through a lot of nice basics with flow theory, how to treat knowledge work, lean, queue theory, feedback, decentralized decision making, agile values, early value delivery, WSJF etc. To me this was all good but also a clear way to build ethos. “Yea, we are pals with all these cool agile kids.”
  • It goes through a lot of things considered “best practises” in the agile world like:
    • Using Kanban to handle the portfolio level.
    • It talks about sound code quality practices (XP) in the teams.
    • How to manage the balance between business driven work and architectural driven work (on an epic level).
    • Replacing projects with continuous work.
  • The “Hardening Sprints” have been replaced by a “Innovation and Planning Sprint”. I really disliked the old concept of reserving two weeks for integration and bug fixing. To me that just seemed very waterfall. Now there is that but also room for innovation, hackathons etc.

Alright, so those were the good parts but to be honest, didn’t we already know about all of that? It is not like SAFe came with anything new – it just re-packaged what we already knew. I guess that the value SAFe adds is that it is now a model that can be “sold” to management… well, since it’s a model.


To the negatives. Since many others have already bashed SAFe (see the first slides in this presentation) I’ll just stick to some particular things to the training I attended. (A disclaimer is that this was the first time this trainer taught this class so all things might not be according to what others are saying.)

  • It feels very much like RUP with a lot of stuff/artifacts. Some might bring value to your context but others won’t. I see a big risk of people searching for a quick fix silver bullet will want to install SAFe into their organizations as is. Without understanding why they do it or how they should take it further.
  • In the two day release planning session you lock down in detail what everyone is going to work on over the next ten weeks. Whatever happened to “responding to change over following a plan”?
  • The release planing sessions sounds like it could have been useful to someone in some context. But is it useful to all? I don’t think so. To me it sounds like something you could blog about, for others to draw inspiration from and tweak to their context.
  • So, grouping up a bunch of teams and looking a dependencies is a really good idea. But instead of trying to break those dependencies to create autonomous teams the direction SAFe is taking is to accept the dependencies and spend a lot of time working around them.

At the end of the course I asked the trainer what companies would really benefit from using SAFe. It was an honest question since I really couldn’t see it. The answers sort of made me fall off my chair. According to him it needed to be really big multinational corporations. In Sweden (this is where I took the training), he said, we only have one of those and it is Ericsson… So why on earth would you then sell this training/model in Sweden to people who are not working at Ericsson? Is this just a new moneymaking machine for trainers to sell certifications? In this case I guess the answer is yes. Since the trainer was also selling his own model for scaling in mid-size corporations I would like to get a second opinion on that statement. Also, if you are already delivering value more frequently and are actively working towards having autonomous teams SAFe (according to the trainer) isn’t for you. Your organization needs to be really messed up.

So a conclusion is that if you like me is living in Sweden and not working at Ericsson – spend your money elsewhere.

Wrap up

To wrap up I’d like to quote Don Reinertsen in his foreword to Dean Leffingwells Agile Software Requirements (that describes sort of a first version of SAFe).

//…// I suggest paying attention to several things. First, try to understand the reasons why certain of these approaches work, not just what they are. If you understand why things work then you can more easily adopt them to your own unique context. Second, treat these ideas as a portfolio of useful patterns rather than a rigid set of practices that must be adopted as a group. //…//

Unfortunately these wise words are all lost in SAFe. It is taught as a “do all or it will fail”-process. Very similar to the way Scrum is taught in many places. But we all know that you shouldn’t do only Scrum by the book – it is  a starting point. And that is what use I see for SAFe – a starting point if you have a really big messed up organization it could serve as a replacement and a starting point when replacing your process. If you don’t have that – consider it a patterns book. And very much like when you use a design pattern when coding. Make sure you understand what problem you are trying solve and also understand the thinking behind the pattern you are thinking about applying.

Sharing is caring

Back from a week of training I have decided to start sharing some of the work that I do. So on this blog I’m going to post things related to my work. Mainly this will be related to agile and lean software development, teamwork and leadership.

I have already written some posts that I have backdated to avoid an empty blog.

Some posts that are in the pipeline already:

  • How to work with continuous improvements without doing retrospectives.
  • Building a network of competence groups – by the members for the members.
  • Time for a new manager – let the team choose.
  • Cookbook for initiating a new team.

Stay tuned!

Team (Squad) Health Check

Last year I was helping out at Spotify as an Agile Coach. One thing we developed/introduced when I was there was a new way of measuring how well the teams (or squads as they call them) are doing from a range of different perspectives. The coaches at Spotify have now blogged about this formats so I thought I would mention it here as well.

I can really recommend it as a tool to use in retrospectives. It lifts the discussions to cover important areas that might otherwise not be discussed. In my experience doing it on a quarterly basis works quite well.

The full blogpost can be found on Spotify Labs.

One thing they forgot to mention in the post that we initially had an “What card did we forget”-card. This was to discover important areas that we as coaches had forgotten. If someone were to adopt this tool to their context I would really recommend having that card.


Go and see bingo

A few Agile Coaches and me at a customer discussed that some managers rarely had the time to spend time with their teams. To remedy this we gamified visiting stand-ups. We called it “go and see bingo”. We starting by creating a map where you can see the location and times of all teams stand-ups. Then we added a bingo-field where the teams are listed from left to right and the managers from top to bottom. Each team was then given a set of stickers that they awarded managers who visited their stand-up. This sticker was then put on the bingo-field in the corresponding box. The first manager to fill their row won eternal fame and glory.

This initiative was well received by the managers and we could immediately see a shift in behavior from their part. The challenge will now be to make the behavior stick and not just be about the competition.