Tutorial

Learn scrum with Jira Software

Detaillierte Anleitung zur Umsetzung eines Scrum-Projekts

Claire Maynard Claire Maynard

Scrum-Tutorial

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.

Zeit:

Lesedauer: 10 Minuten Dauer der Umsetzung: 2 Wochen

 

Zielpublikum:

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

 

Voraussetzungen:

Du hast einen Jira Software-Account erstellt.

Kostenlos testen

Was ist 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.

 

Schritt 1: Erstellen eines Scrum-Projekts

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.

Schritt 2: Erstellen von User Storys oder Aufgaben im Backlog

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.

 

Erstellen von User Storys | Atlassian Agile Coach
Was sind User Storys?

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}.

 

Verwenden wir eine Website als einfaches Beispiel für die Erstellung einer User Story.

 

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.

Was ist ein 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.

Erstellen eines Sprints | Atlassian Agile Coach

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.

Erstellen eines Sprints | Atlassian Agile Coach

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.

Was ist ein Sprintplanungsmeeting?

Teilnehmer: Erforderlich: Entwicklerteam, Scrum Master, Product Owner

 

Wann: Zu Beginn eines Sprints

 

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.

Was ist eine agile Schätzung

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.

Sobald du deinen Sprint begonnen hast, wird im Projekt die Registerkarte "Aktive Sprints" angezeigt.

Aktive Sprints | Atlassian Agile Coach

Hier wählt das Team Elemente aus der Spalte "Zu erledigen" und zieht sie in die Spalte "In Bearbeitung" und schließlich in "Erledigt".

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

Step 6: Hold the daily standup meetings

Versammle dein Team nach Beginn deines Sprints jeden Tag, normalerweise morgens, um durchzugehen, woran die einzelnen Teammitglieder gerade arbeiten. So erkennst du rechtzeitig, ob ein Teammitglied auf Schwierigkeiten stößt, die die Fertigstellung des Sprints gefährden.

Was ist ein tägliches Standup-Meeting?

Attendees (Primarily): development team

 

Wann: Einmal täglich, normalerweise am Morgen

 

Dauer: Nicht mehr als 15 Minuten Für Standup-Meetings ist kein Konferenzraum erforderlich, da das Meeting nicht im Sitzen abgehalten wird. Das Stehen trägt dazu bei, das Meeting kurz zu halten!

 

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:

 

  • Was habe ich gestern erledigt?
  • Woran werde ich heute arbeiten?
  • Bin ich durch irgendetwas blockiert?

 

Es besteht die stillschweigende Übereinkunft, dass du vor deinen Kollegen berichtest, welche Arbeiten du gestern erledigt hast. Niemand möchte das Teammitglied sein, das ständig an derselben Sache arbeitet und keinen Fortschritt macht.

 

Profitipp: Einige Teams nutzen Timer, um alle auf Kurs zu halten. Andere werfen einen Ball im Team hin und her, um sicherzustellen, dass alle aufmerksam sind. Viele verteilte Teams nutzen Videokonferenzen oder Gruppenchats, um die Distanz zu überbrücken. Dein Team ist einzigartig – dein Standup-Meeting sollte dies ebenfalls sein!

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.

Was ist ein Burndown-Chart und wie wird es gelesen?

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.

 

Nutze das Burndown-Chart, um alle im Sprint ausstehenden Aufgaben zu verfolgen und einzuschätzen, wie wahrscheinlich das Erreichen des Sprintziels ist. Durch das Verfolgen der ausstehenden Aufgaben während der Iteration kann ein Team seinen Fortschritt verwalten und entsprechend reagieren.

Agile Burndown-Charts | Atlassian Agile Coach
Anti-Pattern, die vermieden werden sollten
  • Das Team erledigt nahezu alle Sprints vorzeitig, da es nicht genug Aufgaben übernommen hat.
  • Das Team hält die Prognose über mehrere Sprints nicht ein, da es zu viele Aufgaben auf sich genommen hat.
  • Die Burndown-Linie sinkt an einigen Stellen stark ab statt graduell, weil die Aufgaben nicht granular aufgeteilt wurden.
  • Der Product Owner erweitert oder ändert den Umfang mitten im Sprint.

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.

 

Diese Fragen solltest du dir stellen:

 

  • Hat das Team die Sprintprognose eingehalten?
  • Wurden während des Sprints Aufgaben hinzugefügt oder entfernt?
  • Blieben Aufgaben des Sprints unerledigt?
  • Wenn ja, warum?

Schritt 10: Abhalten des Sprintretrospektivmeetings

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

Was ist ein Sprintretrospektivmeeting

Attendees: development team, scrum master, product owner.

 

Wann: Am Ende einer Iteration

 

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.

 

Retrospektiven sind nicht die Zeit für Beschwerden, die keine Aktion nach sich ziehen. Nutze Retrospektiven, um herauszufinden, was funktioniert, damit das Team sich weiterhin auf diese Bereiche konzentrieren kann. Finde außerdem heraus, was nicht funktioniert, und nutze die Zeit, um kreative Lösungen zu finden und einen Aktionsplan zu entwickeln. Eine kontinuierliche Verbesserung unterstützt und fördert die Entwicklung in einem agilen Team und Retrospektiven leisten einen wichtigen Beitrag dazu.

 

Diese Fragen solltest du dir stellen:

 

  • Was ist im Sprint gut gelaufen?
  • Was hätten wir besser machen können?
  • Was werden wir nächstes Mal besser machen?

 

Profitipp: Auch wenn die Dinge im Team gut laufen, sollten Retrospektiven fortgesetzt werden. Retrospektiven sind eine fortlaufende Orientierungshilfe für das Team, damit die Dinge weiterhin gut laufen.

Step 11: Complete the sprint in Jira

Am Ende des Sprints muss dieser abgeschlossen werden.

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

Nun verfügst du über die Grundlagen zur Erstellung deines Backlogs mit User Storys, zur Einordnung deiner User Storys in Sprints, für den Beginn deines Sprints und zum Abhalten von Scrum-Zeremonien. Mit diesen Kenntnissen kannst du entscheiden, ob all dies für dein Team funktioniert oder ob du in ein paar Themen noch tiefer eintauchen möchtest.

 Nachdem du und dein Team die obigen Schritte beherrschen, kannst du dir die Schritte in diesem weiterführenden Artikel vornehmen: Scrum-Verfahren mit Jira Software für Fortgeschrittene