Articles

Scrum Agile Sprint Planning is a collaborative meeting held at the beginning of each sprint where the Scrum team determines the work to be completed during the upcoming sprint. During this session, the Product Owner presents the highest-priority user stories from the product backlog, and the team discusses and selects the ones they can realistically commit to delivering.

Sprint Planning Meeting

The Sprint Planning Meeting is the discussion held by a Scrum team with the goal of agreeing which task will be executed during a set sprint period. In preparing for the Sprint Planning Meeting the SCRUM Master needs to surround the team with the following artifacts and discussion elements:

1. Product Backlog

2. Sprint Backlog

3. Burn-down Chart

The Sprint Planning Meeting is attended by the Product Owner (voice of the customer), Scrum Master and the Development Team. This team discussion is convened to discuss/plan the execution of user stories over the current Sprint and is held in co-located facilities.

In this meeting, the product owner will be prepared to discuss or present enough product backlog items to fit known team’s sprint velocity and is concerned in communicating the sprint goal that will result in a shippable product.

The meeting is devoted to defining the sprint goal which together with the object definition – a Q & A period where the PO details his priorities, the team decomposes user stories from the Product Backlog and devotes time to estimation –where tasks are defined according to time/risk/complexity. Upon agreement a number of these are moved onto the current Sprint Backlog that the team will volunteer to work on and revisit during the sprint.

The Product Backlog

In the example above we have taken a snapshot of a Product backlog and its initial stages of decomposition. Please note that some of the entries were introduced not by the PO but by members of the development team as items found during refinement.

The Sprint Backlog

An output of the Sprint Review Meeting, the Sprint Backlog is shown above. There can be many varieties of what is listed but for the most part it identifies the User Story from where the task originated the description of the task, the status and the estimate value. The estimate is the measure of the task relative to the velocity and the team accomplishment value.

The Burn-down Chart

One of the best sprint status reporting artifacts, the Burn-down Chart is used to assess the success of the sprint remaining days relative to the target velocity. The chart is updated towards the end of the sprint day by the team deducting the amount of completed work from the sprint backlog. Unfinished tasks are moved back to the product backlog and may be prioritized on the next sprint iteration.

Scrum Agile Sprint Planning is a collaborative meeting held at the beginning of each sprint where the Scrum team determines the work to be completed during the upcoming sprint. During this session, the Product Owner presents the highest-priority user stories from the product backlog, and the team discusses and selects the ones they can realistically commit to delivering.

Sprint Planning Meeting

The Sprint Planning Meeting is the discussion held by a Scrum team with the goal of agreeing which task will be executed during a set sprint period. In preparing for the Sprint Planning Meeting the SCRUM Master needs to surround the team with the following artifacts and discussion elements:

1. Product Backlog

2. Sprint Backlog

3. Burn-down Chart

The Sprint Planning Meeting is attended by the Product Owner (voice of the customer), Scrum Master and the Development Team. This team discussion is convened to discuss/plan the execution of user stories over the current Sprint and is held in co-located facilities.

In this meeting, the product owner will be prepared to discuss or present enough product backlog items to fit known team’s sprint velocity and is concerned in communicating the sprint goal that will result in a shippable product.

The meeting is devoted to defining the sprint goal which together with the object definition – a Q & A period where the PO details his priorities, the team decomposes user stories from the Product Backlog and devotes time to estimation –where tasks are defined according to time/risk/complexity. Upon agreement a number of these are moved onto the current Sprint Backlog that the team will volunteer to work on and revisit during the sprint.

The Product Backlog

In the example above we have taken a snapshot of a Product backlog and its initial stages of decomposition. Please note that some of the entries were introduced not by the PO but by members of the development team as items found during refinement.

The Sprint Backlog

An output of the Sprint Review Meeting, the Sprint Backlog is shown above. There can be many varieties of what is listed but for the most part it identifies the User Story from where the task originated the description of the task, the status and the estimate value. The estimate is the measure of the task relative to the velocity and the team accomplishment value.

The Burn-down Chart

One of the best sprint status reporting artifacts, the Burn-down Chart is used to assess the success of the sprint remaining days relative to the target velocity. The chart is updated towards the end of the sprint day by the team deducting the amount of completed work from the sprint backlog. Unfinished tasks are moved back to the product backlog and may be prioritized on the next sprint iteration.

O Scrum Agile Sprint Planning é uma reunião colaborativa realizada no início de cada sprint, onde a equipe Scrum determina o trabalho a ser concluído durante o próximo sprint. Durante esta sessão, o Product Owner apresenta as histórias de usuário de maior prioridade do backlog do produto, e a equipe discute e seleciona aquelas com as quais eles podem se comprometer realisticamente a entregar.

Reunião de planejamento do Sprint

A reunião de planejamento do Sprint é a discussão realizada por uma equipe Scrum com o objetivo de concordar qual tarefa será executada durante um período de sprint definido. Ao se preparar para a reunião de planejamento do Sprint, o SCRUM Master precisa cercar a equipe com os seguintes artefatos e elementos de discussão:

1. Backlog do produto

2. Backlog do Sprint

3. Gráfico de Burn-down

A reunião de planejamento do Sprint é assistida pelo Product Owner (voz do cliente), Scrum Master e a equipe de desenvolvimento. Esta discussão da equipe é convocada para discutir/planejar a execução de histórias de usuário durante o Sprint atual e é realizada em instalações co-localizadas.

Nesta reunião, o product owner estará preparado para discutir ou apresentar itens de backlog de produto suficientes para se adequar à velocidade de sprint conhecida da equipe e está preocupado em comunicar a meta de sprint que resultará em um produto lançável.

A reunião é dedicada a definir a meta de sprint que, juntamente com a definição do objeto – um período de perguntas e respostas onde o PO detalha suas prioridades, a equipe decompõe histórias de usuário do Product Backlog e dedica tempo à estimativa – onde as tarefas são definidas de acordo com tempo/risco/complexidade. Após o acordo, várias delas são movidas para o Sprint Backlog atual, no qual a equipe se voluntariará para trabalhar e revisitar durante o sprint.

O Product Backlog

No exemplo acima, tiramos um instantâneo de um Product backlog e seus estágios iniciais de decomposição. Observe que algumas das entradas foram introduzidas não pelo PO, mas por membros da equipe de desenvolvimento como itens encontrados durante o refinamento.

O Sprint Backlog

Uma saída da Reunião de Revisão do Sprint, o Sprint Backlog é mostrado acima. Pode haver muitas variedades do que é listado, mas na maior parte ele identifica a História do Usuário de onde a tarefa se originou, a descrição da tarefa, o status e o valor estimado. A estimativa é a medida da tarefa em relação à velocidade e ao valor de realização da equipe.

O Gráfico Burn-down

Um dos melhores artefatos de relatórios de status de sprint, o Burn-down Chart é usado para avaliar o sucesso dos dias restantes do sprint em relação à velocidade alvo. O gráfico é atualizado no final do dia do sprint pela equipe deduzindo a quantidade de trabalho concluído do backlog do sprint. Tarefas inacabadas são movidas de volta para o backlog do produto e podem ser priorizadas na próxima iteração do sprint.