Hacker News new | past | comments | ask | show | jobs | submit login

A big issue is the speed at which teams are expected to deliver. If every sprint is expected to deliver value to the user, there is isn’t enough slack in the system to go back and prune the code to remove cruft. People end up cutting corners to meet deadlines set by management. The corners that get cut are the things that are invisible in the demo. Security, documentation, and all the chewing gum holding it all together.





This is why cruft removal is linked to the value delivered to the user

You do not say : "there is two task: add some feature, takes 1 day, and delete some cruft, takes 1 day".

You say: "Yes, that feature. That's one task. It will take 2 days."


And once a level of "story points" is achieved within a Sprint you can't go backwards and you can't deliver less value to the Customer. There is no room for re-evaluation. Forwards, moar!

As per Tame Impala's Elephant:

He pulled the mirrors off his Cadillac

Because he doesn't like it looking like he looks back

Looking back gives the impression of missteps or regret. We have no such thing!


Scrum points are about engineering controllability, rather than performance. But that's a complexity most don't get.

Exactly

And because it is based on nothing, you can just lie about it




Consider applying for YC's Summer 2025 batch! Applications are open till May 13

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: