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
Tag Archives: agile
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
Observing, eavesdropping and overhearing – essential tools for a software development leader
I believe in Management on the Ground and what better way to be on the ground than to be sitting with the team in an open plan office. By simply observing, eavesdropping and overhearing I know what is going on and I also get early warning when I have to intervene.
Continue reading
Brakes let you go faster
Perhaps counter intuitively brakes let you drive fast. Without the brakes we would drive really, really slowly. I believe the same is true of automated tests. Something that looks like it should make you go slower actually lets you deliver code faster. As long as you’re doing the right tests.
Continue reading
Accuracy vs Precision in Estimation
Which is better: An estimate of “roughly 2 weeks” or an estimate of “4.75 days”? Personally I favour accuracy over precision. “4.75” is attractive because it very precise and a smaller number, but “roughly 2 weeks” might be more accurate. And estimating must be accurate to be any use for planning.
Continue reading
Are you dead? A comfortable Agile Project Manager isn’t doing their job
If no one is pissed off with you then you are dead but just haven’t figured it out yet!
Tom Peters (2004)
Bucking Bronco: Software Projects that Kick
Leading software development often reminds me of what it must be like to ride a bucking bronco … with the added problem you have to go somewhere at the same time.
Continue reading
Declarative vs Imperative Gherkin Scenarios for Cucumber
Everybody I’ve met that is new to Gherkin starts with an Imperative style of scenarios. The Imperative approach is simple and intuitive and reflects what manual testers do. But I hate the Imperative style with a passion. I favour a Declarative style of scenarios not least because a declarative style means I can test business rules. The UI is prone to change but the business rules tend to be more stable.
Continue reading