Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Oktokolo39647dIf that feature will save lives, you really better work the weekend.
But if not, you could also just continue the rewrite in the next sprint. Sprints are timed for the feature as it was specified at the start of sprint. When the specification changes, the timing might change too.
r3nrut16846dNo sunk cost in Agile, friend. Fail fast and keep moving forward.
VaderNT168446d> I guess I’m working this weekend
It sounds like the story has changed so much that it requires comprehensive rework. That means it's not the same story any more.
What you do is you close the current story. It's done. Not *finished*, just done. Write a new story with the new business flow and the new AC. Groom and estimate it as usual and add it to the next sprint.
Your PO made a mistake with the business flow. Bad, but that's life. That does *not* constitute an emergency on your end. Don't feel pressured to compensate or take a false sense of pride in "getting things done". The world will keep spinning regardless if this story gets finished in two days or not.