Timeline for Scrum task estimation methodologies
Current License: CC BY-SA 4.0
8 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jun 9, 2019 at 19:37 | comment | added | Erik | What's your role in this team? You say you need to assign things and organize the team's work, which is generally something the team is supposed to do themselves. Are you a member of the team? | |
Jun 9, 2019 at 6:47 | history | edited | embedc | CC BY-SA 4.0 |
added 572 characters in body
|
Jun 8, 2019 at 9:52 | history | edited | embedc | CC BY-SA 4.0 |
deleted 196 characters in body
|
Jun 7, 2019 at 20:34 | comment | added | Todd A. Jacobs♦ | How have you determined that the estimates don't track to some reasonable confidence interval? Without more context, calling team estimates "random" sounds more like a rant than an objective observation. What's your supporting data? | |
Jun 7, 2019 at 15:53 | comment | added | embedc | I don't mean that the estimations are true random numbers, but as a developer I understand that the task analysis was superficial. | |
Jun 6, 2019 at 22:41 | answer | added | Mar | timeline score: 3 | |
Jun 6, 2019 at 20:40 | comment | added | Daniel | When you say random do you mean actually random (like they picked numbers at random, as good as a die roll and put those down) or do you mean something else (I would interpret the different actions very differently). Also, what leads you to believe that they are random? What is your role on the team and were you involved in estimation? | |
Jun 6, 2019 at 18:58 | history | asked | embedc | CC BY-SA 4.0 |