> Next feature, very similar to the other one, 5 story points. But this time you have a button component already, so you can just reuse it. Same points delivered, less time spent, meaning you have time to pick up another story, meaning your velocity goes up.
This makes no sense, nobody works like that. And to be fair, shouldn't.
The next button is a 1 point story because the component is there already. Or not even 1 point, may get buried in a 1 point story to add ten new buttons.
> Scrum does NOT work with deadlines.
No true Scotsman, we're all holding it wrong.
Deadlines will be imposed from afar, in just about every company ever, and then the points will be attempted to be retrofitted to the predetermined plan.
When approximately everyone, for a couple decades now, is always "doing it wrong", it's time to acknowledge that the problem is the idea not the people holding it wrong.
> The rational purpose to sprints is for project management to be able to look ahead and be able to say "we expect this feature to be done in X weeks time"
This is how that goes:
PM: It'd be great if we had all the stories and their points in the place for the next quarter so we can predict good dates, get on that will you?
Eng: Awesome! So I'll need to plan out the work for the quarter, write stories and estimate them. Nice, will do that.
PM: NO! This is agile, don't ever look beyond this sprint. We don't do planning in agile. Just work on your microtask of the sprint, we'll worry about next sprint later.
Eng: Um, wait, what?
You might again say they're doing it wrong. There's no true agile scotsman.
This makes no sense, nobody works like that. And to be fair, shouldn't.
The next button is a 1 point story because the component is there already. Or not even 1 point, may get buried in a 1 point story to add ten new buttons.
> Scrum does NOT work with deadlines.
No true Scotsman, we're all holding it wrong.
Deadlines will be imposed from afar, in just about every company ever, and then the points will be attempted to be retrofitted to the predetermined plan.
When approximately everyone, for a couple decades now, is always "doing it wrong", it's time to acknowledge that the problem is the idea not the people holding it wrong.
> The rational purpose to sprints is for project management to be able to look ahead and be able to say "we expect this feature to be done in X weeks time"
This is how that goes:
PM: It'd be great if we had all the stories and their points in the place for the next quarter so we can predict good dates, get on that will you?
Eng: Awesome! So I'll need to plan out the work for the quarter, write stories and estimate them. Nice, will do that.
PM: NO! This is agile, don't ever look beyond this sprint. We don't do planning in agile. Just work on your microtask of the sprint, we'll worry about next sprint later.
Eng: Um, wait, what?
You might again say they're doing it wrong. There's no true agile scotsman.