Agile was intended to address the problem of waterfall software development: delivering the wrong thing too late.
When "Agile" teams only want to code something once – no acceptance that usability testing might reveal a failing that necessitates another iteration – it's just more waterfall development with Agile-flavoured rituals and ceremonies.
I've recently seen a KPI used called "First Time Right" to measure the ratio of dev tickets needing re-work, as if that is inheritly a bad thing.
Born of good intentions, I'm sure, but given the trends of that KPI, it wasn't helping.
What DID help was to connect the users and devs so they could talk to one another and gain a shared understanding of what problem needed to be solved. It is disheartening to see how we STILL struggle with basic issues like this.
Add comment