Dogma-free Scrum. Tobias Mayer. #SGLON 2011 ... missing is something we might call. The Collaboration Space. This is bot
Dogma-free Scrum Tobias Mayer #SGLON 2011
Scrum as Process Scrum is sold as a process framework A process needs to be defined Hence Scrum Taxonomy Scrum Guide... Eventually ScrumBOK?
Defining Scrum will kill it
Attempts to define the Scrum process...
...it gets worse!
Scrum as a Way of Being Scrum can be thought of as a set of principles This approach removes attachment to terminology and instruction manuals It offers “constrained freedom”
Scrum Flow
5 Scrum Principles Self-Organization Collaboration Focus Alignment Rhythm The value of Trust underlies all five
Exercise 1 Draw a Scrum Diagram with Roles, Meetings and Artifacts and figure out how the 5 principles apply to each of these Scrum components and the interactions between them
Exercise 2 Take a real life problem one of your team has and consider how using the principles as a starting point for exploration will help to resolve the problem
The Collaboration Space Although collaboration is encouraged through dialog and meetings, what is often missing is something we might call The Collaboration Space This is both a mental and a physical space
The Weakest Link Almost all dysfunction in an organization
can be traced back to the inability to make clear requests
Lack of clarity leads to expectation, frustration and resentment Creating a Collaboration Space can help
Scrum Backlog Model Product Owner
Team
Story Abcdefg Story Qwerty Story Cvfgtrh Story Abcdefg Story Qwerty Story Gthyerh Story Pgliyer Story Gytehku
WHO WHAT WHY
HOW
Request/Response Model Requester
Responder/s
Request/Response Model Requester
The Collaboration Space Responder/s
Request/Response Model Requester
The Collaboration Space Responder/s
WHY The reason. The customer. The desired value.
WHAT
The suggested solution, arrived at through requester/responder dialog and collaboration
HOW
The tools, techniques and methods the team will use to meet the request
Single Project
Vision
Why Request/s
Requester
Acceptance
Prioritization
What How
Dialog/Collaboration
Agreement
☺ ☺
☺ ☺ ☺
Response/s
Business Business value Business value value
Multiple Projects
SH
SH
Request/s
Why
SH Request/s
SH
Request/s
Request Coordination Coordinator SH SH SH SH RC
Prioritization
What How
Acceptance
Dialog/Collaboration
Agreement
☺ ☺
☺ ☺ ☺
Response/s
Business Business value Business value value
Approach Matters Right action does not necessarily lead to right thinking Scrum requires a mindshift If we let go of process, process will emerge
Tobias Mayer http://agilethinking.net
[email protected] @tobiasmayer
