ágil

Learn scrum with Jira Software

Instruções passo a passo sobre como conduzir um projeto do scrum

Claire Maynard Claire Maynard

Tutorial do Scrum

In this tutorial, we'll give you step-by-step instructions on how to drive a scrum project, prioritize and organize your backlog into sprints, run scrum ceremonies and more, all within Jira Software.

Tempo:

10 minutos para ler. Complete em duas semanas

 

Público-alvo:

You are new to scrum, agile software development, or Jira Software

 

Pré-requisito:

Você criou uma conta do Jira Software

Experimente grátis

O que é o scrum?

Scrum is one of the most popular frameworks for implementing agile. With scrum, the product is built in a series of fixed-length iterations called sprints that give teams a framework for shipping on a regular cadence.

 

Etapa 1: criar um projeto scrum

Once you create and log in to an account in Jira Software, you can create a project. When you're prompted to select a project template, select Scrum. Otherwise, you can learn how to create a Kanban project here.

Alternatively, if you’re looking for a simpler and more streamlined experience, consider giving our next-gen Scrum template a try. See Getting started with next-gen projects at the Atlassian Community to learn more.

Once you've created your project, you will land on the empty backlog. The backlog is also known as the product backlog and contains an ongoing list of your team's potential work items for the project.

Etapa 2: criar tarefas ou histórias de usuário na lista de pendências

In Jira Software, we call work items like user stories, tasks, and bugs "issues". Create a few user stories with the quick create option on the backlog. If you don't have user stories in mind, just create sample stories to get started and see how the process works.

 

Creating user stories | Atlassian agile coach
O que são histórias de usuário?

User stories are used to describe work items in a non-technical language and from a user's perspective. . As a {type of user}, I want {goal} so that I {receive benefit}.

 

Vamos usar um site como um exemplo simples para criar uma história de usuário.

 

As a customer, I want to be able to create an account so that I can see my previous purchases.

 

User stories are usually sketched out and prioritized by the product owner, and then the development team determines detailed tasks necessary to complete the story in an upcoming sprint. The development team is also responsible for estimating the relative effort required to complete the work of the story.  

Once you've created a few user stories, you can start prioritizing them in the backlog. In Jira Software, you rank or prioritize your stories by dragging and dropping them in the order that they should be worked on.

These are just the starting stories for your project. You will continue to create stories for the project's lifetime. This is because agility involves continuously learning and adapting.

Step 3: Create a sprint

Create your first sprint in the backlog so you can start planning the sprint.

O que é um sprint?

In Scrum, teams forecast to complete a set of user stories or other work items during a fixed time duration, known as a sprint. Generally speaking, sprints are one, two, or four weeks long. It's up to the team to determine the length of a sprint — we recommend starting with two weeks. That's long enough to get something accomplished, but not so long that the team isn't getting regular feedback. Once a sprint cadence is determined, the team perpetually operates on that cadence. Fixed length sprints reinforce estimation skills and predict the future velocity for the team as they work through the backlog.

Criar um sprint | Coach Agile Atlassian

Step 4: Hold the sprint planning meeting

At the beginning of a sprint, you should hold the sprint planning meeting with the rest of your team. The sprint planning meeting is a ceremony that sets up the entire team for success throughout the sprint. In this meeting, the entire team discusses the sprint goal and the stories in the prioritized product backlog. The development team creates detailed tasks and estimates for the high-priority stories. The development team then commits to completing a certain number of stories in the sprint. These stories and the plan for completing them become what is known as the sprint backlog.

Add story point estimates to your stories by adding a number in the Story point estimate field. You can also add more details to the stories or click the create subtask icon to further break down the work of the story.

Criar um sprint | Coach Agile Atlassian

When you're ready, drag the stories agreed to in the sprint planning meeting into the sprint that you just created. This is your sprint backlog.

O que é a reunião de planejamento de sprint?

Participantes: Obrigatório: equipe de desenvolvimento, scrum master, proprietário do produto

 

Quando: no início de um sprint.

 

