Quantcast
Channel: Scrum.org Forum
Viewing all articles
Browse latest Browse all 5648

Estimating entire stories vs 'split' estimates

$
0
0

Hi guys

thanks for all the awesome replies / posts here. It's an awesome source of knowledge!

Wanted to understand if anyone else has experienced this:

A team looks at a requirement and splits the effort into front end, business logic & database. So, linked to the main requirement are tickets (not tasks), that each have their own estimates. I am more used to teams providing one estimate for a requirement, i.e. it's an 8 or 13 for the entire user story.

Does anyone else do the same? Any advice / critique?


Viewing all articles
Browse latest Browse all 5648

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>