NoEstimates Data [public data set]
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
$
%
123
 
 
 
 
 
 
 
 
 
ABCDEFGHIJKLMNOPQRSTUVW
1
ProjectTeam ConfigurationContextDomainStory DefinitionTechnical Story DefinitionStartedDefinition of DoneCorrelationContactNotes
2
A5 TW devs, 3 non-TW devs, 1 non-TW architect, 1 TW BA, 1 non-TW BA, 1 non-TW tester (yes, tester not QA), 2 client POs (tech, biz)overall quite young team, both in the experience with the technology and 4 devs rotated in/added to the team Integration of an online service booking tool into the [automotive company] Owner Site called My[automotive company] Work item that includes everything from front-end, business logic and stubbed version of 3rd party service or actual integrationWork item that is either changing a technical implementation detail or in our specific case the actual integration with the third party API Development has started. This happend for those stories after the initial story draft by the BAs/POs has been refined in 2-3 rounds of refinement with the entire teamPOs signed off on the story. All of those stories are supposed to go to production in one big batch0.59Felix
3
B0.42Mike
4
C0.10Cliff
5
DB2B RetailQA complete0.74Sudeep
6
E3x dev pairs + Tech Lead + 1 client developer, BA, UX and PO (2 of the devs are non-TWers and contractors who recently joined)The company is so-called start up but it is more of a scale up. Very siloed - has platform (backedn) team, QA team, Devops team, and us..."front-end" team. We kicked off a new piece of work 6 weeks ago and are now also doing some backedn + frontend and have one developer from the "backend" team embedded in ours.Company in the Mobility sector B2B/B2B2C We don't separate bugs, user stories, technical stories as they are all pieces of work that need doing.When the story moved to 'In Dev' and was kicked offWhen the story moves to 'QA'0.45AdrianaWe don't do grooming or estimation sessions. When we split stories we try to make them equal pieces of work and we have estimated 3 days on average for a story to be In Dev.

If there is a story that we anticipate will be bigger than the others and cannot be split (doesn't make sense to be), we mark it with 1-3 red dots which means it will take more effort/time to be done.
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
Loading...