StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18522769
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-08-29T23:52:30.910
FavoriteCount
0
LastActivityDate
2013-08-29T23:52:30.910
LastEditDate
LastEditorUserId
0
OwnerUserId
599240
ParentId
18505900
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
<blockquote> Generally, how does SCRUM address estimation accuracy as a whole? </blockquote> By adjusting on-the-fly. You assign story points as a measure of size and complexity. You try your level best to assign points on a like-for-like basis between tasks of comparable size and complexity. You inevitably get it wrong for the first few sprints. As time goes on, you adjust future estimates by the revealed "velocity" of the overall project. The concept is that you create a feedback loop to calibrate the value of story points for that sprint, and that you accept uncertainty. A good discussion is found in Mike Cohn's book, Agile Estimating and Planning. <blockquote> Because as soon as you drill down into the nitty gritty details of a backlog item you will probably almost always find something that you haven't thought about during planning. </blockquote> Missed tasks in estimate is the second most common source of estimation error in development projects (the 1st is ... changing requirements!)[1]. It's also a possible root cause of the "Planning Fallacy" generally. Agile processes tend to be against decomposing tasks too far in advance. However, the usual way to manage this risk is to build up estimation checklists. McConnell's Software Estimation: Demystifying the Black Art is a good resource -- tables 4.2, 4.3 and 4.4 (pp. 44-45) are an excellent starting point for your own checklists. [1] van Genuchten, Michiel. "Why is Software So Late? An Empirical Study of Reasons for Delay in Software Development". IEEE Transactions on Software Engineering, June 1991.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POSCRUM estimation accuracy
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJacques Chester
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.