Upload
dawid-pytel
View
302
Download
0
Tags:
Embed Size (px)
Citation preview
Self-organization applied
Dawid PytelSenior Software Development Manager, Kroll Ontrack
http://www.AgileManager.pl
@DawidPytel
Welcome
ScrumDays Poland 2015
2
They are self-organizing. No one (not even the Scrum Master)
tells the Development Team how to turn Product Backlog into Increments of potentially
releasable functionality;
Scrum Teams are self-organizing and cross-functional.
Self-organizing teams choose how best
to accomplish their work, rather than being directed by others
outside the team
Coaching the Development Team in self-organization and cross-
functionality;
(how Scrum Master serves the Development Team)
The Development Team self-organizes to undertake the work in the Sprint Backlog…
By the end of the Sprint Planning, the Development Team should be able to explain to the Product Owner and Scrum Master how it intends to work
as a self-organizing team to accomplish the Sprint Goal and create
the anticipated Increment.
Development Team should understand how it intends to work together as a self-organizing team to accomplish
the Sprint Goal
Self-organization in Scrum Guide
3
Self-organization can only be enabled, not enforced
We need „Enablers” - key elements of which self-organization is composed, factors which are enabling and strengthening it