The impression that “our problems are different” is a common disease that afflicts management the world over. They are different, to be sure, but the principles that will help to improve the quality of product and service are universal in nature.-W. Edwards Deming

 

Benefits of Agile Development

  • Shorter idea-to-cash cycle, short release cycles
  • Better quality due to early detection of defects with a continuous testing and validation
  • Even workload on staff by maintaining a constant pace indefinitely
  • Easy to roll back mistakes
  • Decision making at all levels
  • Empowered teams
  • Easier collaboration with customers

 

Manifesto for Agile Software Development

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.

 

Principles behind the Agile Manifesto

  1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
  2. Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
  3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
  4. Business people and developers must work together daily throughout the project.
  5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
  6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
  7. Working software is the primary measure of progress.
  8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
  9. Continuous attention to technical excellence and good design enhances agility.
  10. Simplicity–the art of maximizing the amount of work not done–is essential.
  11. The best architectures, requirements, and designs emerge from self-organizing teams.
  12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

 

Common Agile Pitfalls

  1. Lack of right tools for build, deploy and configure
  2. Lack of structured unit tests
  3. Lacking test automation
  4. Allowing technical debt to build up
  5. Product owner role is not properly filled
  6. Lack of overall project design
  7. Geographically spread out scrum teams
  8. Adding stories to a sprint in progress
  9. Lack of sponsor support
  10. Insufficient training
  11. Teams are not focused
  12. Excessive preparation/planning
  13. Problem-solving in the daily standup
  14. Assigning Tasks
  15. Scrum master as a contributor
  16. Attempting to take on too much in a sprint
  17. Fixed time, resources, scope, and quality

References

Leave a Reply

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