The document discusses the role of a Scrum Master and whether it should be a full-time role. It describes Scrum Masters as facilitating the Scrum process and helping the team adhere to practices. It also notes challenges with scaling Scrum in large enterprises and balancing the various duties of a Scrum Master like daily stand-ups, retrospectives, and impediment removal. The document considers whether the role needs to transition over time from full-time to part-time as the team matures.
4. Scrum is an agile framework for
completing complex projects. Scrum
originally was formalized for software
development projects, but works well for
any complex, innovative scope of work.
The possibilities are endless. The Scrum
framework is deceptively simple.
…No matter which impetus stops work,
Scrum ensures that the most valuable
work has been completed when the
project ends.
“”
What Is Scrum
(Scrum Alliance)
Scrum
Defined
“
5. Deliver the Right Stuff
at the Right Time
Image: http://img.ehowcdn.com/article-new/ds-photo/getty/article/129/186/86481282_XS.jpg
Deliver Stuff Right
7. Scrum
Master
Defined
The Scrum Master is responsible for
ensuring Scrum is understood and
enacted. Scrum Masters do this by
ensuring that the Scrum Team adheres to
Scrum theory, practices, and rules. The
Scrum Master is a servant-leader for the
Scrum Team.
The Scrum Master helps those outside the
Scrum Team understand which of their
interactions with the Scrum Team are
helpful and which aren’t. The Scrum
Master helps everyone change these
interactions to maximize the value created
by the Scrum Team.
“
“”The Scrum Guide, 2011
19. Reality of Enterprise Teams
Customer
Development Teams
Product Owner/s
Scrum Master/s
Or Agile coaches
Management
Other Internal Teams
Outsourced Teams Offshore Teams
Part Time /
Working
From Home
21. Upfront
project
planning
process that
typically
happens
between IT
and the
business.
Iterative and
adaptive
approach to
achieving the
overall plan
that was first
laid out in the
'Water' stage.
Controlled,
infrequent
production
release cycle
that is
governed by
organizational
policy and
infrastructure
limitations
Water Scrum Fall
Water-Scrum-Fall
42. Practices
Principles
Values
Working solutions
Human interactions
Customer collaboration
Responding to change
Co-location
Daily standup
Iteration Planning
Customer Showcase
Retrospective
Adaptive release plan
Cross functional team
Requirements as stories
Planning / story wall
Informative workspace
Burn up/down charts
Parking lot diagrams
Success sliders
Relatively sized work
One piece flow
Kanban
Definition of done
Refactoring
Continuous integration
(Acceptance) test
driven development
Automated deployment
Incremental design &
architecture
Domain driven design
Technical spikes
Exploratory testing
Collective code
ownership
Ubiquitous language
Crafstmanship
Team Practices Team Practices
Image:http://www.lawtonps.org/schools/lta/img/wallpapers/1.jpg
Simplicity
Transparency
Frequent delivery
Customer involvement
Technical excellence
Teamwork
Self organisation
Emergent design
Continuous
improvement
Sustainable pace
Servant leadership
Agile Knowledge
43. Administrative MasteryAdministrative Skills
■ Storywall Organisation
■ Work Area
■ Booking Workshops /
Meetings
■ Collecting metrics
■ Tool organisation
■ Wiki gardening
■ Skilful use of pens, paper,
scissors, sticky tape, blu-tac
Image: http://www.warrelics.eu/forum/military_photos/field-equipment-accessories-3-
reich/270586d1322432055-allo-allo-c0083506-telephone_switchboard_operator-_1914-spl.jpg
44. Skillset Mastery
■ Mastery of core domain:
software development /
testing / business analysis /
project management
■ Knowledge of other domains
in team
■ Knowledge of business
domain to facilitate
communication with Product
Owner
Image: http://www.archerysa.org.au/assets/console/news/images/main/sue_indoor.jpg
45. ■ Techniques: Brainstorming,
Affinity Mapping, Wisdom of
the Crowd, Icebreakers,
Futurespectives
■ Achieving session goals and
objectives
■ Being neutral / impartial
■ Keeping focus
■ Achieving concensus with
conflicting priorities and
opinions
■ Keeping decisions and
actions visible
Image: http://upload.wikimedia.org/wikipedia/commons/thumb/0/03/Flipchart1-Asio.JPG/220px-
Flipchart1-Asio.JPG
Facilitation Skills
46. ■ Learning Models: Shu Ha Ri,
Graphic, Audible
■ Matching learning to
content and audience
■ Teaching through
demonstration: “Training
from the Back of the Room”
■ Games: Innovation Games,
Gamestorming, Tasty
Cupcakes
■ Mentoring post-training
■ Alternative delivery
methods
Image: http://backontrack.org/images/30y/30y2.jpg
Training Skills
47. Coaching Models:
■ GROW Coaching Model
■ PrOpER Coaching Model
■ Results Coaching Model
■ 3 days, 3 things, 3 weeks
■ Integral (AQAL) Model
■ CLEAR Model
Image: http://farm4.static.flickr.com/3460/3860609433_fe1e31803d_o.jpg
Coaching Skills