Skip to main content

Agile Australia 2011 Series - Skunkworks budget

This is a teaser topic to tell you that some things will be easier if you get some budgetary discretion. You can then try some neat agile stuff like tackling some technical debt, training some of your allies in Agile or sending them on courses or to conferences. You might find your skunks budget is in fact your training budget. Perhaps your IT team work on a utilisation rate that means that you have some discretion to work on personal interest projects or self development; can you harness it with some like minded folk who want to try agile?

If you have formed your agile interest group, can you gather them together for some extra-curricular work and try some new practices, TDD or continuous integration for example?

You could shell out and start agile on your own home grown project by investing $25.82 on system cards, sharpie permanent markers and Blu Tack. Who in your department will wander over to your card wall and start asking questions about what you are trying?

In my experience workers taking initiative to try something new and innovative for their company will be encouraged for their efforts, particularly if you’ve ‘skunked’ the money out of nowhere and can demonstrate some value in return.

If you feel frustrated that you want to try some new things for your Agile Transformation but you have no cash at all, use that frustration to ask yourself, how can I find some budget to do this that will make it a no-brainer for my boss to agree to it?


Anonymous said…
They are surely the ones who knows the meaning of productivity and because of that their Agility is having an impact overall because at the end learning and growing is the first gaining agile consulting companies are working impressively which can lead it to the betterment.

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…

Agile Australia 2011 Series - Agile Governance

If you are in an industry that is heavily into governance you need some structure and process around your projects or you could find your Agile projects getting usurped by the culture of command and control. So it’s important not to shy away from the topic but to work with the entities that enforce and monitor governance. In this way you can create something that is fast and easy and not laborious to work with.I work for an Apra regulated organisation and we made keenly aware of our obligation under Apra to evidence documented change when audited. However in all organisations I’ve ever worked in, there are boundaries that bend quite a bit, ways to change things and ways to get by that satisfy governance process without crippling your agile process.There’s almost two alternating schools of thought here which are ‘work within process’ and ‘decide to change the process’. It’s actually pretty easy for my team to work within process. Project approvals, mandates and PIDs that are important …