Agile Status Report for Executives: Best, Worst, Throughput

My programme’s Sponsoring Group asked me to send a weekly status report. This was to compensate for the fact they were at a remote site and hence couldn’t see the walls of our informative workspace. They were paying the bills so who was I to argue.

Luckily they don’t want a lot of detail. They want to know three things:

  • Throughput
  • Best thing this week
  • Worst thing this week

Continue reading

Agile Project Manager as Shepherd

I value project managers and see an on-going need for them within a Lean-Agile context. Admittedly the role of the project manager changes when using an Lean-Agile approach, becoming more of a shepherd and less a military officer. In this, the first post of a new series, I thought I’d revisit my definition of the Agile Project Manager.
Continue reading

How to spot a Product Owner’s Pet Requirements

Everybody has pet requirements and product owners, being human, are no different. Unfortunately pet requirements are a real risk to software projects. We should all resist these pet requirements and do everything possible to kill them off ASAP and avoid building them. So how do you spot pet requirements
Continue reading

Is Kanban Turning Developers into Mindless Automata? Not necessarily

David shambles up to the Kanban board. He moves a card from “Dev In Progress” to “Dev Done”. No emotion cracks his blank facade. There is no celebration of a job well done. No acknowledgement from others in the room. David glances briefly to his left and then pulls another card from “Ready for Dev” into “Dev In Progress” before shambling back to this desk. Another burst of coding begins. This little scene has occurred four times already this week, 19 times this month, and 271 times since David joined the project 15 months earlier. Is David just a machine in the Lean-Agile software factory? A mindless development automaton?
Continue reading

Who is Specification by Example for? Everybody!

I was talking to Pedro Santos on the train the other day. Pedro is my technical lead, an expert in his field and a keen advocate of automated testing and software craftsmanship in general. We were talking about Gherkin and Pedro was saying he doesn’t see Gherkin tests adding value because it doesn’t help him as a developer. Of course I disagree. The way I look at it is the Gherkin tests are not for the developers. The Gherkin tests are for the organisation – they are for everybody.
Continue reading

Solution Convergence: Marrying Business, User Experience and Technical Input

My product owner was upset when I told her she couldn’t have the widget that she had agreed with the User Experience (UX) Designer. The problem was the design was not technically feasible. To get a great solution to meet the business requirements three parties – business, user experience and technical – must agree on the approach. That negotiation is what I call “Solution Convergence”.
Continue reading