CS-C2130 / CS-C2140 / CS-E4910

Software Project 1 / 2 / 3

Lecture 2: Scrum Basics

21.9.2016

Agenda

• Course Practicalities

• Scrum Basics / Prof. Casper Lassenius

• Introduction of the Scrum Masters

• Free discussions between the Scrum

Masters and developers

21.9.2016

Course Practicalities

• 15 teams / 131 persons (11*9 + 4*8 person teams)

• CS-E4910 students added to CS-C2130 in MyCourses

– allows you to deliver the learning diary

• Link to Google Spreadsheet was sent by e-mail on 16.9.

– update 1) your personal prefs and 2) your team’s common prefs

• Flowdock (communication tool)

– Info was sent by e-mail on 16.9.

21.9.2016

Scrum Game

• Scrum simulation

– Lego bricks as code

• Goals

– Learning to use Scrum in practice

– Getting to know your team

• Make sure that before the game you know

– Basic steps of the Scrum process

– Scrum roles

– Scrum terminology

• Come with an open mind

– It will be fun & you will learn a lot!

In the game we will not

teach you Scrum, but

you will use Scrum!

21.9.2016

Scrum Game - Registration

• Use the ScrumGame-Sheet in Google Drive

– Five sessions

• max. 36 persons per session

– Four game teams per session

• max. 9 persons per game team

• Get to the same session with your whole team

– …or you will be assigned to a random team in the beginning of the session

• …and you loose the opportunity to get to know your own team

• Register as soon as you have a few members in your team

– Please, try to fill the first sessions first!

– You can change the session later, if needed.

21.9.2016

Scrum Game - Learning Diary

• Content (about 1 page)

– Discuss honestly what you learned during the game (and mention if you

felt you did not learn something)

– Do you think that the game will help your project succeed? How?

– Was there something surprising / controversial in the game?

– You may compare the game to other Scrum materials or to your own

experiences.

– You may also give feedback on the game, what was good/what could

be improved.

• Deliver to MyCourses at most 1 week after the game!

21.9.2016

Researchers will use the

diaries for analyzing and

improving the game.

Scrum Basics

Prof. Casper Lassenius

Aalto University

21.9.2016

Goals of This Lecture

• Teach you

– Why you need a process for working in your projects

– Basics of the Scrum process

• Roles

• Process steps

• Terminology

• After this lecture

– You are able to participate in the Scrum game

– You know the basics of Scrum

• This lecture is based on

– Scrum Primer

– (Scrum Guide)

21.9.2016

Why Process?

21.9.2016

Why Scrum?

21.9.2016

Scrum Process:

21.9.2016

Scrum Roles

21.9.2016

Scrum Team

Scrum team = Team + Scrum Master + Product Owner

21.9.2016

Product Owner

• Is responsible for maximizing

return on investment, thus has

the final authority

• Identifies product features

• Prioritizes the features

• Interacts regularly with the

team, e.g. reviews the Sprint

results

• Product Owner ≈ Product

Manager ≈ Customer

21.9.2016

The Team

• Develops the product and provides ideas to the Product Owner about how to make the product great

• 7 ± 2 people

• Is cross-functional (includes all expertise necessary to deliver the potentially shippable product each sprint)

• Is self-managing: high degree of autonomy and accountability

• Every team member is just a team member, no other roles

21.9.2016

Scrum Master

• Helps the product group learn and apply

Scrum to achieve business value

• Is part of the Scrum Team

• Is NOT the manager of the team

members, NOR a project manager OR

team lead

• Serves the team, e.g. helps to remove

impediments, protects from outside

interference

• Is a coach and teacher, especially Scrum

principles and practices

• Who is the project manager in Scrum??

21.9.2016

Scrum Process

21.9.2016

Sprint / Iteration

• Time-boxed development cycles

• No more than 4 weeks, 2 weeks most common

• Never extended: ends exactly when planned, contents give flexibility

• The output of every sprint is: “Potentially Shippable Product Increment”, which means that item chosen for that sprint are “Done” (according to the DoD = Definition of Done)– System is integrated

