Слайд 3The Product Owner
Responsible for the product backlog
and maximizing the product
ROI.
Represents the users
Clearly expresses backlog items
Orders them by value
Ensures visibility
Слайд 4The Development Team
Responsible for delivering a
potentially shippable
increment of working
software.
Self-organized
Cross functional
Developer as title
Defines practices
4 to 9 persons
Слайд 5The Scrum Master
Responsible for the scrum process
Removes impediments
Facilitates scrum events
Facilitates
communication
Слайд 6The Product Backlog
Single source of requirements
for any changes to
be
made to the product.
Living list that is never complete
Ordered: value,
risk, priority & necessity
Estimated by the team
Слайд 7The Definition of Done
Used to assess when work
is complete
on the
product increment.
Defined by the product owner
Unique for the whole
team
Must allow immediate release
Quality increases with maturity
Слайд 8The Sprint Planning
Two part time boxed meeting: 8h/1m sprint.
Defines
what will be delivered in the increment
Team selects items from
the product backlog
and defines a sprint goal
Defines how the increment will be achieved
Items are converted into tasks & estimated
Слайд 9The Daily Scrum
15 minute time-boxed event for the Team
to synchronize
activities.
What has been accomplished since last meeting?
What will be done
before the next meeting?
What obstacles are in the way?
Слайд 10The Sprint Review
4 hour time-boxed meeting
Product owner
identifies what has been done
Team discusses what went well, what
problems it
ran into & those that were solved
Team demonstrates what it has done in a demo
Product owner discusses the backlog as it stands
Entire group collaborates on what to do next
Слайд 11The Sprint Retrospective
Improves the
process.
Inspect how the last Sprint went
Identify and order the major
items that went well
and potential improvements; and,
Create a plan for implementing improvements
Слайд 12Further Reading
The Official Scrum Guide
http://www.scrum.org/