3 ms·
But the term "sustainable pace" is also mentioned a lot in the literature. An increase in velocity does NOT mean "work harder"; an increase in velocity should
by Cthulhu_ 3y ago
But the term "sustainable pace" is also mentioned a lot in the literature.
An increase in velocity does NOT mean "work harder"; an increase in velocity should come natural as your codebase expands, you get more reusable components, your team gains experience, etc.
Example. New feature, estimated at 5 story points. One part is a button, takes you half a day to build it.
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.
Nobody, least of all proponents of scrum / agile methodologies, is saying that you should work harder, do a death march, etc. It acknowledges that software development is an infinite and long term process.
Scrum does NOT work with deadlines. It works with predictability; your team's average velocity and the story points of upcoming stories are known, it's then up to the product owner to set priorities if they need a feature live at a certain point in time. Missed deadlines then become bad planning and prioritization more than employees not working fast enough.
> There is not rational purpose to this.
Just to highlight this: 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". It doesn't mean that a 4 day task should be done in 2 weeks. A sprint is just a unit of time, it isn't a promise.
- sirwhinesalot 3y ago> 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 absolutely no sense to me and it is not how we do things at work. When the second task is estimated it will get a story point count of 1 because it's just copy pasting a button, not 5 which requires implementing a button from scratch.
- 9659 3y ago"an increase in velocity should come natural as your codebase expands" you may not respect academic software engineering, but if this is true you have just created a perpetual motion machine. changing / adding software to a system becomes more expensive (takes more time) as the size of the system increases. and it is not linear.
- jjav 3y ago> 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.