3 ms·
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 sy
by al_borland 2y ago
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.
- BLKNSLVR 2y agoAnd 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!
- chading 2y agoScrum points are about engineering controllability, rather than performance. But that's a complexity most don't get.
- deleted 2y ago[deleted]
- JackSlateur 2y agoExactly And because it is based on nothing, you can just lie about it
- JackSlateur 2y agoThis 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."