January 2013
Monthly newsletter prepared by Gojko Adzic and colleagues from Neuri Consulting
Previous issues | E-mail subscription | Folow on twitter | Unsubscribe
First of all, Happy New Year and may 2013 bring you a lot of opportunities to make a big impact on your team and organisation. To get you started, here are some great articles and videos published in December.
Jez Humble's video from GOTO conference talk What is value? is his summary of lessons learned while working as a product manager for Go, the CI and release management server at Thoughtworks Studios. He looks into different models for determining value, measuring value and estabilishing feedback loops. If you're interested in impact mapping, make sure to watch this video. Another good reason to watch it is to understand why Nigerian scam e-mails got significantly worse over the last few years.
Peter Bregman warns about the dangers of side-effects associated with goal setting, including neglect of non-goal areas, a rise in unethical behaviour, distorted risk preferences and corrosion of organisational culture. I'm a firm believer that good goals are necessary for successful software delivery, and I've written extensively on this, but I still recommend reading this article for it reflects the dangers of going too far. The author suggests choosing an area of focus instead of setting a clear goal. Not sure I agree with all the conclusions, but this is definitely an interesting thing to experiment with.
Matthew Skelton wrote a summary of a talk by Chris O'Dell and Steve Freeman on the implementation of GOOS ideas at 7Digital. The post has some nice quotes and references, both from the event itself and the GOOS book, on the purpose of tests, dependency injection and logging. If you've not read the book, this might inspire you to do so. If you've read the book, this blog post might point out some hidden gems.
Jim Bird warns against hiding redesign and rewriting code under the name of refactoring, and provides some nice references to Martin Fowler's and Kent Becks's work to explain what refactoring was originally intended to mean. What refactoring is, and what it isn't is a nice refresher, and a useful link to send out the next time someone requests a week for refactoring.
J.B. Rainsberger brings user stories back to their roots, as a promise to hold a conversation, by proposing a new template for user story cards.
The questions of accountability and responsibility are often the biggest stumbling blocks for managers to accept self-organising teams, and for organisational change towards adopting Scrum or Kanban in my experience. Tobias Mayer published two post s on this (The Accountability Trap and Accountability Revisited) trying to clarify the difference between the two aspects. His first post sparked some interesting comments, well worth reading as well.
Rob Lambert summarises John Seddon's talk from EuroSTAR 2012 on failure demand, where process or system failures create a demand elsewhere. Through a case study of optimising a call centre at Aviva, Seddon's story and conclusions show the danger of running systems based on cost and not on value, and of optimising the wrong things. Rob Lambert continues the post by drawing parallels between Seddon's story and software testing. You'll also find links to two videos of similar talks in the blog post. Recommended reading for anyone trying to improve software delivery in their team or organisation.
Finally, Bob Marshall's post on Approaching Change is a fantastic summary 23 different options for organisational change, with great references for further research.
Attend my next Impact Mapping and Specification by Example workshop in London with 30% off. Book online with the promo code impact before February 1st to get this dicount.
ScrumTrek and AgileRussia community are organising the 7th International Russian-language Conference on modern approaches to software development, AgileDays, in Moscow from 29-30 March 2013. Book with promo code AgileDaysGojko to get a 10% discount.
Without doubt, my favourite book of 2012 is Lean from the Trenches: Managing Large Scale Projects with Kanban. I once heard the author speak at Oredev about his papers as an occasional brain-dump, kind of emptying short term memory so that he could learn new things, and this book is a great example of that. Without dogma, buzzwords or marketing, Henrik Kniberg notes lessons learned from a uniquely interesting project, where lean software delivery principles were applied to a large scale public sector effort with great success. I particularly love that there is no preaching, the author does not claim that what worked for them works universally, but tells a great story with deep insights and lets readers make their own conclusions.
I read the book in one go, without putting it down, during a five hour flight. The first part is the case study of the delivery of the Digital Investigation System for the Swedish Police Authority. The second part is a deeper dive into the techniques and tools used to set up and run the delivery process. The book is for experienced practitioners and newbies alike. People new to Kanban and Lean software delivery will benefit from a real-world warts-and-all case study, with a pretty good example of how things were set up. Examples of process metrics, bug handling, setting up a Kanban board across teams and handling technical stories will be particularly interesting to people who had some prior knowledge but haven't seen the techniques work at large. Part II will probably help newbies make a lot more sense out of Part I, so if you are completely new to the topic it might be worth reading the second part first. Practitioners will benefit from some nice insights and ideas spread across the first part of the book, for example imposing work-in-progress limits on bugs, distinguishing between buffer and WIP columns on Kanban boards and setting up a "continuous process improvement engine".
The last point is incredibly important, as continous process improvement is one of the key aspects of successful delivery in my experience. Knibeg nails it with "A great process isn’t designed; it is evolved". Many other authors have written on this topic, but Kniberg's unique contribution with this book is a simple guideline that will help teams put this in place: Clarity, Communication, Data. Kniberg documents how physical boards provide visibility and clarity, how periodic process improvement workshops within a team and across teams communicate ideas and how simple metrics provide data to help a team stay on the right track. The entire chapter 10 is devoted to this topic. In addition to that chapter, my special thanks go to Kniberg for his glossary appendix, where he lists how they avoided the buzzword lingo that turns off so many people. For example, using "Process Improvement Meeting" instead of "Sprint Retrospective".
Five out of five stars, without hesitation. Drop whatever you are reading now and read this one instead.
Lean from the Trenches: Managing Large-Scale Projects with Kanban
Verdict:
Author: Henrik Kniberg
Publisher: Pragmatic Bookshelf
ISBN: 978-1934356852
Pick it up from
Amazon UK
or
Amazon.Com.
No, it's not Uncle Bob's third book in the Clean series, though the title might suggest that. Clean Language by Wendy Sullivan and Judy Rees is a book about an interesting communication technique. The book was published in 2008, but I only recently came across it, and it impressed me enough to recommend to my readers.
The central idea of the book is that metaphors are a fundamental tool for organising thoughts and we use them subconciously to make sense of the world, without even being aware of it. Some typical examples of that are temperature used for affection ("They greeted me warmly."), size used for importance ("Tomorrow is a big day."), height used for quantity ("Prices are high."), and purpose represented as a physical object of desire ("I saw an opportunity for success and grabbed it."). Though such simple metaphors should be unversally understood, more complex metaphors can be easily understood by different people in different ways. The authors argue that we can get better understanding and awareness of others' and our own ideas by recognising metaphors, pushing them from subconcious processing into concious analysis, understanding the ties between a metaphor and the real situation and reverse-engineering metaphorical solutions into real ones. For example, the next time you feel stuck while working with a computer program, try thinking about what kind of stuck feeling that really is and what would make you feel unstuck.
Clean Language is an approach to soliciting information and facilitating discussion that recognises this central role of metaphors, helps us spot metaphors in other people's thoughts and our own ideas and makes those connections explicit. The premise of Clean Language is that such concious analysis of metaphors helps understand other people better. One particularly eye-opening aspect of this approach for me was how much my own metaphors and assumptions can cloud my understanding of clients' issues and situation. Clean Language provides a toolkit, through a set of twelve questions, that prevents polluting communication with our own metaphors, hence the title "Clean". Instead of introducing our own metaphors into the mix, Clean Language questions help people improve active listening.
Most of the examples in the book are about psychology, and helping people with psychological issues, but I've been able to translate many of those examples easily into my everyday consulting. Since reading the book, I became a lot more attentive to the way others use metaphors and a lot more careful about driving the conversation with my own metaphors that could be easily misunderstood. This hardly makes it a life-changing experience, but anything that improves communication will surely be a useful toolkit for many people in our industry. Business analysts, team leaders, process improvement coaches and consultants will probably benefit from this book the most.
I give the book four out of five stars. For all the good content, there is a bit too much repetition for my taste in the book. The example discussion sessions sometimes go on forever and I found myself skipping large portions of those parts.
Clean Language:Revealing Metaphors and Opening Minds
Verdict:
Authors: Wendy Sullivan and Judy Rees
Publisher: Crown House Publishing
ISBN: 978-1845901257
Pick it up from
Amazon UK
or
Amazon.Com.
By popular demand, I'm now running a full day practical Impact Mapping workshop:
For those that want to learn more about specification by example, try it out in practice, and discuss advanced ideas, I'm organising SBE workshops in many places all over Europe
In 2013, I plan to attend far fewer conferences than in the previous years. Here are a few speaking engagements I have confirmed so far:
That’s it for now. Until next time...
Gojko Adzic http://gojko.net @gojkoadzic