Example of Day to Day Governance on an Agile Programme

You’d think I couldn’t win. Senior corporate managers are nervous that I am doing unconventional agile stuff, without those reassuring Gantt charts or status reports and hardly any formal minutes. Agilists are horrified that I advocate Agile Governance.

This conflict isn’t impossible it is just one of many places where I can demonstrate that Agile practices aid traditional processes/goals. In this case programme/project governance. I start from the position that governance is not contrary to Agile, it is built in. Rather than less governance my Agile programme actually has more governance than is the norm and is is safer as a consequence. Given this position is fairly controversial I thought I’d explain how I go about governance at the moment. I’ll give you a clue – there is a lot of talking.
Continue reading

Another kicking from stakeholders? Not when dispassionate and positive

“Well, we just got another kicking”. A group of us, representing technology, had just attended the regular programme board meeting with the business types. In the debrief afterwards the technology folk around me were despondent. In fact they were despondent every month after this meeting. They genuinely felt kicked. But I didn’t. I never did. It was almost like I experienced a completely different meeting to that experienced by my colleagues.
Continue reading

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

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