Agile Development Cycle

This content is syndicated from by Kelly Waters. To view the original post in full, click here.

Although agile development methods have been around for a little while now, many people still ask about the agile development cycle, what it is and how exactly it's different to a more traditional approach to development projects.  Here is a simple explanation of the basics for people new to all this.

Traditional software development projects follow what is commonly known as a waterfall approach, where each phase of the software development life cycle is completed in detail and in sequence, one stage at a time.  Simplistically a traditional software development life cycle might look something like this...

'Waterfall' Software Development Life Cycle (SDLC)

waterfall software development life cycle (SDLC)

Each phase is completed in turn, for instance:

  • Detailed Planning

  • Detailed Analysis

  • Detailed Design

  • Development

  • Testing

  • Release

  • Maintenance

With waterfall projects, the whole project is analysed, then designed, then developed, then tested, and then deployed.  Sometimes projects are cut into multiple smaller phases to make them more manageable, but still these phases tend to work roughly sequentially like above and tend to still be quite large, for instance 3-6 months or maybe even more.

Agile Development Cycle

An agile development cycle is different.  Instead, the initial planning and analysis is kept to a very high level, just enough to outline the scope of the development project.  Then the team go through a series of iterations, analysing, designing, developing and testing each feature in turn within the iterations.

For instance, it might look a bit more like this:

agile development cycle

There aren't really any distinct stages during the development.  Instead, each feature is taken from start to finish within an iteration, with the software being released at the end of each iteration, or if appropriate even during an iteration.

An iteration is simply a fixed, short period of time that the team chooses to work within.  Typically for agile teams, an iteration is between 1 week and 30 days.  Strictly speaking, the Scrum agile development methodology advocates 30 days, but I've encountered very few teams that actually do this.  2 or 3 weeks seems to be more common.  The Extreme Programming agile methodology advocates 1 week.  This is very short and in my experience requires quite a lot of maturity in the team and its processes to achieve, because getting to a stable release every week can be difficult.

Either way, the principles are the same.  The idea is to stick to short, fixed-length iterations and complete all stages of the development cycle for each feature in turn within an iteration.

The key difference this creates is visibility of complete working features much earlier in the project life cycle, allowing for a better gauge of progress and quality, and allowing for feedback and adaption along the way.  The result is to see some results earlier, mitigate risk, and to allow flexibility to accommodate change.

One of the dangers of a waterfall approach is that by the time the detailed up-front planning, analysis and design are done, let alone by the time the solution is developed and tested, many requirements may have changed - especially these days when the pace of change is so incredibly fast.  Agile mitigates this risk too, helping to ensure that the right solution is delivered.


Leave a Reply

Your email address will not be published. Required fields are marked *

nine + 20 =

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

What People Say

“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.”


“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 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 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...”


“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 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 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. ”


“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 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 was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“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.”



To explore how we can help you, please get in touch