http://sched.co/9h2u Everybody wants to be a Scaled Up Lean Startup Enterprise nowadays. But do you have what it takes to be on the edge? And should you even be trying? At every conference you hear many great ideas. And you would probably like to implement some of them back at work. And yet, is this really the right moment? And have you considered if the rest of the organisation can keep up? Or even wants to? In this talk we present a way to navigate the different practices available from the Agile community. Inspired by the Agile Fluency™ Model, we show you how to start with the issues you face today, find the direction you’re aiming for, and identify the Agile practices that will help you get there. In practical terms, we’ll describe the kinds of situations, problems and issues that can be encountered, discuss what different reactions can be depending on the stage of fluency we’re aiming at, and what practices and skills might help progressing from there.

1. Choose your own Agile adventure
Wouter Lagerweij
@wouterla
Karel Boekhout
@karelboekhout
#XP2017

2. Introduction
Karel Boekhout | @karelboekhout Wouter Lagerweij | @wouterla

3. The Problem?

4. We never finish the sprint,
we always carry over stories to the next
We can’t make a Sprint in two weeks; let’s make
it three!
It's done. All I need to do is write the unit tests.
We don’t unit test much, it makes changing the
production code too difficult
Thursday? No, not on Thursday. Thursday is
merge day!
My project, my product, my scope: you’ll do the
whole &^%$# thing
Our velocity is going up? Do we get a raise now?
Retrospectives are a waste of time. Everyone
complains, nothing gets changed.
We do need to get story points for fixing this
bug! Otherwise our velocity drops!
We need to scale up. We need SAFe.

5. What should we learn next?
It depends...

6. The Problem

7. Agile Fluency™ Model
● By Diane Larsen & James Shore (2012)
● Fluency is how a team develops software
when it’s under pressure
● NOT a maturity model!
● ★★★★ not relevant for every organization

8. Start: Building Code

10. Zone 1: Focus on Value

12. Zone 2: Deliver Value

14. Zone 3: Optimize Value

16. Zone 4: Optimize for Systems

18. Agile Fluency™ & Investment

19. Investment Zone 1

20. Investment Zone 2

21. Investment Zone 3

22. Investment Zone 4

23. Agile Fluency™ & Autonomy

24. Autonomy Zone 1

25. Autonomy Zone 2

26. Autonomy Zone 3

27. Autonomy Zone 4

28. Agile Fluency™ & Metrics
Tomorrow, Ballroom D, 15:30

29. Roles’ development in different zones
Product Owner
Scrum MasterTeam
Management

30. Product Owner in the different zones
User Stories
INVEST
CCC
Acceptance Criteria
Iterative vs Incremental
The Increment
Hamburger Slicing
Velocity
Burn-up / -down
Prioritised backlog
Cycle-time and variance
Stakeholder
management
Specification by
Example
BDD
Story Mapping
Example Mapping
Portfolio planning
Personas
Lead Times
Impact Mapping
Hypothesis Driven Dev
A/B Testing + analytics
MVP
Business Model Canvas
Lean Startup
Lean Enterprise
Lean UX
Customer Journey
Cost of Delay
Continuous Business
Goals Monitoring
Product Market Fit
Data science
Wardley Mapping
Three Horizons model

31. Scrum Master in the different zones
Scrum
Kanban
Focus
WIP
King/Servant
Classes of Service
Basic KPIs
Velocity
Feature vs.
anti-feature
Interruptions
(Scrum) ceremonies
Westrum org. culture
Agile Games
Group dynamics
Team forming
Build Quality In
Root-cause analysis
Value Stream Mapping
Lead times
Failure demand
Theory of Constraints
Queueing Theory
Retrospectives variation
WSJF scheduling
Lean Startup
MVPs
Experiment Design
Impact Mapping
Communities of Interest
Coaching
Management
HR
Finance
Marketing
Complexity
Cynefin
Self management
Management 3.0
Semler style

