Comment by bunderbunder

Comment by bunderbunder 4 days ago

It seems industry-wide these days.

What I’ve seen as an older-than-average developer is that the Agile movement has made it increasingly difficult to make time for paying attention to some of the more subtle aspects of user experience such as performance. Because I can’t predict how much work it will be accurately enough to assign story points to the task, and that means that this kind of work frequently results in a black spot on our team performance metrics.

CD makes it even harder because this kind of work really does need some time to bake. Fast iterations don’t leave much time to verify that performance-oriented changes have the intended effect and no adverse side effects prior to release.

2muchcoffeeman 4 days ago

That’s not agile’s fault. That’s the orgs fault.

We used to have a few days set aside regularly to fix things that would never get prioritised.

Reply View 1 reply

bunderbunder 3 days ago

I think this is another of those spots where the difference between agile with a little an and Agile with a big À comes to the forefront.
Little a agile is about pushing back against dysfunctional business dynamics for the sake of humanistic goals like employees’ mental health and doing right by customers.
Big À Agile co-opts that, and is more about squeezing as much money out of everyone as possible while wearing the trappings of agile values to make it seem more palatable.

Reply View | 0 replies