My views only, mostly techie stuff.

Implementing and Agile Workflow – Reasoning

By Francisco | 2nd December 2014 | 0 Comment


This is the second iteration of my Agile Workflow programme series of articles.

Evidence shows that iterative and evolutionary development correlates with lower risk, higher productivity and the lowest defect rate. Alternatively, predictive project approaches have been shown to incur increased costs and delays as the projects duration and complexity increase.

Therefore the following projects have been developed iteratively:

  • USA Space Shuttle fight control software
  • IBM Federal systems
  • Canadian air traffic control system
  • Google uses Scrum* on their largest distributed projects e.g. adWords
  • Yahoo uses Scrum*

*Scrum is an Agile method or a subset of the Agile framework.

A more relevant reason to UK market is some of your clients may already be looking for it. Tesco is using Agile internally to build their internal product and services.

The diagram below illustrates how both approaches to project management (traditional and Agile) handle their key project constrains.



  1. Embrace change – The Agile methodology allows for changes to the overall scope folowing initial planning. Changes are expected and embraced.
  2. Focus on delivery – Flexibility with changing the scope means it’s easier to add features that ensure the project keeps up-to-date with the latest developments and business requirements.
  3. Embrace communication and feedback – Enables client feedback throughout the build to ensure the end product meets the clients business needs.
  4. Fail earlier, fail often – The testing is integrated in the development cycle and done as part of each iteration, ensuring bugs are caught and taken care of.
  5. Deliver on time – Because the products are tested so thoroughly with Agile, the product can be launched at the end of any cycle. As a result, the product is more likely to meet its launch date on time


  1. Without a clear goal for each iteration, there is a risk the project could become a series of empty sprints where no clear value is delivered at the end of each iteration.
  2. Without a detailed upfront project plan and sufficient stakeholders involvement the final product can be grossly different to what was initially intended.
  3. Lacks of upfront solution design documentation.
  4. The team can deliver a solution faster than the organisation can consume it.


Leave a Reply

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