Friday, October 19, 2018

Agile Makes Work Faster

Agile Software Development is an approach to software development under which requirements and solutions evolve through the collaborative effort of self-organizing and cross-functional teams and their customer(s)/end user(s).

  • Individuals and Interactions over processes and tools
  • Working Software over comprehensive documentation
  • Customer Collaboration over contract negotiation
  • Responding to Change over following a plan

  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 primary 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

Studies shows that agile projects can be faster. Janet Gregory, authors of agile testing made a bold statement that “agile means faster” is just a myth. But Matthew Heusser stated that, “comparing an agile team that can't get something done in a year to a more traditional team that can is a false comparison. In a year, the traditional team will have 12-and-a-half requirements done, a mess on the floor and nothing to ship”.

There are four reasons to make Agile projects can slow down. They are:
  1. The wrong people: Remove people from the team who aren’t following good engineering discipline or are making things more complex.
  2. Putting the process first: Establish open communication and self-organizing and empowered teams.
  3. Using the wrong technologies: give teams authority to make technology decisions, and allow technology choices to be reversed if they hinder delivery.
  4. Making the architecture too complex: Keep your software as simple as possible, refactor.

Do you want to talk to us?

Connect with us

We are open to talking about any requirements that you have. Send us a message!


No: 18, Jai Nagar 2nd Street, Valasaravakkam, Chennai - 600087

Work Time:

Monday - Friday from 9am to 7pm