Scrum Spreadsheet Template

Scrum Spreadsheet Template– Did you know the profile of Scrum Master is among the 10 most wanted in the labor market? Enroll in the Scrum Master Course + Lead Scrum Teams.

The Scrum methodology divides the software development process into a series of iterations, called Sprints. At the beginning of the iteration a planning meeting is held (Sprint Planning), where the list of tasks of the iteration (Sprint Backlog) is defined.

In Scrum, the iteration task list template (Sprint Backlog) is a list of the elements of the product stack (Product Backlog) and its component tasks, selected by the Scrum team for the iteration.

Therefore, to elaborate the list of tasks of the iteration, it is necessary to have previously defined the product stack (Product Backlog) and the elements of the product backlog, which can be documented in the form of user stories (There are other forms, for Scrum does not prescribe any).

While the product stack contains only stories and covers the entire project, the iteration task list expands the detail and lists the individual tasks needed to implement them, for example screen design, software development, connection configuration with interfaces and databases, tests, among others.

Download the template in the following link

>> Iteration Task List Template (Sprint Backlog)

The template is free of copyright and can be used freely by our readers.

Scrum Master Online Course

Would you like to get a general and complete overview of Scrum and clear up false paradigms?

Sign up for the Course:

Scrum Master + Lead Scrum Teams

More templates of agile methodologies

Scrum templates: Product roadmap (Agile Roadmap)
Scrum templates: User stories and acceptance criteria
Scrum templates: Product stack (Product Backlog)
Scrum templates: Retrospective meeting

> More Software Development Project Management Templates

Scrum Spreadsheet Template

Scrum Spreadsheet Template
Scrum Spreadsheet Template

How to use the template?

To complete the template, the elements of the product stack (Product Backlog) are selected one by one, defining the individual tasks needed to develop and implement them.

For each task, the Scrum team defines the necessary effort estimates, which can be expressed in hours, this is done to determine if all the selected work can be completed in one iteration (Sprint).

One aspect that is important to note is that the Sprint Backlog is a live artifact, which evolves throughout the Sprint, in fact, the development team only needs to define the tasks for the first days in the Sprint Planning meeting and then it can go expanding the Sprint Backlog as the work evolves in the iteration and discover more about the technical ways to implement the elements of the Product Backlog.

If during this evolution it will happen that it is discovered that the amount of work exceeds the capacity for the Sprint, the development team must negotiate postponing for another Sprint any of the Product Backlog elements selected for the iteration.

Scrum states that the development team must self-organize to undertake the work established in the Sprint Backlog. The Scrum Master, helps the team, providing Coaching in self-organization and cross functions. On the other hand, the Scrum Master supports the Product Owner in the understanding of how product planning is carried out in an environment of empiricism (Scrum is based on empiricism).

Scrum Velocity Calculation Spreadsheet
Scrum Velocity Calculation Spreadsheet

Description of the template

Next the content of the template:

  • Product backlog item identifier (ID): A code that refers to the item in the product stack (Product Backlog) to which the task of the iteration refers.
  • Statement of the Product Backlog item: Statement or name of the product stack item (Product Backlog). In most cases, the name assigned to the product backlog element is the same as the user history (If the user history is the form selected by the Scrum team to document it, there are other forms and Scrum does not prescribe any).
  • Task: Name of the iteration task (Sprint) specified in this line, represents the minimum element that is planned. To complete a product backlog element you will need to execute several tasks, for example: Design screen, link fields with the database, define processes, configure connections with interfaces or database, among others.
  • Owner / Volunteer: Member of the Scrum team who has taken responsibility for the task. He is also called a volunteer because in Scrum the tasks are not assigned by a Manager or supervisor, but each member selects the task that he will execute. A person will take one or several tasks in the daily meeting, and once these are completed (according to the definition of “fact”) he / she will be able to take on other tasks.
  • Status: Current status of the task. The types of status are decided by the development team (they can be advised by the Scrum Master). For example, a status classification could be: To start, in process and done (completed). The status classification can also be linked to the columns that are reflected in a Kanban board (if the team decides to use a Kanban board).
  • Estimated total hours: Hours estimated by the Scrum team to execute the task. The allocation of estimates is made during the planning meeting of the iteration (Sprint Planning Meeting).
  • Day 1 ….. Day n: Once the iteration begins to run, the columns are used to keep track of the hours that have been consumed in each task and how many hours remain to complete it.
  • Cons .: Hours consumed in the task on the specified day.
  • Rest .: Hours remaining after recording the daily consumption. It is calculated by taking the hours that were left the previous day and subtracting the hours consumed in the day. If it is the first day, the hours of day 1 are subtracted from the estimate of total hours.
  • Total: Registers the sum of all the hours consumed in the Sprint and the remaining hours. The remaining hours should be zero if the task can be executed in its entirety.
Scrum Product Backlog Template
Scrum Product Backlog Template

And what do you think?

What format or template have you used to record the planning of the iteration? What do you think of including planning and tracking information in the same template? What would you add or remove? Leave us your comments in this post or send us a direct message to the Contact Us section. We invite you to subscribe through the different channels.

Are you looking for more templates of agile methodologies?

Do you want to get project management templates and agile methodologies completely free and directly in your email, then click on “subscribe” below. What are you waiting for?

Gallery of Scrum Spreadsheet Template

( Click Image to Enlarge )

See More!