User Avatar

I make Software Engineering fun and easy using visuals. 20+ years of experience in building large-scale software systems.

“Agile” vs being agile
Rajat Mishra
  • The agile software development movement over the last two decades is a massive positive change over software development processes followed earlier.

  • But now that "Agile" is the default process to develop software, in most organizations it has degraded to the point of being agile in name only:

    • Excessive focus on Tools to manage agile processes

    • Too many and too long planning meetings

    • Too much of internal documentation

    • Weaponization of retrospectives and metrics like Velocity

  • However, being agile is simple: relentlessly focus on the timeless agile principles as listed in the Manifesto and ignore the noise of heavyweight frameworks and tools sold by consultants and tools vendors:

    • Individuals and Interactions over processes and tools

    • Working software over comprehensive documentation

    • Customer collaboration over contract negotiation

    • Responding to change over following the plan

See more at: https://agilemanifesto.org/