– Fully tested

– End-user documented

– Potentially shippable

21.9.2016

Product Backlog

• Is a prioritized list of customer-centric features

• “Everything that could be done by the Team ever in order of priority”

• Includes “items”, e.g. new customer features, major engineering improvement goals, research work, (known defects)

• Includes effort estimates

• Is detailed appropriately

• Is regularly refined (“grooming”) = splitting, estimating, re-estimating items

21.9.2016

Scrum Board

21.9.2016

Release Planning

• No instructions given by Scrum

• Needed especially in case of a new product

• There Product Owner and Team shape a Scrum Product Backlog, including

– Planning the contents of the release

– Estimating, refining estimates

– Prioritizing

• May take a few days or a week…

• Not needed in continuous product development, done by product backlog refinements in every sprint

21.9.2016

Sprint Planning I

• Participants: Product Owner,

Team, Scrum Master

• Goal: understanding WHAT

the Product Owner wants and

WHY they are needed

• Discussion of the goals

context of the highest priority

items

– PO explains

– Team asks questions

21.9.2016

Sprint Planning II

• Participants: Team, Scrum Master (Product Owner reachable for questions)

• Focus on HOW to implement the items the Team decides to take on– Team decides how much work it will

complete!

• May contain:– Estimating the team’s capacity for the next

sprint

– Overall design

– Selecting and splitting product backlog items into tasks – building sprint backlog!

– Estimating items/tasks

– Selecting as many items team estimates they can realistically complete: sprint “commitment” / forecast

21.9.2016

Daily Scrum Meeting

• Participants: Team, Scrum Master (Product Owner optional)

• Update and coordination between team members – not a status reporting to anybody else

• Max 15 min

• Each member report to the other team members:– What has been accomplished since the

last meeting?

– What will be done before the next meeting?

– What obstacles are in the way?

• If discussion needed: follow-up meetings agreed and held afterwards

21.9.2016

Definition of Done

• Defined what is needed for something (e.g. task,

backlog item, sprint) to be considered “DONE”

• Sometimes people say it is ”done-done” to mean it

meets the criteria for DoD

• You must define your own DoD

• Typically things like

– Code is implemented, commented, integrated, reviewed/tested

21.9.2016

Sprint Review

• Participants: Team, Product Owner,

Scrum Master, other stakeholders

invited by the Product Owner

• Inspection and adaption related to the

product increment of functionality

– What is going on with the product and team

– What is going on with the Product Owner

and the market

– In-depth conversation

– Includes hands-on inspection of the real

software running live

21.9.2016

Sprint Retrospective

• Inspection and adaption related to the process and environment

• Participants: Team, Scrum Master, Product Owner (optional)

– Team discusses what’s working and what’s not working and agree on changes to try

– Usually the Scrum Master facilitates

– Different techniques, try different ones!

21.9.2016

Tracking Progress

Burndown / burn-up charts

21.9.2016

Want to Know More?

• Google

– Scrum Guide

– Scrum Primer

21.9.2016

End of Scrum Basics

21.9.2016

Next Steps

• Find a team

– Both Scrum Masters and developers can be active

– Teacher assigns the remaining developers to the teams on We 28.9.

• if you already belong to a team, make sure your Team ID is filled in GD

• if you are not in a team, update “Favorite Team ID” column by 27.9.

• Register to a Scrum Game session

– as soon as you have a few members in your team

• Lecture on We 28.9. in T4

– for Scrum Masters only, in English

21.9.2016

Introduction of the Scrum Masters

1. Haakana Simo

2. Haapala Olavi

3. Haikala Niko (not present)

4. Jaktholm Sami

5. Lehto Juho Oskari

6. Liljestrand Nico

7. Orgo Ly

8. Rantala Jesse

9. Sauvala Janne

10. Simell Aleksi

11. Timonen Mathias

12. Wallis Kim

13. Westersund Simon

14. Mertanen Joonas

15. Vesterinen Teppo

21.9.2016

• SW engineering background (school & work, if any)

• Preferences, e.g. work times, topics

• Anything else…

… in 60 seconds