The key issue in scaling Agile is ensuring that the correct governance principles are adopted and scaled as the use of Agile evolves. Many organisations use Agile methods successfully on smaller projects, but these start to fail when project size increases or when multiple projects and programmes exist.
This session at the recent Agile Business Conference discussed IndigoBlue’s tried and tested approach to Agile governance: ADAPT and CONTROL. My presentation slides are now available below.
IndigoBlue works in close partnership with clients, blending our experience gained in the im
ADAPT and CONTROLThe governance framework or agile governance model is used in conjunction with a standard Agile processes, such as Scrum. They work in two specific ways:
There’s quite a lot of change in the air at the moment - and not just in terms of the weather. We’re currently putting the finishing touches to our new website and are very pleased with the content, layout, and functionality we’ve been able to include.
Agile Training for Self-SufficiencyTraining is a key element in the development of skills within any Agile transition. However, training is not the answer alone. Our approach is to build experience through support for hands-on project work. This means that a wide range of your staff are involved at a deep level and will result in your having a more comprehensive understanding of the process and its objectives and values than if training courses alone were used.
Agile Development - An Integrated ApproachIndigoBlue is not a software house. However, our consultants have the necessary skills and proven experience to create and manage a team to successfully manage and deliver your project.
Around this time of year, some of the members of our team always seem to find themselves involved in that most seasonally-topical (ahem) of activities - planning what they’ll be doing on Christmas Day. One of us, in particular, has decided that this kind of thing is about as Agile as anything can get in everyday life, as it’s all about adapting to changing circumstances.
We were asked again recently about the idea behind incremental delivery, so here’s another explanation:
It’s one of the fundamentals of Agile that it should feature incremental delivery of the stages of the overall project. In some cases - particularly with Scrum - the increments are time-limited and are known as “Sprints”. In all cases, though, there is a build up of deliverables on an ongoing basis, rather than having everything delivered together at the deadline date.
One of our team here is a keen golfer, but has restricted himself to only playing in fair weather up until this year, when he experienced his first round of golf in the rain. Here's what he said about it:
"Being the Agile geek that I am, I couldn't help but assess the prospects for my round of golf based on the weather forecast, and plan in an Agile manner accordingly. In fact, golf is a pretty Agile pastime anyway - in both senses of the word! - as there is certainly a lot of incremental delivery involved in getting a ball from the tee to the hole.
DSDM stands for Dynamic Systems Development Method. It is one of the earliest forms of Agile to be developed, and in common with other Agile methodologies, it was originally designed to assist people in the development of software.
The method is incremental and iterative - obviously for an Agile methodology - and emphasises continuous user involvement in the process. There are generally 3 phases of a project in the DSDM methodology - pre-project, project life-cycle, and post-project.