Agile Project Management: Avoiding The Waterfall – by Richard Revis

Agile Project Management: Avoiding The Waterfall.This is a guest blog post by Richard Revis from The Plan Is

“Agile project management can be hard to implement successfully because even once you have good practices in place the way projects are run can revert to the old methodology quickly. I would like to share three reasons that I have come across for the reappearance of waterfall project management in an organisation and look at some ways to address this.

The first reason is the sponsor’s view of how a project should operate. A client, internal or external, probably has a mental model in his head of how things will happen when commissioning a project.

  • The project is briefed to the project team.
  • The project team does the work.
  • The sponsor checks the work has been done correctly.

One thing we can notice about this progression is that it looks suspiciously like the key steps from the waterfall process:

  • Requirements
  • Design and implementation
  • Verification

If this is how your sponsor views the world there will be a strong tendency for it to creep into the way the project is managed.

Secondly the business environment can add to the pressure to do single iterations. Most projects occur in an environment with severe constraints. A typical project starts now and ends when the money, or attention, or time runs out. I have worked on several projects where this end date was defined by the last day we could deliver something to avoid being sued.

This kind of time constraint will lead your project sponsor even more towards thinking about their project in a waterfall style as the important requirement (don’t get sued) is very clear. The consequence of such a precise requirement is the belief that it must be possible to work out how to achieve that result and then do it right the first time.

Finally, interaction with the rest of the programme can contribute. Generally your project sponsor will be thinking about more than one strand of work at a time. The part which is handed over to you will be going on in parallel with the work that is being done in marketing or operations or by another team. This naturally will reinforce the tendency to plan in a waterfall style, where each strand is completed and then brought together for iteration.

So how can a project team address this kind of imbalance between the process they wish to operate and the natural inclination of their sponsor or client?

The fact that there will be an underlying waterfall project plan, at least in the mind of your project sponsor, doesn’t mean that you have to throw away your agile practices.

You probably can’t get rid of the waterfall thinking entirely. The constraints and thinking I have mentioned will generally already be set by the time you get involved. However by moving the plan they have in mind up to a high enough level it is still possible for you to implement agile practices underneath.

For the element of the larger project you are working within you can try to pulling your stakeholder in early, delivering small iterations, and changing the specification to closer match the real requirements as you go along.

You will still be aiming to deliver what they want, within the time scales they ask for, just organising it in a slightly different way than they probably expected.

However in order to get this flexibility it is necessary to ensure that project milestones in your sponsors plan are high level and flexible. For example good milestones I have seen are achieve 80% rating on customer feedback, deliver £5,000/day revenue and launch a good product.

Milestones like this offer enough flexibility that another process can iterate underneath working out what the actual definition of ‘a good product’ is and how to best build it.

In summary, if you identify the hidden waterfall project that is going on and work out how to influence it appropriately it won’t necessarily harm your project. In fact knowing about these implicit constraints and deadlines can help you deliver a better result.”

About the Author:
Richard Revis has run technology development projects involving everything from iPhones up to front line fighter jets. He is currently Project Director at The Plan Is where he is developing web applications that make it easier to plan fixed duration projects. He writes regularly on project management and start ups at theplanis.com/blog.

One Response to “Agile Project Management: Avoiding The Waterfall – by Richard Revis”

  1. agile waterfall says:

    The transition from waterfall to agile software development requires careful planning, collaboration and change management. Waterfall and agile are two unique development models used in interactive and software production. It's likely the debate over which is better will continue indefinitely, but in reality, both approaches boast significant but different benefits. It's generally accepted that agile, specifically, lends itself well to software development and large-scale website projects. Although a novice Project Manager may feel more comfortable working with a waterfall approach because each step is predictable, letting go of the familiar may well be worth it to make the move to an agile model. The collaboration and flexibility that agile brings can result in a better end product for your client, and a more engaged, harmonious internal team.

Leave a Reply

What is 9 + 8 ?
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...”

PETER SILVA-JANKOWSKI
IPC MEDIA

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

LUKE SHARKEY /STRATEGY & IMPLEMENTATION LEADER
SUNCORP

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

GILES BENTLEY, DEVELOPMENT & OPERATIONS DIRECTOR
TIME INC

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

DAN PULHAM, DIGITAL DIRECTOR
TELSTRA

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

GINA MILLARD
GLASS'S INFORMATION SERVICES

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

ANDY JEFFRIES/TECHNICAL LEAD
IPC MEDIA

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

HANNAH JOYCE
GLASS'S INFORMATION SERVICES

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

BRUCE WEIR/EGM
SUNCORP

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

BEATRIZ MONTOYA/CONSUMER MARKETING DIRECTOR
IPC MEDIA

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

PETER THATCHER, SENIOR ACCOUNT DIRECTOR
ThoughtWorks

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

JULIE PEEL
GLASS'S INFORMATION SERVICES