Duration: Usually two hours per week of iteration – e.g. a two-week sprint kicks off with a four-hour planning meeting. The meeting ends when its purpose has been achieved.

 

Purpose: Plan the work of the sprint. The team agrees to the sprint goal and the sprint backlog.

What is a sprint goal?

When creating a sprint, the product owner usually identifies a sprint goal. This provides a theme for the work to be completed in the sprint. A sprint goal also provides some flexibility in the number of stories that are completed in a sprint. A sprint is considered a success if the sprint goal is achieved.

O que é estimativa ágil?

Traditional software teams give estimates in a time format: days, weeks, months.
Many agile teams, however, have transitioned to story points. Story points rate the relative effort of work, often in a Fibonacci-like format: 0, 0.5, 1, 2, 3, 5, 8, 13, 20, 40, 100. 

Estimates help you gauge how much work you should add to the next sprint based on the number of team members you have. After a few sprints, your team will get better at figuring out how much work they can do each sprint, which will help avoid over-committing.

Step 5: Start the sprint in Jira

Name the sprint. Some teams name the sprint based on their sprint goal. If there is a commonality between the issues in the sprint, name the sprint around that theme. Otherwise, you can name the sprint whatever you like.

Add a duration of the sprint and start and end dates. The start and end dates should align to your team's schedule. For example, some teams start sprints on a Monday and then end on a Friday morning in the next week. Other teams decide to start and end their sprints mid-week. It's up to you! If you're unsure how long your sprints should be, we recommend trying two weeks.

Add the sprint goal as agreed to in the sprint planning meeting.

Assim que iniciar seu sprint, você será direcionado para a aba de sprints ativos no projeto.

Sprints ativos | Coach Agile Atlassian

Essa aba é onde sua equipe trabalhará para pegar itens da coluna de afazeres e movê-los para a coluna "em andamento" e, eventualmente, "concluído"!

If you’re using the next-gen Scrum template, this will be called Board.

Step 6: Hold the daily standup meetings

Após começar seu sprint, reúna-se com sua equipe diariamente, normalmente pela manhã, para revisar no que todo mundo está trabalhando. O propósito disto é ver se alguém na sua equipe está enfrentando obstáculos na realização de tarefas de sprint.

O que é a reunião rápida diária?

Attendees (Primarily): development team

 

Quando: uma vez por dia, normalmente pela manhã

 

Duração: não mais que 15 minutos. Não reserve uma sala de conferências nem conduza a reunião rápida sentado. Ficar em pé faz com que a reunião seja rápida.

 

Purpose: The daily standup is designed to inform everyone quickly of what's going on across the team and to plan the work of the day. It's not a full status meeting. The tone should be light and fun, but informative. Have each team member answer the following questions:

 

  • O que fiz ontem?
  • No que trabalharei hoje?
  • Meu trabalho está com algum obstáculo?

 

Há uma responsabilidade implícita ao relatar o trabalho concluído ontem na frente de seus colegas de trabalho. Ninguém quer ser o membro da equipe que está constantemente fazendo a mesma coisa e não progride.

 

Dica de profissionais: algumas equipes usam cronômetros para que todos mantenham o ritmo. Outras equipes jogam uma bola entre todos para certificar-se de que todo mundo está prestando atenção. Muitas equipes distribuídas usam videoconferência ou bate-papo em grupo para lidar com problemas ocasionados pela distância. Sua equipe é única — sua reunião rápida deve ser também!

You can use the active sprints of your scrum board during the daily standup, so that each member can view the tasks they're working on.

Step 7: View the Burndown Chart

It's a good idea to check the Burndown Chart during a sprint. In Jira Software, the Burndown Chart shows the actual and estimated amount of work to be done in a sprint. The Burndown Chart is automatically updated by Jira as you complete work items. To view this chart, click Reports from the sidebar, and then select the Burndown Chart from the reports dropdown.

O que é um gráfico Burndown e como lê-lo.

A Burndown Chart shows the actual and estimated amount of work to be done in a sprint. The horizontal x-axis in a Burndown Chart indicates time, while the vertical y-axis typically indicates story points.

 

