Академический Документы
Профессиональный Документы
Культура Документы
Scrum Origin
Ken
Schwaber
Jeff
Sutherland
Ken Schwaber and Jeff Sutherland wrote the Scrum Guide. Together,
they stand behind the Scrum Guide, which can be downloaded in
multiple languages from http://www.scrum.org/Scrum-Guides
Scrum Pillars
Transpare
ncy
Inspection
Adaptatio
n
DAILY
SCRUM
WORKING
DAYS
High Priority
SPRINT
2-4 Weeks
Low Priority
SPRINT
BACKLOG
PLANNING
PRODUCT BACKLOG
REVIE
W
RETROSPECT
IVE
FINAL
PRODUCT
ACCEPTED
PROJECT
COMPLETE
SHIPPABLE
PRODUCT
INCREMENT
Scrum Roles
Product
Owner
Ensure and
maximized the
ROI for the
customer from
the work of the
Team.
Scrum
Master
Development
Team
Product Owner
Development Team
Scrum Events/Ceremonies
Sprint planning
Daily Scrum
Sprint review
Sprint retrospective
Sprint Planning
The purpose of the sprint planning meeting is for
the team to commit to the completion of a set of
highest-ranked product backlog items.
These commitments define the sprint backlog
These commitments are commonly referred to as
user stories
Daily Scrum
The daily stand-up is for and about the team and its commitments. In
this meeting, the team checks in on how their work is progressing in
the sprint, adjusts plans and gets assistance with removing
impediments.
Every day, same time, same place, same people. This provides a regular
rhythm and cadence on everyones calendar. The meeting last no more
than 15 minutes.
Sprint Review
Held at the end of sprint to inspect the increment and adapt the product backlog
if needed
Scrum team and stakeholder collaborate and review what was done in the sprint
Elicit feedback
Sprint Retrospective
The sprint retrospective occurs after the sprint review and prior to the next
sprint planning meeting
This is a three-hour time-boxed meeting for one-month sprints. Proportionately
less time is allocated for shorter Sprints
The purpose of the sprint retrospective is to:
Inspect how the last sprint went with regards to people, relationships, process,
and tools
Identify and order the major items that went well and potential improvements
and,
Create a plan for implementing improvements to the way the Scrum team does
its work
Scrum Events
Iteration 1
2 Weeks
Backlog
Creation
Iteratio
n1
Plannin
Backlog
g
Refineme
nt
Iteration 2
2 Weeks
Iteratio
n1
Review
Retrospec
tive 1
Iteration
2
Planning
Backlog
Refineme
nt
Daily Stand-up
Release
Plannin
g
Release
Plannin
g
Iteratio
n2
Review
Retrospec
tive 2
Relea
se
Scrum Artifacts
Product Backlog
Sprint Backlog
Increment
Product Backlog
Higher
Priority
Lower
Priority
Product Backlog
Sprint Backlog
Product Backlog
Sprint Backlog
Product Increment