Scale: The Most Hyped Term in Agile Development Today

AT7
Concurrent Session
11/9/17 1:30 PM

Scale: The Most Hyped Term in Agile
Development Today

Presented by:

Dave West
Scrum.org

Brought to you by:

350 Corporate Way, Suite 400, Orange Park, FL 32073
888---268---8770 ·· 904---278---0524 - info@techwell.com - https://www.techwell.com/

Dave West
Scrum.org

Dave West is the CEO/product owner at Scrum.org. He is a frequent speaker and
widely published author of articles and his acclaimed book, Head First Object-
Oriented Analysis and Design. Dave led the development of the Rational Unified
Process (RUP) and worked with Ivar Jacobson to run the North American business
for IJI. He managed the software delivery practice at Forrester research where he
was VP and research director. Prior to joining Scrum.org, Dave was chief product
officer at Tasktop, where he was responsible for product management,
engineering, and architecture.

© 1993-2011 Scrum.org, All Rights Reserved 1
1© 1993-2016 Scrum.org, All Rights Reserved
Scale: The Most Hyped Term
in Agile Development Today
DAVE WEST @DavidJWest
CEO
Scrum.org
A man who carries a cat by the tail learns something
he can learn in no other way.
- Mark Twain
2
Improving the Profession of
So2ware Delivery

3
Dave West
Product Owner / CEO Scrum.org
Dave.West@scrum.org @DavidJWest
We will cover
1.  Scale, the hype
2.  How far does Scrum
go?
3.  How do you scale
successfully?
4.  Nexus Framework, an
introduction
5.  Scaled Professional
Scrum with Nexus
1,700,000+ Open Assessments
Taken
130,000+ Professional Scrum
CerMﬁcaMons
The Home of Scrum
90% Agile Teams Use Scrum
188 Professional Scrum
Trainers
Taught PracMced everywhere
86,000+
+12M Using Scrum Daily
One Scrum Guide
As of 9/30/2017

1.  Scale, the hype
2.  How far does Scrum go?
3.  How do you scale successfully?
4.  Nexus Framework, an introduction
5.  Scaled Professional Scrum with Nexus
Agenda
5
When Organizations Talk about Scale they mean…
•  More people delivering working
software with an Agile approach
(scaling product delivery)
– More teams and different project
types
•  Agile growing outside of delivery
to include other supporting
functions (fixing water-scrum-fall)
– Adding Portfolio Planning, EA,
Support, etc..
Agile

•  You have an organization in
place that allows product
teams to deliver products
•  That the high level or portfolio
planning has been done
elsewhere
•  That the funding, staffing and
support functions of those
product teams is being
managed
We Assume….
Agile
We are Focused on Scaling Product Delivery

Scrum is a Key Part of ANY Scaling Strategy
•  Building on the
success of Scrum
at the team level
•  Adopting
methodologies
such as SAFe,
LeSS
One Scrum Team doing work

1
1
Nine Scrum Teams doing work
When scaling, several challenges emerge:
•  Ensuring a shared goal is understood and aimed for
•  Coordinating work across many teams
•  Allowing for self-organization while still achieving consistency
•  Releasing a fully integrated and tested Increment of software
as often as possible
•  Identifying dependencies between teams, between
components of the software, and between requirements
•  Removing or minimizing those dependencies
Challenges in scaled development

•  Identify and resolve or
minimize dependencies:
–  Ongoing & persistent
–  In all dimensions
–  Prior to work occurring
•  Reactive to ensure that
undetected dependencies
aren’t corrupting outcomes:
– Frequent integration
– Acceptance testing
– Continual build and delivery
– Minimize technical debt
Essence of Scaling Product Delivery
Anticipation* Reification**
** The process or result of reifying.
Making something real, bringing something
into being, or making something concrete.
* The act of preparing for something.
A prior action that takes into account or
forestalls a later action.
Nexus Defined
Nexus –noun
ˈnek-səs
: a relationship or connection between people or things
Nexus is the exoskeleton of scaled Scrum
- Ken Schwaber

1
5
Nexus™

Scrum Framework
1
8
Nexus Roles, Events, and Artifacts
ROLES EVENTS ARTIFACTS
DEVELOPMENT TEAMS
PRODUCT OWNER
NEXUS INTEGRATION TEAM
SCRUM MASTER
THE SPRINT
SPRINT PLANNING
NEXUS SPRINT PLANNING
NEXUS DAILY SCRUM
DAILY SCRUM
NEXUS SPRINT REVIEW
SPRINT RETROSPECTIVE
NEXUS SPRINT RETROSPECTIVE
REFINEMENT
PRODUCT BACKLOG
SPRINT BACKLOG
NEXUS SPRINT BACKLOG
INTEGRATED INCREMENT
NEXUS GOAL

