Releases with themes
When I’m doing agile training, I commonly advise customers to give names to releases and iterations to help them decide which stories belong in which iteration, but it’s not something that I see many customers do and since I rarely take that role not something I do much myself either. But today I got some direct experience!
Cogent is building a software application to help you organize your personal work, and I’m acting in the sponsor role. The details of the functionality are being sorted out by someone else, but I’m the person focussed on the operational requirements and how we get it to the billable stage as quickly as possible (everyone else in interested in this too, but it’s my particular role). Yesterday afternoon I added operational stories to our list, and then prioritised the list story by story, and got what looked like a reasonable response.
Today I went back and created some themed releases, and gave them names.
- Homely – Ugly, but interesting. This release is usable, but won’t win any design awards. We want it first because we’re using the application internally now, so functionality is important. This is the release we’ll pass to “friendly” testers for feedback, so it needs to support a small set of concurrent users without getting too slow. Codename : Homer
- Prettified – Like Homer, but certainly nicer looking and generally more usable. We still won’t be confident in our backup plan, nor have stress tested the application, but it will look professional and be generally usable. Codename : Marge
- Robust – we need this one to be tough, so it can withstand the abuse of a lot of people. This is the point where we can do an open beta – still not charging, but giving the general public access. Codename : Bart
- Billable – something that we feel we could reasonably charge money for. Codename : Lisa
With these releases in mind I went back and looked at my priorities again, and found that some of them were quite different. If you are a customer on an agile project, I strongly encourage you to do the same thing – you may be surprised by the difference it makes.
Hi, Steve
Our human ability to see things from different perspectives is very useful for learning and making decisions. Themes and names are powerful mechanisms for synthesising meaningful abstractions that give life to a new perspective.
Your simple, but rich, example is very illustrative of how we can make better decisions and plans when we adopt a global view, instead of a punctual perspective.
Usually, in non-trivial situations, prioritising stories on a one by one basis is a complex, difficult and sub-optimal process. When we link the stories to higher level objectives, we can achieve much better results: the stories act in synergy towards a well defined focus. The planned releases represent in fact a fast and secure path for launching your product.
Thanks for your inspiring post. I was missing this kind of thinking in my readings. It was a pleasant learning experience to me. I am glad I came to your blog.
Rafael Peixoto de Azevedo
http://sympriser.wordpress.com/
I have encouraged my clients to named their releases and it has helped a lot, as it makes the goal more real to them. It’s like they can not ‘touch’ the result.
The funny thing is that most of the clients choose the same name for the first release, “sputnik”.
I wonder how common first release names are ?