Agile Project Management...Is Your Software Outsourcer / BPO Firm Using It ?....

One problem I frequently run into when discussing project guidelines for outsourced software development  is that most of the clients  are well familiar with Gantt charts or Waterfall charts. As such they prefer to look at the project guidelines, timelines and milestones based upon those  charts.

Nothing wrong with that of course...but the software development world has moved on and at least the better companies are now mostly using an Agile Software Development set of principles. The concept of an Agile environment is that it is much more "free flowing" and not bound to the traditional milestones and tightly defined guidelines which are being used in a Non-Agile environment.

The challenge is how to provide the accountability to the client  (the ones who pay the bill) while harvesting the advantages the Agile environment can deliver.

The Agile Development environment is based upon the following 12 principles:


  1. Customer satisfaction by early and continuous delivery of valuable software
  2. Welcome changing requirements, even in late development
  3. Working software is delivered frequently (weeks rather than months)
  4. Close, daily cooperation between business people and developers
  5. Projects are built around motivated individuals, who should be trusted
  6. Face-to-face conversation is the best form of communication (co-location)
  7. Working software is the principal measure of progress
  8. Sustainable development, able to maintain a constant pace
  9. Continuous attention to technical excellence and good design
  10. Simplicity—the art of maximizing the amount of work not done—is essential
  11. Best architectures, requirements, and designs emerge from self-organizing teams
  12. Regularly, the team reflects on how to become more effective, and adjusts accordingly



A practical problem of an Agile development is that there are really no Milestones the teams are working towards. As such there is no firm date which can be given so that the customer can review a an interim work product (milestone).   


A practical solution to this dilemma (and one we use internally) is to still provide Gantt charts but use an  Agile environment in House.  The process has to be of course managed properly...but if done well it is entirely  possible to utilize an Agile environment while also providing the form and accountability the client is looking for.  

A great article which goes into details as to the way an Agile Development Environment works can be found below.