Explanation of Sprint Backlog

Question

Give a brief explanation of Sprint Backlog.

Answer 1

The sprint backlog is the list of work Development Team should address throughout the next sprint. The list is derived by the selecting stories or features from the top of product backlog till the Development Team feels it has sufficient work to fill the sprint. This is completed by the Development Team asking ‘Can we also do this?’ and adding stories or features to sprint backlog. The Development Team must keep in mind the velocity of its preceding Sprints (total story points done from each of last sprints stories) when selecting stories or features for new sprint, and use this number as a guide line of how much ‘effort’ they can complete.

The stories or also features are broken down in tasks by Development Team, which, as a best practice, must normally be between four and 16 hours of work. With this level of detail Development Team understands accurately what to do, and potentially, anyone can select a task from the list. Tasks on sprint backlog are never allocated; rather, tasks are signed up for by team members as required throughout the daily scrum, according to the set priority and Development Team member skills. This encourages self-organization of Development Team, and developer buy-in.

The sprint backlog is property of Development Team, and all incorporated estimates are given by the Development Team. Often an accompanying task board is employed to see and change or alter the state of tasks of current sprint,