Embed Size (px)
Citation preview
Software Engineering @ LEIC/LETI
Scrum
Scrum
(Sommerville, Fig 3.9)
Team Organization
self-organizing and cross-functional
Team Organization
self-organizing and cross-functional
product owner
Team Organization
self-organizing and cross-functional
product owner
scrum master
Team Organization
self-organizing and cross-functional
product owner
scrum master
teammember
Product Owner
responsible for managing the product backlog
Product Owner
responsible for managing the product backlog
value
Development Team
plane and cross-functionalsingle accountability
Development Team
plane and cross-functionalsingle accountability
increm
ent
Scrum Master
servant-leader
Scrum Master
servant-leader
facilit
ator
Pregame Phase
Set the Product Vision
Set the Product Vision
common language
Set the Product Vision
common languagefunctio
nal staff
Create Initial Product Backlog
not complete (half a day work)
Create Initial Product Backlog
not complete (half a day work)storie
s
Create Initial Product Backlog
not complete (half a day work)storie
s
product owner
Story
Story
relative business valuerelative estimation
Prioritize the Product Backlog
use the business value
Estimate the Product Backlog
use ideal daysuse story points - fibonacci sequence
Estimate the Product Backlog
use ideal daysuse story points - fibonacci sequence
averag
e
Estimate the Product Backlog
use ideal daysuse story points - fibonacci sequence
averag
e
poker ga
me
Adjust Estimates
Adjust Estimatescomplexity factor
Adjust Estimatescomplexity factor
drag factor
Adjust Estimatescomplexity factor
drag factorworking environment
Adjust Estimatescomplexity factor
drag factorworking environment
multiple-teams
Adjust Estimatescomplexity factor
drag factorworking environment
multiple-teams subjec
tive
Choose Sprint Length
2-4 weeks
Calculate Initial Velocityprevious projects
break stories into tasksexecute short sprint
Calculating Durationduration = size remaining / velocity
duration = ideal time remaining / velocity
Game Phase
Sprint Planning Meetinghalf a day meeting
Sprint Planning Meetinghalf a day meeting
available hours
Sprint Planning Meetinghalf a day meeting
available hours
sprint business value
Sprint Planning Meetinghalf a day meeting
available hours
sprint business value
sprint stories
Sprint Planning Meetinghalf a day meeting
available hours
sprint business value
sprint stories
sprint tasks backlog
Executing the Sprint
Executing the Sprint
allocating tasks
Executing the Sprint
allocating tasks
daily stand-up meeting
Executing the Sprint
allocating tasks
daily stand-up meeting15 minutes
Executing the Sprint
allocating tasks
daily stand-up meeting15 minutes
common language
Executing the Sprint
allocating tasks
daily stand-up meeting15 minutes
common language
impediments
Executing the Sprint
allocating tasks
daily stand-up meeting15 minutes
common language
impediments
sticking to the sprint backlog
Executing the Sprint
allocating tasks
daily stand-up meeting15 minutes
common language
impediments
sticking to the sprint backlog
white-board for the sprint backlog
Executing the Sprint
allocating tasks
daily stand-up meeting15 minutes
common language
impediments
sticking to the sprint backlog
white-board for the sprint backlog
daily estimation of time-remaining
Executing the Sprint
allocating tasks
daily stand-up meeting15 minutes
common language
impediments
sticking to the sprint backlog
white-board for the sprint backlog
daily estimation of time-remaining
sprint burn-down chart
Executing the Sprint
allocating tasks
daily stand-up meeting15 minutes
common language
impediments
sticking to the sprint backlog
white-board for the sprint backlog
daily estimation of time-remaining
sprint burn-down chartmove stories in/out
(http://en.wikipedia.org/wiki/Scrum_(software_development))
(http://en.wikipedia.org/wiki/Scrum_(software_development))
Sprint Retrospectiveproduct owner, scrum master, and
team members talk about improvements
Product Burn-down Chart
big picture of the progress
Postgame Phase
Wraps Up the Project
lessons learned
Scrum in the Project simplified version:
no scrum master; no PO; no estimation
