Timeline for Sizing tickets Approriately in Scrum
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 1, 2017 at 16:18 | vote | accept | Chris | ||
| Jan 31, 2017 at 3:42 | answer | added | Bryan Oakley | timeline score: 1 | |
| Jan 31, 2017 at 3:26 | comment | added | Bryan Oakley | @Chris: I don't know if it has anything to do with demoralization or not. Why are they demoralized? Scrum should be simple: if you overcommit, just bring fewer stories into the next sprint. The sizes are all relative and shouldn't be related to the amount of time it takes to complete a story. Pick and "average" story, and then size everything relative to it. Do you think it's about the same amount of work" Same number. Definitely less work, it's a smaller number. Definitely more? It's a bigger number. | |
| Jan 31, 2017 at 3:15 | comment | added | Chris | @BryanOakley, interesting, so maybe the problem is less with our process and more with the team getting demoralized. | |
| Jan 31, 2017 at 2:12 | comment | added | RubberDuck | Related: pm.stackexchange.com/q/20239/21039 | |
| Jan 30, 2017 at 23:51 | comment | added | Bryan Oakley | If you have a developer who spreads a story out to fill an entire sprint, you have bigger problems than sizing stories. That person is not a team player. | |
| Jan 30, 2017 at 23:07 | history | tweeted | twitter.com/StackSoftEng/status/826205177598337024 | ||
| Jan 30, 2017 at 21:11 | answer | added | John Wu | timeline score: 1 | |
| Jan 30, 2017 at 15:25 | answer | added | Cormac Mulhall | timeline score: 8 | |
| Jan 30, 2017 at 15:13 | comment | added | Robbie Dee | Points are merely there to show the relative effort of one ticket against another. If you're automatically equating points with time, then that is comparing apples and oranges with the inevitable results as you've seen. | |
| Jan 30, 2017 at 14:42 | history | asked | Chris | CC BY-SA 3.0 |