Stack Exchange Network

Stack Exchange network consists of 175 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Visit Stack Exchange

Hot answers tagged

4

The statements that you claim should be true in Scrum aren't necessarily true in Scrum, according to the Scrum Guide. It is not true, according to Scrum, that you should be estimating user stories in story points. The Scrum Guide mentions neither user stories nor story points. In Scrum, you have a Product Backlog that contains Product Backlog Items, and one ...


1

The official Scrum answer is "Estimate complexity not time and use Story Points" However, on a practical note I would say estimation is not something you want to get hung up on. There are a couple of main objectives scrum is trying to achieve which impact estimation. You can measure progress towards the story in terms of completed tasks. This means that ...


1

Stories are a tiny piece of functionality, a piece of code that is testable and provides some value. As such the workflow should be that they are raised, analysed, coded, tested, released. As such these are owned by the team as a whole and as part of the work pipeline will transition from one 'discipline' / expert to another. If you must, you can use sub-...


Only top voted, non community-wiki answers of a minimum length are eligible