Loading presentation...
Prezi is an interactive zooming presentation

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

scrum medicore

scrum medicore
by

Renze J. Klamer

on 28 December 2015

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of scrum medicore

Scrum
Training

Scrum practice
Scrum background
What is Scrum?
a workshop
Conclude
What did you find
What could be improved?
What to do next?
1. Scrum is simple
2. Scrum has history
3. Scrum has principles
4. Scrum is fast and flexible
Action.
Inspect and adept.
Eliminate waste.
Is it really so simple?
Not many rules - easy to learn
(chess, football, cricket)
Difficult to play


Values:
Commitment
Focus
Openness
Respect
Courage
modelled as a SCRUM process
Individuals and interactions over processes and tools.

Working software over comprehensive documentation.

Customer collaboration over contract negotation.

responding to change over following a plan.
What to do?
small groups
talk about scrum
post-it notes (5 each)
- what do you want to know?
- what questions are to be answered?

present

total view
vote
Ball game
3 balls
pass on to each other
not to neighbour
remember order
2nd ball same order
3rd ball same order
as fast as you can
all balls have to be handled by all people,
end with the person who started
Draft backlog - Sprint 1
Details
Team
Product Owner
Scrum Master

Product Backlog
Sprint Backlog

Sprint 2-4 wk
daily stand-up
Sprint planning 1
Sprint planning 2
Sprint review
Sprint retrospective
Team
fully committed
All functions included
Self organising
does all the work and is enthousiastically
provides a demo to the product owner
Scrum roles
Scrumprocess
Lists
Product Backlog:
user stories
the higher the prio the more detail
sprint planning 1 determines order / prio of elements in product backlog.
team determines weight and leght of the user stories
Epic Story
User story (goal)
for (target group)
who (expression of need or want)
the (product) is a (category)
which is (unique advantage, compelling reason)
and not as (most important alterantive)
our product is (convincing difference)
Sprint
2-4 weken
Begins with Sprint planning 1
(all people involved)
GOAL!
determine priority of the user stories
detail discussion (outside team)
result: backlog prioritised

Sprint planning 2 (team)
tasks / to do list
commitment to the back-log
Scrum time boxes
Planning
Story points
'Size' of user story
relative to importance
- triangular comparison
- no unit of measure
Defintion of Done
Agreements
Everybody agrees
Updates are possible AND needed
Planning poker
let the cards do the talking
No reservations for the future
no assumptions - ask the product owner
make triangular comparisons
pay attention the the extremes
Focus
use reference user stories
Pokergame
Use animals to order in 'size':

Lion
Kangaroo
Rhinocerus
Bear = 2
Giraffe
Gorilla
Hippopotamus
Tiger
Epic Story

for (target group)
who (expression of need or want)
the (product) is a (category)
which is (unique advantage, compelling reason)
and not as (most important alterantive)
our product is (convincing difference)
User Story

barely enough
enough detail to be estimated by the team
detail depends on priority
as a story:
In order to (benefit)
as a (role, persona)
I want (feature)

Card, Conversation, Confirmation
I
ndependent
N
egotiable
V
aluable
E
stimable
S
mall
T
estable
Product Owner
fully committed
responsible for ROI
determines priorities
intermediate between team and stakeholders
accepts the result
Scrum roles
Scrum master
Is there for the team
Change agent
solves impendiments
responsible for the process
Scrum roles
Sprint retrospective
team (event. product owner)
Inspect and adept
1. situation
2. data collection
3. cause analyses
4 actions


Sprint Review
all involved
How did the sprint go?
Demo
feedback from stakeholders
continuation decisions
Scrum time boxes
Daily Scrum meeting - standup
team
15 minuten
everybody is prepared!
everybody answers shortly 3 questions
1. what did you do since last meeting?
2. what are you going to do today?
3. what impedements hinder you?
Scrum time boxes
Lists
Sprint Backlog contains
tasks (to realise user-stories)
only those user-stories which are committed to in that sprint.
determined by team and scrum master
sprint planning 2 determines sprint-backlog order
Full transcript