Use o gráfico Burndown para controlar o trabalho total remanescente para um sprint e para projetar a probabilidade de atingir a meta do sprint. Ao monitorar o trabalho restante durante a iteração, uma equipe pode gerenciar o progresso e responder de acordo.

Gráfico burndown ágil | Coach Agile Atlassian
Antipadrões que devem ser observados
  • A equipe finaliza, antecipadamente, sprint após sprint porque ela está se comprometendo a fazer muito trabalho.
  • A equipe perde seu sprint de previsão após o sprint porque eles estão se comprometendo a fazer muito trabalho.
  • A linha de burndown mostra quedas bruscas em vez de um burndown mais gradual porque o trabalho não foi dividido em partes menores.
  • O proprietário do produto adiciona ou altera o sprint intermediário do escopo.

Step 8: View the sprint report

At any point during or after the sprint, you can view the Sprint Report to monitor the sprint.

What is the sprint report?

The Sprint Report includes the Burndown Chart, and lists the work completed, work not completed, and any work added after the sprint started.

 

Step 9: Hold the sprint review meeting

The sprint review, or sprint demo, is a sharing meeting where the team shows what they've shipped in that sprint. Each sprint usually produces a working part of the product called an increment.

This is a meeting with a lot of feedback on the project and includes a brainstorming session to help decide what to do next.

Attendees (Primarily): development team, scrum master, product owner.
Optional: stakeholders

 

When: Typically on the last day of the sprint

 

Duration: Typically two hours for a two-week sprint

 

Purpose: Inspect the increment and collaboratively update the product backlog.

 

Perguntas a fazer:

 

  • A equipe atendeu a previsão de sprint?
  • Houve trabalho adicionado ou removido durante o sprint?
  • Algum trabalho não foi concluído no sprint?
  • Em caso afirmativo, por quê?

Etapa 10: fazer uma reunião de retrospectiva do sprint

After you complete the sprint, have your team do a retrospective. Document your retrospective somewhere. May we suggest Confluence?

O que é uma reunião de retrospectiva de sprint?

Attendees: development team, scrum master, product owner.

 

Quando: no final da iteração.

 

Duration:  Typically 90 minutes for a two-week sprint.

 

Purpose: The team inspects itself, including its processes, tools and team interaction. Improvement issues are often added to the next sprint's backlog.

 

As retrospectivas não não apenas um momento para reclamações sem ação. Use retrospectivas para descobrir o que está funcionando para que a equipe possa continuar a focar nessas áreas. Além disso, descubra o que não está funcionando e use esse momento para encontrar soluções criativas e desenvolver um plano de ação. Melhoria contínua é o que sustenta e impulsiona desenvolvimento dentro de uma equipe ágil e as retrospectivas são uma parte fundamental disso.

 

Perguntas a fazer:

 

  • O que fizemos certo durante o sprint?
  • O que poderíamos ter feito melhor?
  • O que vamos fazer melhor da próxima vez?

 

Dica profissional: mesmo se tudo estiver correndo bem na equipe, não pare de fazer retrospectivas. As retrospectivas fornecem orientação contínua para que a equipe possa manter tudo correndo bem.

Step 11: Complete the sprint in Jira

No final do sprint, você deve concluí-lo.

If the sprint has incomplete issues, you can:

  • Move the issue(s) to the backlog.
  • Move the issue(s) to a future sprint.
  • Move the issue(s) to a new sprint, which Jira will create for you.

Step 12: Repeat from step 2

Neste ponto, você aprendeu o básico sobre a criação de sua lista de pendências com histórias de usuário, organizando suas histórias de usuário em sprints, começando seu sprint e aguardando as cerimônias de Scrum. Você pode decidir se isto está funcionando para sua equipe, ou se gostaria de seguir em frente em alguns tópicos mais avançados.

 Depois que você e sua equipe souberem tudo sobre as etapas acima. Consulte o artigo avançado: Como efetuar práticas avançadas de scrum com o Jira Software.