Loading 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

eGile - an introduction to SCRUM

No description
by

Mirza Keserovic

on 8 December 2014

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of eGile - an introduction to SCRUM

Waterfall
Scrum
Scrum is about
gradual development
of a product using a number of
short
and
timeboxed
development cycles (
iterations
), where a development team delivers a shippable work with
increased business value
of a product
by the end of every iteration
.
Unlike a lot of all development methodologies, in SCRUM it is NOT about drawing the perfect product diagram or writing the perfect requirement document.

In SCRUM the focus is on good
communication
between all involved parts,
fast changes
and
getting things done
.
To iterate a perfect solution
A traditional methodology
An introduction to
SCRUM

Dynamic and flexible
There is no universal solution
For every iteration the
Scrum Team
will get better and better to plan and execute the project.
eGile
Scrum
Product owner (PO)
How do we SCRUM?
Users and investors
All begins with an
idea...
also called Stakeholders
...a wish about
a change.
Product Owner (PO)
Product Owner (PO)
Product Owner (PO)
User Stories
Concrete user-story
A well defined user-story with good business value
should end up as a line in product backlog.
Is a hart of SCRUM. It is a prioritized list of requests (stories, features) described using "the customer's" terminology.
Product Backlog
A unique
identification
number for every user-story
A short,
descriptive name
of the story, clear enough so that all involved parts could distinguish it from another stories
Story's importance (priority) - how important the specified story is from PO's point of view. What is the
business value
of the story?
Relative
value of the first implementation time estimate. Denoted in "
story-points
".
A high level description of how story should be tested (do-this-do-that). Good for bringing clarity to the user-story name.
A place for any other info, reference or clarification.
Product Owner (PO)
...
Importance (Prio)
Product Backlog
Sprint Planning
Development Team (Dev)
Sprint Backlog
SPRINT
2 - 6 weeks
Scrum Master (SM)
24h
Product Backlog
...
...
Produkt Owner
Development Team
Product Backlog
If we have a development team
with capacity of
C
story-points/week

and

focus factor
F

then we can estimate
V
(velocity of development team)
Purpose with sprint planing meetings is to give the Development Team enough information to be able to independently work for a number of weeks
to give the Product Owner enough confidence
in Development Team to let them do so.
&
Product Owner (PO)
Development Team (Dev)
Scope
Importance
Estimate
???
Sprint planing meeting
Scrum Master (SM)
The principle of Yesterday's weather:

V = (C for Sprint 2) * F

where

F = (Actual V for Sprint 1) / (C for Sprint 1
)

if
SP2 = SP1
then
F = your guess is as good as mine
Sprint Backlog
...
Produkt Owner
Development Team
Product Backlog
C
depends on:
1) Sprints length (2-6 weeks)
2) Number of team members
3) Member commitment

Focus factor
F
is a statistical value of team's efficiency.

Estimated velocity
V
is product
of capacity
C
and focus factor
F

V = C * F
Sprint Backlog
4 story-points

8 story-points


5 story-points

7 story-points

4 story-points
High-importance



...




Lo-importance
Story-point:
Can be expressed in hours or days
Is an effective development time with no disturbances
Measured in days:
One story point = 6 effective working hours
Minimum time = 0,5 story-point (3 hours)
Maximum time = 20 story-points
Why?
Everything less then 3 hours = micromanagement
Everything more then 20-40 days = risk for under/overcommitment
Importance is indicated with a number from 1 to 150
where higher importance (priority) means higher number.

The scale is relative:
leave space
between importance-values in order to be more flexible while setting a next value or making changes.
4 story-points

8 story-points


5 story-points

7 story-points

4 story-points
...
Produkt Owner
Development Team
Product Backlog
Example:
Sprint length = 2 weeks
Team has 5 member
Member commitment:
One team member works 50% with sprint and all other team members work 80%
Also one team member is on vacation 5 days
Focus factor
F
is 65%
Sprint Backlog
4 story-points

8 story-points


5 story-points

7 story-points

4 story-points
This gives us
V
= (2 * (3 * 4 + 2,5) + 4) *
F
= 33
* F
= 33 * 0,65 = 21,45 ~ 21,5 story-points
...
Produkt Owner
Development Team
Product Backlog
What is Estimated velocity?
Sprint Backlog
4 story-points

