Early in my Agile career I was the only person on my team who knew anything about Agile. Now everybody claims to know Agile and/or to have Agile experience. Certainly this has been true for most people on my last couple of teams. My advice to you is – don’t believe a word of it. Assume they know nothing.
Continue reading
Corporate control = Project brakes
In general I believe brakes let you go faster. But what if the brakes are locked on? Suddenly you’re not going anywhere. And that is what happens when a project comes under excessive corporate control. The project screeches to a halt.
Continue reading
Abuser Story – User Stories to Prevent Hacking
A couple of years ago Mike Cohn introduced me to a cute concept. The “Abuser Story”. A User Story to prevent abuse.
Continue reading
DRY Gherkin: When Using Cucumber, Keep Your Step Definitions DRY
When using Cucumber for automated testing I try to ensure my Gherkin uses ubiquitous language so the business and development team share a common language. But the Gherkin must also be DRY. This not only saves confusion but also saves development effort.
Continue reading
What do you do when the business imposes an arbitrary deadline?
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
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