New answers tagged

0 votes

Story points or number of stories

Put in the skin of the devs... what are they going to get by putting the effort into estimating a task? NONE. Forcing them to do it is a bad idea and making them accountable for the estimates is even ...
user avatar
1 vote

Story points or number of stories

A very interesting question with many facets. Why are the team reluctant to break work down before starting? why is estimation not working for you ? why are the team focussed on building stuff without ...
user avatar
  • 255
1 vote

Story points or number of stories

TL;DR You may have an X/Y problem where the symptom is Developers failing to see value in collaborative Sprint Planning. However, the root cause is more likely a disincentive for the Developers to ...
user avatar
  • 47.9k
0 votes

Story points or number of stories

The problem that I see here isn't one related estimation technique. The main problem that I see is the lack of investment in refinement activities. Planning is not the time to work on understanding, ...
user avatar
  • 17.7k
0 votes

Story points or number of stories

You should go with story point only, if the dev team is reluctant then you should take a reference of previous done stories. IMO- I never go with Story estimation into the story points.
user avatar
2 votes

How can I close an Epic with open defects?

TL;DR If the Scrum Team's Definition of Done for the epic requires this defect to be fixed before the epic can be considered fully complete, then the epic isn't really done until the defect is fixed. ...
user avatar
  • 47.9k

Top 50 recent answers are included