Scrum Ireland

So the Product Owner has listed the top priority items, the team has estimated how much they can do in a single Sprint, half way into a 3 week Sprint the Burndown Chart shows only 10developer days work out of estimated 30days work, what do you do now as a Team/Scrum Master? At the morning Scrum meeting the ScrumMaster points out that only 10 out of the 30 days are complete, this is what the Sprint Burndown Chart is for, to visualise the problems early on. If it ain't working then try something different. Get some tasks complete by tomorrow's Scrum needs to be the goal. Ask each team member what can be done to hurry along the completion of the items, something is holding up each developer, the developer must be honest and tell what the issue is could be; I haven't been focussed I'm being distracted by queries from outside the group I've had other tasks to do (This is a common one, but then why isn't the task listed in the Sprint backlog?). I don't understand ...

Estimating the time to complete a User Story in SCRUM is done by the development team. I mean the whole development team and not just the individual developer.  This is done using some sort of voting system which allows the development team to contribute their estimate for the User Story. One way to vote is to use a card voting system such as voting cards where each developer votes with a card, there's an online version of this at planningpoker.com .  Whatever medium you choose to use doesn't really matter, the process should be the same, the User Story is studied and the team may later sit together and give their estimation time by voting,if the estimates differ greatly then the reasons why should be discussed.  If a single value cannot be decided on and the estimate is larger than the time for the Sprint then a Spike is required or the User Story should be split into smaller User Stories.   When voting on the estimates of User Stories the Fabbonici number should be used i.e....