I first got in contact with Joakim Holm and Jagannath Tammeleth (the authors of the book I’m about to review) at Agila Sverige (Agile Sweden). Actually, this year the conference was kickstarted by Joakim, dressed up as a punk rocker talking about ”Agile is not dead – It only smells a little”. Via Twitter I found out that the book with the Swedish title ”Värdefokuserande teamarbetssätt” was released. That roughly translates to ”Value focused team working”, the subtitle is ”A guide in eight steps for teams that wants to master the basics in agile system development”.
This is actually the second time I do a review on a book written in Swedish, my native language. I realize that many of you will never get a opportunity to read the book, but according to my blog statistics Sweden is in third place when it comes to visitors (after USA & UK). The book has 154 pages and was released in 2016.
“Agile is ordering tapas til you’re full ‒ not ordering a 10-course meal.” ‒ Neil Killick
The team ways of working selected for the book are (each covered in a chapter):
- Small batch sizes
- Maintaining a backlog
- Common planning
- Agreed guidelines
- Visual guidance
- Sync meeting
- Demonstrate the result
- Continous improvements
Does those ways of working make a good representation for a team? Yes, I think so. I can’t come up with anything that should have been added to the list. Each chapter has sections for: purpose, description (i.e., more details), learnings from the reality and references to further reading. All topped up with recommendations and tips!
Small batch sizes are fundamental in agile. And the ambition to go from large batch sizes (enormous waterfall projects that are doomed to fail) to small batches (handling customer deliveries in a continuous flow). Large batch sizes gives delays that in turn hid process problems that never will surface. On the other hand it’s not easy to shift to this way of working if you are coming from waterfall.
The backlog is something very familiar for an agile team. To produce a backlog is not a one time job (you do it and then you are finished). The backlog needs to be looked after all the time. A way for the team to understand what is important is to have a common planning.
It may not come as a big surprise that visual guidance is my absolute favorite thing about agile. It’s said that ”a picture says more than thousand words” and it’s really true. What you ”see”, you can do something about. What you don’t ”see”, well, there is nothing you can do then.
The sync meeting is usually the first ”aha moment” and most valuable thing, when starting with agile ways of working (being a team using Scrum and Kanban). Starting off the days by sorting out what is most important, who needs help, etc., has been done before but with agile it has really got high-lighted.
When first starting with agile ways of working (being a team using Scrum and Kanban) the first ”aha moment” and most valuable thing is the sync meeting. Starting off the days by sorting out what is most important, who needs help etc. has been done before, but with agile it has really got high-lighted.
The get feedback on your work, one good way is to demonstrate the result to others. I think the demo is a good thing, but sometimes it represents a too long feedback loop (to get input on your work when you are done, not when you are doing it).
Finally the fundament in lean, the continuous improvements (also known as kaizen). I’ve heard a story about an agile coach that was hired to ”implement agile” within a company. He started out with implementing just one practice, the retrospective meeting. With that in place he could steer continuous improvements to set the other principles and practices in place.
I really enjoyed reading this book! It is short, well structured, and to the point. The illustrations are awesome! I also really liked the fact that it took the standpoint from the team’s view, when describing good agile ways of working. If you can read Swedish and want to have value focused team working, you should definitely check it out!
All the best,
Tomas from TheAgileist