Skip to main content

The sophistication of simplicity

One of the great observations of agile tools and techniques that was made by a stakeholder during our first Agile pilot project a couple of years ago, was how refreshing it was to use simple child-like notions such as hand-written coloured cards and marker pens to identify categorise and prioritise work. As I plan out my Agile Australia presentation I find it a much less daunting task now I have it carded up on my wall, I can grab one at a time to work on them, I can see a visual representation of the work I need to get done, and I can mark cards when they are in draft, review or complete.

These simple activities supported by low fidelity tools that can be purchased for dollars from a newsagency, have the benefit of familiarity for new-comers to agile, and also lend themselves to collaboration in the most natural way; anyone can pick up a card and scrawl a few thoughts down to generate a discussion. Even your most experienced agile consultant will not scare a business stakeholder as they demonstrate the ease in which you can write up a card, stick it in a priority order on a wall, or even grab it off and tear it in two if it’s no longer needed.

It’s this demystification of work-that-needs-to-get-done that can be such a powerful enabler when using an agile approach to software and business change.

Banish confusing tools that have training and cost as an entry barrier, and death to weighty ‘enterprise worthy’ document templates.


Benjamin Cain said…
That must be a need of tremendously working strategies because at the end that is what works big time and it has to be moving on according to all the needs so yeah agile consultants are the ones who can move ahead quite sensibly and that is the way for it.

Popular posts from this blog

Business Requirement Documents are just no good and should be abolished from the world of creating software

I had hoped the world could have wholeheartedly rejected Business Requirement documents by now. For too long I’ve seen the repeated scenario of only commencing the creation of a new initiative with a requirements document.Unfortunately most organisations that have teams developing software still use these flawed anathemas to creativity as the status quo. Despite agile approaches maturing and customer-centric modes of design emerging, requirements documents still persist. 
If you work in an organisation that doesn’t use business requirement documents any more, read no further. You are lucky; sense has prevailed at your place however in my experience, you are still the minority.
Let's face it; addressing this issue is not always the point you want to start your improvement work when there's much that could be dysfunctional with how a team is delivering software. But now, I find myself as mad as hell, and I'm not going to take business requirement documents anymore. I want to …

Gamify your children

Inspired by James Ross’s LAST conference talk on The Shamification of Lamification and the Reclaimification of Gamification I was motivated to try and “Gamify” the school holidays for my three children, Leo aged 8, Chloe 9 and Max 10.
Buy-in is everything, so the first thing we did was a quick workshop to extract the kids ideas. I asked them to write their ideas for good rewards on sticky notes, with a few examples for context, such as ‘trip to the movies or ‘play date with a friend’ . They had 5 minutes to come up with their ideas – one idea per sticky note (as always).
They then read out their ideas for all of us to hear, there were a few duplicates and also a few comedy suggestions. Even though we had ruled out crazy stuff, such as rewards of a million dollars, Leo had written down ‘A unicorn for the back yard’ reading it out with gleeful giggles.
Then they spent 5 minutes writing down tasks that they could do to earn rewards. By now they had the hang of it and quickly came up with t…

My take on SAFe - Scaled Agile Framework for the Enterprise

Something I’ve observed recently amongst this agile/lean/start up/digitally disrupted community that I’m in, is there are a lot of‘SAFe haters’ dissing on SAFe out there.
Well I’ve just come from a giant organisation that is actually making a good fist of ‘doing SAFe’, so I feel like I’ve got an experienced based perspective on SAFe which might be of interest to some.
I’ve been chatting to people on this topic, it astonishes me the amount of opinion that is being shared on SAFe. The criticism and the eye rolling and statements about what it is and isn’t. There’s a growing anticipation over how it will be received and perceived at up coming Lean and Agile conferences, the sense of controversy is palpable. I’ve been soul searching over my own recent experiences. Digested into one sentence my opinion is: “SAFe – it ain’t so bad, but it’s not the answer either.”
So, in what ways do I thinkSAFe is good and can help?
Lining up iterations amongst several teams.
I’ve observed and executed a few…