8 story-points


5 story-points

7 story-points

4 story-points
...
Produkt Owner
Development Team
Product Backlog
Sprint Backlog
4 story-points

8 story-points


5 story-points

7 story-points

4 story-points
High-importance



...




Lo-importance
...
Produkt Owner
Development Team
Product Backlog
Sprint Backlog
4 story-points

8 story-points


5 story-points

7 story-points

4 story-points
17
24
21,5
Under-commitment /
Over-commitment
...
Produkt Owner
Development Team
Product Backlog
Sprint Backlog
4 story-points

8 story-points


5 story-points

7 story-points

4 story-points
21
21,5
4 story-points

8 story-points


5 story-points

4 story-points
Direct communication is fundamental for SCRUM
och sprint planing in the most important part of a SCRUM project. That is why:

All Scrum Team members inclusive Project Owner must always attend/be available during sprint planing.
Product Owner (PO)
Development Team (Dev)
Sprint planing meeting
Scrum Master (SM)
Meeting output (importance):

1) Decide sprint
goal
and
demo date
(done date).
2) The
list of stories
that have been accepted for sprint.
3)
Estimate
filled in for each story in sprint.
4)
"How to demo"
filled in for each story in sprint.
5)
Velocity and resources
calculations done. Include list of team members and their commitment.
6) Specify time for
daily scrum
.
7) Stories broken down in
tasks
.
Product Owner (PO)
Development Team (Dev)
Sprint planing meeting
gradual development

of a product using a number of
short

and
timeboxed

development cycles (
iterations
), where a development team delivers a shippable work with
increased business value
of a product
by the end of every iteration
.
Simplified...
Followup or how is team doing?
Burndown chart nicely following the estimated-time line
Followup or how is team doing?
Burndown chart shows time for an over committed sprint
Followup or how is team doing?
Burndown chart shows time for an under committed team
Goal - Something that has
not yet been achieved
.
An answer to the questions: "Why are we doing this?" "Why don't we all just go o-ha Bad Gastein instead?"
Time estimation and braking down the stories into smaller
tasks
is a process that usually takes the largest part of sprint planing.
However it is also the most important part of the meeting because this is where all important
questions
and
misunderstandings
will surface.
Stories and tasks - Index cards and post-its
Sprint and daily scrum
eGain + agile = eGile
eGain + agile = eGile
Sales PO
Salesman
Customer
User
Marketing PO
...
Energy PO
Support/Installation PO
Product Dev. PO
Mantis
Produktråds möte
Product Council Meeting
eGain + agile = eGile
eGile product meetings:
first day at beginning of every sprint
timeboxed at 4 hours
all PO's involved should be present in the meeting room or on Skype during whole meeting
eGain + agile = eGile
Timeboxed Sprint Planning meeting (example):
13:00 - 13:30


13:30 - 15:00



15:00 - 16:00


16:00 - 17:00
PO goes through sprint
goal
and summarizes
product backlog
. Demo place and time is set.

Team
time-estimates
, and
break down
items as necessary.
PO

updates importance ratings. Items are clarified and "
How to do
" is filled in for all items in sprint.

Team selects
stories to be included
in sprint and makes
velocity calculations
as a reality check.

Time decides time and place for
daily scrum
. Further breakdown of stories into tasks.
Bugs
Questions?
Unlike a lot of all development methodologies, in SCRUM it is NOT about drawing the perfect product diagram or writing the perfect requirement document.

In SCRUM the focus is on good
communication
between all involved parts,
fast changes
and
getting things done
.
Dynamic and flexible
The story about the Chicken and the Pig
A Pig and a Chicken are walking down the road.
The Chicken says: "Hey Pig, I was thinking we should open a restaurant!".
Pig replies: "Hm, maybe, what would we call it?".
The Chicken responds: "How about 'ham-n-eggs'?".

The Pig thinks for a moment and says: "No thanks. I'd be committed, but you'd only be involved!"
committed to the project and accountable for its outcome are:

Scrum Master, Product Owners and Development Team
are those who consult on the project and are informed of its progress:

Users, Customers and Executive Management
PO
Dev
SM
Product Council Meeting
More questions?

mirza.keserovic@gmail.com
Full transcript