Agile Principle 5: How Do You Eat An Elephant?

How do you eat an elephant? One bite at a time!

Likewise, agile development projects are delivered in small bite-sized pieces, delivering small, incremental *releases* and iterating.

In more traditional software development projects, the (simplified) lifecycle is Analyse, Develop, Test – first gathering all known requirements for the whole product, then developing all elements of the software, then testing that the entire product is fit for release.
In agile software development, the cycle is Analyse, Develop, Test; Analyse, Develop, Test; and so on… doing each step for each feature, one feature at a time.

Advantages of this iterative approach to software development include:

  • Reduced risk: clear visibility of what’s completed to date throughout a project
  • Increased value: delivering some benefits early; being able to release the product whenever it’s deemed good enough, rather than having to wait for all intended features to be ready
  • More flexibility/agility: can choose to change direction or adapt the next iterations based on actually seeing and using the software
  • Better cost management: if, like all-too-many software development projects, you run over budget, some value can still be realised; you don’t have to scrap the whole thing if you run short of funds

For this approach to be practical, each feature must be fully developed, to the extent that it’s ready to be shipped, before moving on.

Another practicality is to make sure features are developed in *priority* order, not necessarily in a logical order by function. Otherwise you could run out of time, having built some of the less important features – as in agile software development, the timescales are fixed.

Building the features of the software ”broad but shallow” is also advisable for the same reason. Only when you’ve completed all your must-have features, move on to the should-haves, and only then move on to the could-haves. Otherwise you can get into a situation where your earlier features are functionally rich, whereas later features of the software are increasingly less sophisticated as time runs out.

Try to keep your product backlog or feature list expressed in terms of use cases, user stories, or features – not technical tasks. Ideally each item on the list should always be something of value to the user, and always deliverables rather than activities so you can ‘kick the tyres’ and judge their completeness, quality and readiness for release.

These are important characteristics of iterative, feature-driven development – and they’re essential if you plan to deliver in fixed timescales – one of the 10 key principles of agile software development.


7 Responses to “Agile Principle 5: How Do You Eat An Elephant?”

  1. Mike says:

    Hi Kelly. I posted a link from my blog to yours. Thanks for the information.

  2. Anonymous says:

    Very nice and succinct. I will borrow some language for a presentation I need to give!

  3. srutanjay says:

    Well, when changes happen over a small discussion or verbally it is important that those are tracked. how are the changes documented. At the end of the day it is important to track the requirements, though it may keep changing.

  4. Kelly Waters says:

    Hi srutanjay

    You say “it’s important to track the requirements” – why is that?


  5. srutanjay says:

    Hi kelly,

    First, when requirements keep getting modified due to iterative method of development, one may need to see how the final requirement has shaped up as compared to the initial one.

    Secondly, as time and cost are fixed, some of the requirements may be differred for a later release.


  6. Kelly Waters says:

    Hi srutanjay

    Re your first point, I have worked in development for many years and the only reason I’ve ever had to do this is to argue with people about why we’re late. In agile development, the key stakeholders (especially the product owner) should have been involved throughout, so this risk is mitigated. In my experience of agile, I don’t think I’ve seen this need once as a result.

    If any requirements are defered for a later release, they can simply be captured on the product backlog and a new user story written nearer the time of development.

    It’s a very interesting point though. Has anyone else got a view on this?


  7. Mielczarek says:

    Srutanjay: What do you mean with the requirements being different for a later release?

Leave a Reply

What is 2 + 10 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)

There are 101 ways to approach anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”


“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”


“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”