Timeline for When estimating with a fresh team on a new project, is there a reason not to use default velocity for estimating?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 27, 2015 at 11:50 | vote | accept | hawkeye | ||
| Aug 27, 2015 at 7:11 | answer | added | teclis | timeline score: 0 | |
| S Aug 27, 2015 at 6:22 | history | suggested | Dennis Christian | CC BY-SA 3.0 | corrected spelling in title |
| Aug 27, 2015 at 5:55 | review | Suggested edits | |||
| S Aug 27, 2015 at 6:22 | |||||
| Aug 26, 2015 at 19:45 | history | edited | Ixrec | Removed new tags; [estimation] only has ~130 questions so no need to give it more subtags | |
| Aug 25, 2015 at 14:13 | answer | added | Evgeni | timeline score: 1 | |
| Aug 25, 2015 at 12:16 | comment | added | Doc Brown | Wrong question. Better ask: is there any reason to believe any estimation you make (by whatever methodology) will be accurate? | |
| Aug 25, 2015 at 11:38 | comment | added | Thomas Owens♦ | What is your "default velocity"? How are you generating this? For the first sprint, you do need to pull some number of story points into the sprint. However, you don't know what that number is until after your first sprint is finished (and it will likely vary for the first few sprints before settling to some roughly consistent value, ideally). Does this question on how many story points to bring into the first sprint help you at all? | |
| Aug 25, 2015 at 10:54 | answer | added | gbjbaanb | timeline score: 2 | |
| Aug 25, 2015 at 10:49 | history | asked | hawkeye | CC BY-SA 3.0 |