My business stakeholders wanted the product launch to align with a major event in the political calendar – happens to have been the state opening of British parliament. The product was all about politics so launching simultaneously with a major political event made perfect sense to the business folk. The trouble was that this was just an arbitrary date as far as the development team was concerned. What do you do when the business imposes an arbitrary deadline?
Continue reading
Category Archives: Musing
Build it Twice then Build it again – the 3rd Version Will be Great
It is not something I want to say to a new client, but even before we touch a line of code, I know it will be the third version of their new product that will be great. The first two versions will serve their purpose but will be at just okay from a user’s perspective.
Continue reading
Plug for Henrik Kniberg’s Agile Product Ownership in a nutshell
Just a small plug for Henrik Kniberg’s video Agile Product Ownership in a nutshell. Genius. Watch it.
Continue reading
Agile has Lists but isn’t Lists
Andrew Vos tweeted (@AndrewVos, 15 Nov 2012):
Hey, guys! Guys. Listen. I found this new agile tool! It’s called “writing stuff down in a list, then doing them one by one”1
Andrew is right, the core of Agile planning is a list. Actually several lists. The product backlog is just a list of high level requirements. A sprint backlog is just a list of tasks to do during the sprint. And, more or less, the team does them one by one from the top priority to lowest priority.
But I disagree with the colleague of mine who said to me a couple of years back “Agile is just managing lists.”
Continue reading
Improve Customer Collaboration with Ubiquitous language
Normally I’m quite a calm chap but I get quite grumpy when developers want to model the business domain using technical language. I believe in using “ubiquitous language” and that means using business language to model the business domain.
Continue reading
What to do when a developer produces too many bugs
Brian and Simon were both young and relatively inexperienced developers. One was fast, the other slow, both had quality issues. Too many bugs. What to do?
Continue reading
Lean-Agile is micromanagement but not in an excessive way
Is Lean-Agile micromanagement? Mike Cohn says “yes” but Mike’s use of the term excludes the “excessive” aspect of the conventional definition. An attention to detail is a good thing, making for better management, and Lean-Agile has the tools to make the detail transparent. Excessive attention to detail leads to the Fallacy of Control and horror – I don’t see this in Lean-Agile teams.
Continue reading
Software Batch Sizes are Plummeting
When I said Continuous Delivery is Inevitable I cited shorter iterations as the main driver. However, along with shorter iterations we’re also getting smaller batch sizes. And from a Lean perspective it is the smaller batch sizes that are more interesting.
Continue reading
Three Amigos Meeting – Agree the tests before development starts
“Three Amigos” is what Matt Wynne calls the meeting to discuss the Gherkin scenarios before development starts. The Three Amigos involves the business, development and testing voices. However who turns up, where they meet, what they produce in the meeting, the homework to complete after the meeting, and who does that homework can all vary depending on the particular team.
Continue reading
No need for a PM for a team of one. Professionals manage their own time
What do you do when you’re asked to project manage a team of one? Personally I say “okay” then do nothing. I believe the smaller the team the lighter the process necessary to run the team. When project management merges into time management you don’t need the project manager any more. Professionals manage their own time. I manage teams.
Continue reading