AT12	
Concurrent	Session	
11/9/17	3:00	PM	
	
	
	
	
	
Resolve	the	Contradiction	of	Specialists	
within	Agile	Teams	
	
Presented	by:	
	
Steve	Berczuk	
Fitbit	
	
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/
Steve	Berczuk	
Fitbit	
	
A	principal	engineer	at	Fitbit,	Steve	Berczuk	leads	a	quality	infrastructure	and	
engineering	team	which	builds	tools	and	provides	coaching	to	help	teams	deliver	
features	effectively.	Steve	is	a	software	developer	and	manager	who	is	
passionate	about	helping	teams	deliver	effectively	by	helping	to	solve	technical,	
process,	and	people	management	problems.	A	ScrumMaster	and	agile	software	
configuration	management	expert,	Steve	is	a	frequent	contributor	to	TechWell	
and	author	of	Software	Configuration	Management	Patterns.	Read	Steve's	
articles	and	his	blog	and	follow	him	on	Twitter	@sberczuk.
© 2017 Steve Berczuk

Resolve the Contradiction of
Specialists within Agile Teams
Steve Berczuk

Fitbit
1
© 2017 Steve Berczuk

About Me
People
Process
Technology
2002
2005
1995
Software
Development
Writing
© 2017 Steve Berczuk

Agenda
• Scrum Process & Principles

• Scrum and Scrum Teams

• Dealing with Growth & Kinds of Teams

• Specialization

• Questions/Discussion
© 2017 Steve Berczuk

Scrum Process &
Principles
© 2017 Steve Berczuk

Scrum Pillars and Values
Transparency Inspection Adaptation
Scrum
© 2017 Steve Berczuk

Scrum Pillars and Values
Transparency Inspection Adaptation
Commitment
Courage
Openness Focus
Respect
Scrum
Principles Practices
© 2017 Steve Berczuk

Scrum
Events
Team
Artifacts
© 2017 Steve Berczuk

Scrum Teams
© 2017 Steve Berczuk

The Scrum Team
© 2017 Steve Berczuk

The Scrum Team
Scrum
Values
© 2017 Steve Berczuk

What is a
“Scrum Team?”
© 2017 Steve Berczuk

Scrum Teams
• Accountable

• Self Organizing

• Cross Functional

• “Atomic” (no sub teams)
© 2017 Steve Berczuk

Blocking
Sprint Backlog
(Tasks)
© 2017 Steve Berczuk

T Shaped Skills
© 2017 Steve Berczuk

T-Shaped Skills
Sprint Backlog
(Tasks)
© 2017 Steve Berczuk

Reality
© 2017 Steve Berczuk

Teams and Features
© 2017 Steve Berczuk

Aside: Feature v Application
Payment
Service
Customer
Service
Fulfillment
Service
Feature
© 2017 Steve Berczuk

Aside: Feature v Application
Payment
Service
Customer
Service
Fulfillment
Service
FeatureFeatureFeature
© 2017 Steve Berczuk

Growth
© 2017 Steve Berczuk

Growth Patterns
• Architecture

• Common Components

• Location

• Teams in multiple locations

• Multi Location Teams (?)

• Technical and Domain Specialization
© 2017 Steve Berczuk

Teams and Components
© 2017 Steve Berczuk

Components & Features
© 2017 Steve Berczuk

Component Team Backlogs
Capacity
© 2017 Steve Berczuk

Dependencies in Time
Plan
Work
WorkFeature Team
Component Team Plan
Other
Work
Other
Work
© 2017 Steve Berczuk

Teams and Specialties
iOS
iOS
© 2017 Steve Berczuk

Teams and Specialties
iOS iOS
?
© 2017 Steve Berczuk

Specialization
© 2017 Steve Berczuk

These are all
Engineering Skills
© 2017 Steve Berczuk

Expertise,
Training & Learning
© 2017 Steve Berczuk

Specialists: Options
© 2017 Steve Berczuk

Embedded Specialist
?
© 2017 Steve Berczuk

Specialist Component Team
© 2017 Steve Berczuk

Specialist Component Team
Backlogs
Capacity
© 2017 Steve Berczuk

Consulting Model
© 2017 Steve Berczuk

Consulting Model
© 2017 Steve Berczuk

Balance
Commitment
Team Cohesion
Bandwidth Efficiency
Communication
Reuse
© 2017 Steve Berczuk

Scrum Pillars and Values
Transparency Inspection Adaptation
Commitment
Courage
Openness Focus
Respect
Scrum
© 2017 Steve Berczuk

Specialist Teams
© 2017 Steve Berczuk

Specialist Teams
© 2017 Steve Berczuk

Specialist Teams
© 2017 Steve Berczuk

Specialist Teams
© 2017 Steve Berczuk

Specialist Teams
© 2017 Steve Berczuk

Specialist & Team Backlogs
Rotation or
% Allocation
© 2017 Steve Berczuk

Specialist Teams
• Embed with Scrum Teams for multiple sprints

• Train, Coach, and Build Infrastructure

• Identify Common Needs Across Teams

• Share Knowledge Across Teams

• Build Shared Tools and Frameworks
© 2017 Steve Berczuk

When?
Planning
Sprint
Sprint
Sprint
Plan
Embed
Team 1
Embed
Team 2
Embed
Team 1
© 2017 Steve Berczuk

Example: Test
Automation
© 2017 Steve Berczuk

Example: DBA
© 2017 Steve Berczuk

Benefits: Knowledge
Sharing
• Embedding for a period of time -> Commitment

• Sharing of knowledge and techniques

• Creation of communication channels between teams
© 2017 Steve Berczuk

Other Approaches to
shared Special Tools
• Collective Code Ownership

• Teams make changes as needed & Share (versioning)

• Internal Open Source (Specialists as gatekeepers)

• Component Team

• Need to stay close to needs/use
© 2017 Steve Berczuk

Types of Teams
Feature
Team
Feature Team
iOS iOS
Component
Component
Team
Specialist
Team
© 2017 Steve Berczuk

Things to Do
• Visualize your team’s skill set 

• Jan Beaver Visualizing Cross Functionality

• Identify gaps

• Consider how you organize teams
© 2017 Steve Berczuk

Visualization
https://coachingagile.blogspot.com/2012/02/visualizing-cross-functionality-with.html
© 2017 Steve Berczuk

Summary
• Feature Teams

• Build Features (Customer Visible)

• Component Teams

• Build Shared Components

• Specialist Teams

• Embed with Feature and Component Scrum Teams

• Most members are embedded in other Scrum Teams

• Enable Teams to forecast more accurately with less overhead
© 2017 Steve Berczuk

Questions?
© 2017 Steve Berczuk

Contact
• Twitter: @sberczuk

• Linked In: steveberczuk

• steve@berczuk.com 

• www.berczuk.com

Resolve the Contradiction of Specialists within Agile Teams