Should you ever re-estimate user stories?
My current project is having a ‘discussion’ which is split down the middle- “this story is more complex than we originally thought, we should re-estimate” vs “you should never re-estimate as you only ever estimate up and never down”.
Should the number of developers be considered when estimating a task?
I am pretty inexperienced with working in agile projects but I have tried it a few times and I always run into this problem when estimating a task.
What are the methods to estimate source code value?
I’ve been working on some project on my free time for the past few months. Recently I’ve been approached by friends to build a startup, and this source code would be very valuable to us.
Freelancing – Getting paid for the quote or estimate [closed]
Closed 9 years ago.
If you have several SCRUM teams working on one backlog, how do you divide story point estimation between those teams?
I’m asking because approach in my company looks as follows:
Where did the estimation rule of thumb originate that time spent will be one-third in each of the following: design, implementation, and testing?
I’m looking for a reference to the following. I commonly hear that one-third of a projects time will be spent in design, one-third in implementation, and one-third in testing. The three phases of development seems to be derived from the waterfall model. But, where did the time division originate (1/3, 1/3, 1/3)? Is there a paper or book that this is from?
Why do we use story points instead of man days when estimating user stories?
In agile methodologies (e.g. SCRUM), the complexity/effort needed for user stories are measured in Story points. Story points are used to calculate how many user stories a team can take in an iteration.
Has research been done on the effectiveness of Planning Poker as an estimation technique?
Although it is a commonly held opinion that planning poker improves the accuracy of project estimations (a small sample of which demonstrated on this question), has any defined research been done on the subject?
How are effort estimations and duration estimations distinct?
How are effort estimations and duration estimations distinct?
Efficient way to create a code estimation/technical specification in a fast-moving environment
To better understand my question, let me elaborate the background of the subject matter.