Scrum walkthrough internship course held on September 10, 2019, at Endava in Targu-Mures.

1. 1
SCRUM WALKTHROUGH
ISZLAI ZOLTAN, SEPTEMBER 2019

2. 2
2
AGENDA
 INTRODUCTION
 THE GOAL
 ACTORS
 THE PROCESS
 SCRUM CEREMONIES
 PLANNING

3. 3
3
3
Scrum is an iterative and incremental development methodology for
agile project management; it’s a flexible and a holistic strategy where
the team works as a unit to achieve a common goal.
The crucial fact about scrum is that during the development the client
can change his mind about what he wanted previously .
SCRUM
INTRODUCTION

4. 4
4
4
THE GOAL
INTRO
 Scrum understands, that a problem can’t be fully understood, or
described, so it concentrates on the team instead
 With fast development we answer the questions which popup for
future requirements by the client
THE IDEA
 Management of complexity
 Unforeseen change management
 End goal change management

5. 5
5
5
PRODUCT OWNER
ACTORS
 It’s responsible for the product vision
 The person represents the client
 The product features are described and prioritized
 Sets the release deadlines
 Accepts or refuses the results

6. 6
6
6
TEAM
ACTORS
 Self managed, composed of multiple type of individuals with varied
knowledge
 Describe the work (breaks the work down into smaller pieces)
 They estimate the work
 They create the product

7. 7
7
7
SCRUM MASTER
ACTORS
 Protector of the team
 Problem solving, barrier blocking leader (Servant leader)
 Helps the team in the work, manages the management
 Supports the Scrum methodology during development

8. 8
8
THE SCRUM PROCESS

9. 9
9
9
THE DAILY SCRUM MEETING
INTRO
 “The heart of Scrum”
 Commitment and responsibility
 The whole team takes part (max 15 minutes)
EACH TEAM MEMBER ANSWERS
 What have I done since the last meeting?
 What I’m going to do until the next meeting?
 What problems did I face or will I face?

10. 10
10
10
SPRINTS
THE PRODUCT BACKLOG
USER STORIES
 An ordered list, which describes what are the requirements, which
is being maintained by the Scrum team
 The list is not complete, it’s not perfect and it will change during the
project development phase
 As a <user> I want to <functionality> so that <benefit>.
 As a librarian I want to search for the books based on the
publication date so that I can create a report for the latest books in
the library.
 As a user I want to be able to save the contents of my hard drive,
for safety purposes.
 As a writer, I want to change the introduction note about the author
so that I can remove any spelling mistakes.

11. 11
11
11
SPRINTS
SPRINTS AND SPRINT PLANNING
SPRINT PLANNING
 Features tied to a fix deadlines, which is doable in a Sprint
 If the project goal changes, the work can still be performed
 Communication happens between each person in the team
 The approach is from the user perspective
 Priority assignment happens here
 The acceptance criteria is set here
 The tasks are estimated here

12. 12
12
12
PLANNING
PLANNING POKER
 Each estimator is given a deck of cards
 Each card has an estimate written on it (Fibonacci sequence)
 The product owner reads a story and it’s discussed briefly
 Each estimator selects a card that’s his or her estimate
 Cards are turned over so all can see them
 Discuss differences (especially outliers)
 Re-estimate until estimates converge
 Zero development & testing effort (seldom used)
 ½ to 13 can grasp complexity, accurate estimate
 20 to 100 higher or unknown complexity (epics & themes)

13. 13
13
13
INTRO
RETROSPECTIVE
 What have I done since the last meeting?
 What I’m going to do until the next meeting?
 What problems did I face or will I face?
EACH TEAM MEMBER ANSWERS:
 “The heart of Scrum”
 Commitment and responsibility
 The whole team takes part (max 15 minutes)

14. 14
14
14
Q&A