I am very excited about the level of interest in the new series of talks at the BCS on Agile Business Change, and also honoured to have been asked to give the inaugural presentation on the 17th September.
I have always considered myself an engineer at heart. When I did my first degree, many people considered IT as an engineering discipline. I was a strong supporter of this classification and still do agree with it having become a Chartered Engineer many years ago now.
At IndigoBlue we have spent many years developing and refining the ideas that help people understand how and why Agile works. In a recent workshop I was asked how our ideas differ from the Agile Manifesto. It’s been a while since I analysed the manifesto in detail, and I found the process interesting.
As Agile continues to increase in popularity and prominence, I’ve become increasingly alarmed at the number of people who seem to have latched on to the idea of “fail fast” as a justification for avoiding, or not meeting, committed outcomes.
"Fail fast" is a great sound-bite, but it doesn't capture the true intention of Agile. There should be no concept of intentional failure, and certainly not of delivering things that don't work properly. Failure is after all failure, no matter how quickly it happens, learning is the real objective.
The time has come for you to consider who you should be nominating for the Agile Awards for 2013!
IndigoBlue is delighted to be working with Vocalink on the development of their new mobile payments platform Zapp, and we're particularly pleased now that the product is public domain. The project has provided an excellent exemplar of how Agile provides significant competitive advantage in environmments where innovation and uncertainty rein, and our approach has enabled the product development to move ahead at pace whilst providing VocaLink with the confidence to set demanding launch timescales.
After the success of last years’ Memberwise Conference, I’m again delighted to be presenting a keynote at this years’ event, Harnessing the Web 2013. The conference this year will focus on how membership organisations and associations can better harness the web to drive membership value and growth and includes 3 themed break-out seminar streams:
What is a “broken project”? It’s what I describe as a project where the team has less capacity than the simplest solution requires. The word ‘broken’ is strong language but that’s the intention, to shock someone into action.
Recently I had reason to make contact with bit10 a web design and development company I have worked with before, based in Coventry. In the process of catching up with their latest development’s bit10’s Sales Director, Mark McKeever brought to my attention to a recent and prestigious award that bit10 had won for their innovative App for GAME.
In the famous joke, two proud parents watch as their son marches past in an army parade. The mother notices that her son is marching in a different rhythm to the rest of the garrison and exclaims "Ooh look! They're all out of step with our 'arry!"
It was good to read the July Socitm Insight report Agile: a methodology for our time as IndigoBlue was a key contributor to the work behind the report. I had the pleasure of helping two of the local councils covered.Socitm is the membership association for all ICT professionals working in Local Authorities and the Public and Third Sectors and suppliers to those sectors.
The Guardian recently ran an interesting article reporting that the Charity sector is failing to make sufficient investment in technology and therefore failing to take advantage of the opportunities opened up by more effective use of technology. Whilst this is directly linked to the fact that as a sector Charity invests less in IT per headcount than any other, the reasons for this are a lot more fundamental than just not having enough money.
The largest single problem within the majority of Agile implementations we encounter is absence of structured change control. Many of the issues experienced can be traced either to inappropriate change or to resultant confusion because the change is not managed. Senior management suspicion of Agile can invariably be traced to a lack of visibility and control of change.
In recent conversations around governance, I've been challenged to reflect on and refine my own understanding and working definition of the term.
For a long time, my working definition of Governance was something like "Governance is the process of insight and influence for people outside the team". This definition accepts - and builds on - the idea that, in an enterprise adoption of Agile, there are often external stakeholders with authority. But ...