1
9
Nexus Roles, Events, and Artifacts
ROLES EVENTS ARTIFACTS
DEVELOPMENT TEAMS
PRODUCT OWNER
NEXUS INTEGRATION TEAM
SCRUM MASTER
THE SPRINT
SPRINT PLANNING
NEXUS SPRINT PLANNING
NEXUS DAILY SCRUM
DAILY SCRUM
NEXUS SPRINT REVIEW
SPRINT RETROSPECTIVE
NEXUS SPRINT RETROSPECTIVE
REFINEMENT
PRODUCT BACKLOG
SPRINT BACKLOG
NEXUS SPRINT BACKLOG
INTEGRATED INCREMENT
NEXUS GOAL
Scaled Scrum is Still Scrum
•  Nexus introduces new roles, events, and
artifacts
•  The Product Backlog is still the Product
Backlog
– The Product Backlog may have several levels
of decomposition
– Dependencies between Product Backlog items
should be minimized
1 Product
=
1 Product
Backlog

Nexus™
The Nexus Integration Team (NIT)
•  Purpose
– Provide transparent
accountability for Nexus
integration
•  Accountability
–  Ensure that an integrated
increment is produced at
least every Nexus Sprint

Nexus Integration Team Roles
A Nexus works
off a single
Product
Backlog
Product Owner
Accountable for maximizing value of the product, Product Owner
for the Nexus
Scrum Master
Responsibility for ensuring the Nexus framework is understood and
enacted, oden facilitates the Nexus level events
Team Members
Accountable for successful integraMon of all work by all Scrum Teams.
These are oden members of Scrum Teams within the Nexus
The Purpose of the Nexus Integration Team
•  The Scrum Teams do the integration work; however, the
Nexus Integration Team remains accountable
•  Activities
– Helps coordinate work between the teams
– Raises awareness of dependencies as early as possible
– Ensures integration tools and practices are known and used
– Serves as consultants, coaches, and communication links
– Sometimes they will even assist with the work
– Facilitates shared architecture/infrastructure
– Raises transparency

Nexus Integration Team – Modes of Working
•  Coaching
•  Consulting
•  Highlighting dependencies
•  Identifying cross-team
issues
Product Backlog Refinement Event
•  Continuous elaboration
•  Conduct regular refinement
meetings
•  Run these as time-boxed
events
– Reduces big batches
– Smoother transition across
releases
– Time to consider the problem
and solution
– Talk with SME’s outside the
Development Team
– Allows dependencies to be
discovered earlier

Cross-Team Refinement
Sprint
n
Sprint
n + 1
Sprint
n +2 …
1
2
6
5 8
7
3
4 Team A
People
Technology
Domain
Sodware
External
9
7
6
Team B
Team C
Nexus Sprint Planning
•  Purpose
– To coordinate and align all
Scrum Teams
– To create plan(s) for the next
Sprint
– To identify and manage in-
Sprint dependencies

Nexus Sprint Backlog
•  Purpose
– To provide visibility and
transparency into any and
all dependencies that exist
during the Sprint
•  Potentially a mechanism to
view all the Product
Backlog items included in
the Sprint
Nexus Daily Scrum
•  Purpose
– Make integration issues transparent
•  The output of the Nexus Daily
Scrum serves as input to each
individual team’s Daily Scrum so
they can plan their next day’s
work

Nexus Sprint Review
•  Purpose
– Get feedback on the Integrated
Increment
Nexus Sprint Retrospective
•  Purpose
– Allows for shared challenges to be
addressed via bottom-up
intelligence
•  Three parts:
1.  Representatives from each
Scrum Team meet to identify
shared challenges
2.  Scrum Team Retrospective
3.  Representatives from each
Scrum
Team meet to discuss any
actions needed for shared
challenges

You can scale as long as you continuously…
•  Identify and remove dependencies;
•  Integrate work across all level;
•  Create and inspect integrated increments
regularly;
•  Provide adequate tooling and skills; and,
•  Inspect and adapt frequently.
Continuous
integration,
build, test and
delivery test
adequacy of
effort
Ending
•  Don’t scale flaccid Scrum. Scale Professional Scrum.
•  Nexus creates connections between Scrum Teams and is the
exoskeleton of scaled Scrum.
•  At scale, Refinement is not optional.
•  Bottom-up intelligence. Solutions need to come from the
teams, not from “above.”
•  To scale, be rigorous about removing dependencies and
creating an Integrated Increment every Sprint.
•  #scaledscrumisstillscrum

Scrum.org for next steps
Nexus Guide Assessment A Workshop
And watch for the new book due out December 15th…

Scrum on!
Thank you.
Dave.west@scrum.org
@davidjwest @scrumdotorg

Scrum.org is a community. Connect.
Twi<er
@scrumdotorg
LinkedIn
LinkedIn.com
/company/
Scrum.org
Facebook
Facebook.com
/Scrum.org
Forums
Scrum.org
/Community
RSS
Scrum.org/RSS

Scale: The Most Hyped Term in Agile Development Today

More Related Content

What's hot (20)

Similar to Scale: The Most Hyped Term in Agile Development Today (20)

More from TechWell (20)

Recently uploaded (20)

Scale: The Most Hyped Term in Agile Development Today