32. Team in the different zones
Recognize conflict
Tester in team
Sprint <= 2 weeks
Automated deploy
Testing in sprint
Done means…
WIP limits at all levels
Functional vs. Technical
slicing
Pairing / Mobbing
TDD
Continuous Integration
Exploratory testing
Test automation
BDD
Pairing / mobbing
DevOps
Craftsmanship
Sprint <= 1 week
Infrastructure as code
Continuous Delivery
Single Branch Dev.
Feature Toggles
Design Thinking
Lean UX
Business Metrics
Dashboards
A/B Testing
Experiment Design

33. Management in the different zones
Invest in coaching
Focus
Goals
Priorities
Kaizen
Gemba walks
Base delivery metrics
Velocity
Lead/Cycle Time
Invest in quality
Multi-functional teams
(DevOps)
Support Iterative work
Team incentives/targets
Team metrics on
business goals
ROI
Profit per empl.
Customer
satisfaction
Product Teams
Aligned incentives
Management 3.0
Lean enterprise
Wardley Mapping
Three Horizons model
Lean enterprise
Strategy Deployment
Aligned incentives

34. In practice
1. What problems should you fix?
2. What approaches are available?
3. Which approach matches your ‘zone’?

35. In practice: Zone 1
Every time we demo at the end of the sprint, the PO doesn’t
accept a bunch of stories because they were not what he wanted

36. In practice: Zone 1
...

37. ● Ubiquitous Language
● ATDD/BDD
● Smaller steps: working Acceptance Test by Acc. Test
● DoR, Acceptance Criteria
● Results specified in too technical terms, instead of
functional
● Review is first time PO sees result
In practice: Zone 1
● Results specified in too functional terms, instead of
outcome based
● Results not measured/measurable, leaving team unable
to optimize

38. In practice: Zone 2
Development is saying it is faster,
but we still take ages to finish a project!

39. In practice: Zone 2
...

40. ● Project vs. Feature vs. Story, iterative development
● Development does not include Ops
● Testing is not automated (sufficiently)
● Ops is not automated (where’s my deployment
pipeline?)
● Development does not include Business / requirements /
stakeholders / external dependencies
● Cycle vs. Lead times insights
● Development does not include Test
In practice: Zone 2
● Project/feature is specified as specific
functionality instead of business outcome
● Project/feature is not approached iteratively:
MVP tests, track results, improve outcome,
extend horizontally

41. In practice: Zone 3
We decided to work on improvement for the 18-25 yo cohort
but after two months it turned out
we hadn’t had any impact on that group.

42. In practice: Zone 3
...

43. ● Personas not supported by user testing, PO works with
team to get data from system to support persona
behaviour theories
● Personas not supported by interviews, PO works with
UX/design to develop personas do user interviews,
market research
●
In practice: Zone 3
● No check on business results: Hypothesis Driven
Development, specify expected business results first
● Features not developed/released iteratively. MVP for
Hypothesis confirmation, later steps… later!
● Continuous Business Goal Monitoring: Use personas
and market segments as cohort groups to measure and
dashboard

44. In practice: Zone 4
...

45. In practice: Zone 4

46. Twilight Zone

47. In closing

48. #agilefluency project
● Website: http://www.agilefluency.org/
● Google Group
● Short introduction by Diana Larsen: https://youtu.be/69dsU-_EEzM
● Agile Fluency™ Game
● 3rd Agile Fluency™ Gathering @ Rückersbach Seminar Center, 4-5 October 2017
● @AgileFluency

49. Acknowledgements
● Website: http://www.agilefluency.org/
● It started with this article: http://martinfowler.com/articles/agileFluency.html
● Diana Larsen: http://www.futureworksconsulting.com/about/diana-larsen
● James Shore: http://www.jamesshore.com/

50. Karel Boekhout | @karelboekhoutWouter Lagerweij | @wouterla
Let’s keep in touch
● http://www.lagerweij.com/agileadventure