I once was coaching at a team and had a big problem getting their attention and interest. We had many discussions about improvements and I used most of my tools but saw very little change.
It took me quite some time to understand why this was hard, but after a while it stood out like a soar and obvious thumb. And I felt so stupid not seeing that before.
It has to do with purpose and intent.Read on ...
The word backlog has a negative ring to me (and I think to Swedish people in general). A backlog is a list of tasks that and I’ve yet not completed, things that still is required from me or my team. Putting something on a backlog is a nice way of saying; we will look at it… eventually.
(Business) Impacts, on the other hand, has a much more positive, forward-leaning ring to it. Here a bunch of opportunities that we still haven’t tried, that potentially make us even better.
Now it’s a bit sad that backlog is a central word in agile because I think it misses the point, quite a bit, and sets us in a defensive mood from the start.
In this post, I wanted to explore some thoughts I have had in my head on why we should stop using backlogs and start using impacts. Not only the words but the entire list altogether.Read on ...
Today with my team I tried something new for our retrospective. There were a few reasons for me trying something new.
Although I think that retrospectives are a fundamental practice of any agile team and the foundation for a continuous improvements mindset … I still think that I suck at facilitating them. And I cannot get excited about doing so.
Most retrospectives become a wailing-fest of the bad things that happens and very seldom leads to actionable small (!) items that we can implement to improve.
Also … I forgot to book a room after moving the retrospective in time.
These things led me to be a little bit innovative and we ran the retrospective today as described below.
The post will be the description of how to run the retrospectives, a few lines of correct attributions and then a few thoughts about why this worked. Because it was really good! Actually.Read on ...
I had a colleague on one of my gigs many years ago, let’s call him Olle (since that was his name). Olle just got a blood pressure meter for Christmas. He was around 45, at the time, and in reasonably good health, according to himself. But he was one of those guys that “had everything” and someone got him this machine. Mostly for fun.
Now, as he as a gadget geek he loved this new toy and of course started to use it. And he kept records in Excel. A few weeks after he started to track his health, to his horror he saw that he was getting worse by the day he measured.
Now, at the time when he told me this, he just started to measure 3-4 times a day and the result were not promising; his blood pressure was through the roof.
He had a doctors appointment later that afternoon to get proper medication.
I think I’m becoming Olle. And it’s JIRAs fault. And mine own. Mostly my own.Read on ...
Scrum was my first love in agile. I still remember the revolution and excitement I felt after the Scrum Master course and when I and my colleague Öystein started our first Scrum team. It was awesome!
Later I moved on to more flow based approaches when I ended up in environments where Scrum was not a great fit with it s iterations and locked down scope.
Scrum and I was far away from a time. There are no hard feelings but we just don’t hang around much anymore.
I saw someone tweet something like;
I feel like many people talking about Scrum doesn’t really know what it’s about. Really.
Something like that. I felt that it was about me. So I decided to read the official Scrum guide and take some notes. They are summarized in this post.Read on ...
In 2013 I got invited to write blog posts for CodeBetter.com. I was quite surprised and honoured, since that’s a place where I’ve read many great posts over the year.
I hopped to the challenge though (never regretted doing that) and ended up writing 6 posts, before I lost tempo.
I’m actually proud of all those posts and wanted to preserve them here on my site also. I noticed that CodeBetter.com has slowed down and went away completely the other week without anyone noticing. So I thought it would be better to save them somewhere else.
Here’s they are:Read on ...
A couple of months ago I was very fortunate to work alongside a great team. They had a not so envious task before them, namely to introduce a new main concept into an legacy code base. You know, the code has been around for at least 5 years and now you need to add a concept that was no-one ever thought we would have in there.
They did that. In just 3-4 months and delivered with flying colours. I didn’t have much to do with that, I merely observed their work.
When they were done I proudly introduced the team to a new senior in the company and told him about their feat and how they had gone about doing it. His words: well, that’s Lean backwards then.
He was right, but I never thought about it until then. In this post I’ll describe how they worked, what the “lean” way would have looked like and what we can learn from the difference.
Let me just say that the way the team went about their worked, and the feature was a success in production. Very high quality (2 bugs reported if I’m not mistaken) and well received. In order to not put any blame on that great team I will talk about “we” in this post. Although I didn’t have much to do with their success.Read on ...
When our board is lined up as our process it’s quite often an array of columns starting to the left when the idea first comes into mind (or in a backlog column) continuing down our workflow, adding more and more value until it reaches our customers where we can learn from the usage of our new feature.
Although it could be tempting to go through the columns from left to right in our morning meeting, I would suggest that you consider doing the opposite.
My job is to help clients to use and adapt the principles of lean and agile to achieve a better flow of value. Sometimes I get questions from friends and old clients about how to do specific things. And sometimes I get questions from complete strangers.
Last Tuesday was such a day when Emily reached out via email and asked me three insightful questions.
I was happy to do that and my “fee” was that I can publish the questions and my answers here on the blog. So you’re reading my paymentRead on ...
Many daily stand up meetings follow the patterns originally from Scrum - that is we ask each individual what they did yesterday, what they are going to do today and if anything is blocking them.
This is a nice sentiment but misalign our focus.
Because making sure that people are busy is not important… at least not compared to making work flow.
There’s an easy way to change our focus, at least in our morning meetings.
When kanban first came into common use and practice it was often posed as an alternative to Scrum. Well, as Torbjörn Gyllebring told us many years ago, kanban is not your process. Kanban is a process improvement tool and works on whatever process you apply it to. It’s one of the powers of the tool and the reason I like kanban so much.
However, for many early adopters of kanban, removing the cermonies of Scrum sometimes went overboard and we removed everything that constrained us and made us make tradeoffs. Kanban - love it! No planning, no sprints, no constraints - it’s just our board and work flows as fast as it flows… Nice!
Well - it’s not really a kanban board if you don’t have a work in process limit. Let me explain a bit further.
One of the things that always catches my attention when I walk past a board is the colours of the stickies. Why? Because colours requests our attention and can help us in understanding more about a thing. Red is naturally a warning (in western culture at least), green feels ok, etc.
This is why I get troubled when I hear that the reason that we have chosen the colours of the stickies on our board is “because we took the ones that was closest to us”.
That is sad and I share a few thoughts on how to improve on that state of mind - it’s easy.
This comment is closely related to the comment about columns. In this post I’m more specifically want to talk about the “Done”-column. The last column on most boards. I’m on a crusade to rename Done all over the world.
Let’s do it! Done-column - you’re going down!Read on ...
Ok, got a few encouraging comments on the first post so I’ll continue this series. If for nothing else it’s keeping to my orignal blog-idea to write things down to clear it up for me and not forget about it.
This time I wanted to talk about the column themselves, or maybe I dare to talk about the process they reflect. Our process for work!Read on ...
It’s very interesting to see how a practice goes from a nice idea to best practice and over to tradition. In my community, the software industry, things move very fast so I’ve seen many examples of this; simple things like formatting of code, background colors of editor all the way to architectural patterns - all of these become default usages and tradition, and sometime “the way it’s done”. Sometimes people calls it cargo cult which refers to that I often do things without really reflecting over why.
When it comes to my field of practice; lean and agile there’s bountyful examples of cargo culting, but in this series of post I wanted to examine a few very practical things that I often notices on how agile team uses their boards.
It will be a little hit-list of my pet issues commonly found on agile/kanban-boards I’ve seen.Read on ...
Scope creep is a common phenomenon in software development where the size and workload increases beyond what we first envisioned. In many cases this is so small that it happens without anyone really noticing but sometimes it can degenerate and slow down progress considerably. Sometimes even stopping a progress or team completely.
Scope creep comes from many sources, sometimes from the outside, but I think that the most common one are ourselves:
That value should probably be a configuration property…
What if someone decides to change database server…
This is of course good questions to ask and could be value, but I think there’s more value in getting a feature in front of users and learn about their behavior and how the feature is doing. After that we can harden it, make it more flexible or otherwise improve it.
Drifting away from my main topic… So now you’ve experienced scope creep too and how easy it is to fall into. See what I did there ^^
On a more serious note - this post is really about how I’ve seen scope creep being visualised and managed by a few teams on their board.Read on ...
The other day I heard someone distinguish between a few roles that I take on from time to other. I’ve never made the different between those roles clear to myself and as a consequence I end up doing them all at the same time, in my consulting.
This can sometimes be confusing for me, and my clients but makes me also ineffective in the role I’m trying - or is expected to play. I actually wrote about this in a post a few years ago - without really knowing what kind of problem I was addressing.
In this post I wanted to share a few thoughts on these different roles and hopefullyRead on ...
Sometimes I get the opportunity to try things that I never done before, or didn’t think that I would dare. Do those things if you get the chance. Always do them! I never regretted taking one of those opportunities, after they are over.
In this case I got the opportunity to talk with a bunch of school kids (14-16 year olds) about Lean, experimenting and how to iterate ever faster by improving your process. It was quite the experience and I wanted to share some highlights of the time I had together with them.Read on ...
For the record I still think it’s a great event and every time we have run it we have come out the other end in a more aligned, enlightened and excited state than when we went in. And for the record I still think it’s just a phase in our process improvement that we should move away from, in a suitable pace.
I’ve been running 3 or 4 big room planning sessions now and I’m starting to see pattern of what bites us the most and what is the foundation of being successful in these session.
In this post I wanted to share the top 3-4 (there might be few slipping in there) things that I’ve found paramount in order to have a great planning session worth the time and effort.Read on ...
I’m very proud of my church (or corps as we say in the Salvation Army - the Vasa Corps of Stockholm. The moment I came there I felt right at home and I’m more than happy to, voluntary, spend a lot of my leisure time in the different groups of the church.
About a month ago I heard someone, that is new to our congregation, say something that summarised a lot of the spirit in the church:
Here people are saying kind things about each other
That did not only make me feel very proud and happy, but also signals a culture that holds true for many of the great place I’ve been working in or associated with.Read on ...