Thanks Mike for this valuable information. I have a doubt , if I want to pick a card say 5 points then does that mean it includes effort for build, unit testing and other testings( like Integration and QA). I hope I am clear with my question. Thanks !
How does this technique work with teams split into different functions like a frontend, backend, UI/UX and testing team? A particular user story might be a 2 for the frontend team, but a 5 for the backend team and a 8 for the UI/UX or testing team. So in this case, I don't suppose that everyone will converge on a common figure. So should we run the poker estimation individually by teams and if yes how would be consolidate it to arrive at a story size? Or is there a different approach to solving this?
There's a technique known as Complexity Bucket, where each of these efforts is estimated by the respective resource. Complexity can range from Low to High and given numbers 1-4. And all the numbers add up to give you the point based estimation for a story. However, as a self-organized & cross-functional team, it's always essential that the team comes to a consensus for point estimation and comes up with one number. BTW, we do not identify any roles in Scrum like UI, DBA, Developer, Tester etc. The Dev Team should comprise of all the skills/resources required to deliver the sprint.
