Timeline for Is a large increase in velocity realistic in a Scrum environment?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 20, 2018 at 19:30 | comment | added | Curtis Reed | "your estimate already assumes you are going as fast as you can while doing everything correctly" This is probably an incorrect assumption. We can always continue to improve and optimize. Teams should never assume that their stable velocity indicates that they can't get any better. But they need to look at their entire process systematically and look for minor process improvements. | |
| Jun 6, 2017 at 14:37 | comment | added | Chris Pratt | That's exactly the solution I tell people. Since story points are relative units anyways, if your manager wants more, just multiply what you used to use by two. Suddenly your velocity jumps from 50 to 100. Yay! We're twice as productive now. Of course, this is ridiculous. Velocity should be a measure of what the team can do reasonably within any given sprint over time. If you're trying to force them to move faster, you're going to burn them out and hurt velocity later down the line. | |
| Sep 18, 2013 at 14:15 | comment | added | KeithS | axosoft.com/blog/wp-content/uploads/2012/08/… | |
| Sep 17, 2013 at 22:26 | comment | added | pablosaraiva | And if you agree and really increase the velocity by 40%, it will look like to others that you and your team were not working at your best. The professional way to handle it is give a straight answer: "No, can't do.". Another book reference about it: "The Clean Coder" by Robert C. Martin. | |
| Sep 17, 2013 at 17:18 | vote | accept | P2l | ||
| Sep 16, 2013 at 21:41 | comment | added | psr | @Paul - I thought it was good. But the advice in it can mostly only be followed by managers, and the ones that could benefit from it probably won't read it. Nor will reading it necessarily change behavior. | |
| Sep 16, 2013 at 20:45 | comment | added | Doc Brown | I strongly believe that there is no "quick and dirty". "Dirty" always makes me slow - even in short term. | |
| Sep 16, 2013 at 19:21 | comment | added | BЈовић | I have seen people creating mess for years, but they only added new things (never change previous), until one day their performance dropped when they had to change some features :) | |
| Sep 16, 2013 at 18:31 | history | answered | psr | CC BY-SA 3.0 |
