(SDD) Flow PDF

@aahoogendoorn | @kimvanwilgen | Flow | SDD
Flow
The official worst software development methodology in history
Sander Hoogendoorn | Quby | ditisagile.nl | @aahoogendoorn

Kim van Wilgen | Schuberg Philis | @kimvanwilgen
Next
Sander Hoogendoorn
Freelance new-agile coach, trainer,
programmer, speaker, author, traveler, dad
Currently
Chief Architect Quby
Before
CTO ANVA, CTO Klaverblad Insurances
Global agile thoughtleader Capgemini
sanderhoogendoorn.com
aahoogendoorn
aahoogendoorn
sander@ditisagile.nl
Next
Kim van Wilgen

@kimvanwilgen
19 Hello
world 20 Head of IT
Klaverblad 20 Head of
development 20 Customer
director
80 14 Insurances
17 ANVA
18 Philis
Schuberg
A short history of methodologies

From waterfall to sociocracy
Waterfail
Click here

Click here

Click here

Click here

Fragile agile
Agile == Scrum?
Click here
Click here

Agile beyond building software?
Click here
Is agile dead?
Click here
Quotes from agile conferences
“Make sure you don’t miss the agile elephant versus the
waterfall elephant in the lobby.”
“During this session we are going to discuss the Happiness
Index of projects.”
“Add Ready for Celebration before the Done column on
your Kanban board”
Click here
More and more, I’m coming to see

the term “Agile” as both unnecessary
and self defeating. Agile has come to
mean “do part of Scrum badly and
Allan Holub use Jira.” Let’s just drop it.
Click here
Introducing Flow
The official worst modern software development methodology in history
Why yet another

methodology?
Click here
Agile beyond the hype
Click here
Naming our methodology
We need Japanese words
Kaizen, Kanban, Obeya, Origami
It needs to end with cracy
Holacracy, Sociocracy, Idiocracy
And it needs to be Continuous with a D
Discovery? Disappointment? Disagreement?
Click here
More #No
and Less Yes?
#NoOps
#NoProjects
#NoEstimates
#NoSQL
#NoTesting
#NoCode
Serverless
Pointless?
Click here
As a service?
SaaS
IaaS
PaaS
TaaS
XaaS
Click here
We propose
Methodoloy
as a Service
Click here
Flow
Because it
nicely fits
laptop stickers
Click here
We’ll keep sprints

We are all Usain Bolt right?
The red sprint anti-pattern
Click here
We need good estimates!

So let’s elaborate…
Click here
We need gamification
So people from outside our industry will understand too
Autonomy on a leish
Our teams can be autonomous,
but…
• They don’t get to hire people
• They don’t get to fire people
• They don’t do appraisals
• They don’t decide what they
work on (it has to be on the
backlog)
• They don’t get to spend
money
Read more …
Autonomy on a leish
Our teams can be
autonomous, so …
• We decide what’s on the
backlog
• We decide who’s on which
team
• We decide what tools
they’re using
• When they have meetings
Read more …
But.. they get to decorate their workplace!

Just like at home?
Mandatory
• Maybe we’re overdoing it a little?
fun
We play games
20% of our working days
Bring your own controller
Click here
Teams and roles … and resources

Small
• Do we mean 7 plus or minus 2?
teams?
Roles in Disciplined Agile 2.0 (outside of the team)
Functional manager
Chief product owner Database administrator
Enterprise architect
Human resource manager Governor
Chief architecture owner

Community of practice
lead Product manager
Portfolio manager Support manager
Release manager
Operations manager Process manager

Support engineers
Process engineers Release engineers
Operations engineers
Click here Reuse engineers
Our annual SAFe Quiz
Where’s the customer?
Click here
Resources
Managers are used
to calling people
If you want to become resources anyway,
a real resource, so why bother
you need to grow a beard trying to change that
Click here
Where’s
Agile coaching?
the code?
Agile coach camps
Agile retreats
Agile leadership
weekends
Click here
DevOps?
DevOps!
Click here
OpsDev
OpsDev means front-loading
Ops considerations – relating
to applications’ operability,
security, scale etc. early on in
the process.
Read more …
SecDevSecOpsSec
But where are the analysts?
Testers?
Project managers?
Read more …
“I picked ‘DevOpsDays’ as Dev and

Ops working together because ‘Agile
System Administration’ was too long,”
Patrick Debois he said. “There never was a grand
Founder of Devops
plan for DevOps as a word.”
Click here
Flow’s collaboration mindset
Community – Development – Operations – Analysts – Security
ComDevOpsAnalSecs
Resources
Res
Click here
Meetings
Meetings break flow, so they’re good
Stand-ups
The good
They are boring
Everybody loves them?
They break developer flow!
Read more …
Stand-ups
The bad
Absolutely useful meetings
But… far too often
We don’t want people to
know what other people are
doing
Read more …
Stand-ups
So
Yes, but once a week
About one hour
Every Tuesday from 9PM to
1AM
Read more …
Retrospectives
The good
They’re only once a month
We can loose lots of time
trying to prepare demo’s that
will fail anyway
Read more …
Retrospectives
And then
Tedious discuss for at least
two hours with the whole
team why we could have
gone faster
So, we keep them, but …
Every two weeks!
We don’t follow up on
improvements so we can And, yes we definitively
repeat endlessly
needed a LEGO reference
Read more …
In flow
Breaking flow
So
In Flow we organize random
meetings throughout the week
With random topics, such
design sessions, UI meetings
with the customer, stakeholder
meetings
About an hour and with the
whole team
We call these flow meetings
(as they break flow)
Read more …
Flow in the enterprise

This is where the real money is ☺
Agile == Scrum?
Scrum Guide Quiz
Manager
Autonomous
Project manager
Project
Stakeholder
Product owner
User story
Planning poker
Tester
Read more …
Does agile scale?
Click here
Or does large scale agile require a large scale process?
Click here
Sociocracy?
Click here
Let’s all copy Spotify!
Click here
Big Flow Framework (BFF) 3.0
BFF will feature
3.0, similar to Management 3.0
and Sociocracy 3
Release planes
Role based pattern matrix
Similar to SAFe we add more
complexity with each new
release
And … of course we copy
Spotify
Read more …
Tooling
We need boards – lots of overly complicated boards of-course
Flow boards
We need boards!
We’ll have so many boards that our
clients will not even try to
understand what our progress
really is
Boards are required
to have at least 20 columns
In Enterprise Flow you are required
to have a special room for your
boards called the board room
Read more …
Boards
Jira
Jira == agile
So Jira is mandatory
You will both have a Scrum
board and a Kanban board
You will use epics, stories
and tasks randomly
Read more …
Boards
Progress? What progress?
A chart showing your
progress is generated for you
by Jira
We call it a burn chart as
they usually do not go down
anyway and you burn money
in the project
Read more …
Burn chart
There really isn’t any progress, but we burn money anyway
More …

Obeya rooms
At its core, obeya (Japanese
for “big room” or “great
room”) is a dedicated room
for employees to meet and
make decisions about
specific topics
A room to put your pitiful
burn charts on a wall
A room to keep agile coaches
busy, when no-one wants to
be coached any more
Read more …
Communication
Resources
need to stay in flow
at all times
Click here
Open Floor Plans

Or how we’ve become the
company’s brochure
Click here
If you want to become In Flow

a real resource,
you need to get a tattoo Resources
are required to wear
noise cancelling
headphones
Click here
In Flow 2.0
We are experimenting
with augmented reality
glasses too
… but it appears that
they find it hard
to see the code
Click here
Slack
Resources need to stay in flow
So, resources do not directly
communicate with each other
Communication between resources
only takes place via Slack
Occasionally resources are allowed
to do pair slacking
There is one Slack channel per
release so we can track bugs directly
to Slack conversations between
resources
Agile coaches may act as thread
police
Read more …
On manifestos
Continue
Manifesto
A published
verbal declaration
of the intentions, motives
or views of the issuer.
Click here
A brief history of technical manifestos
GNU 1985
Hacker 1986
Agile
manifesto
2001 Software
craftsmanship
manifesto Agile HR
2009 manifesto
2017 Rugged
manifesto TBA
Click here
Click here
Flow manifesto
Extensive certification over hands-on experience
Copying methodologies over thinking for yourself
Tool-driven confusion over building working software
Endless meetings over individual flow
Mandatory gamification over authentic autonomy
That is, while we ignore the things on the right, we do the things on the left
Click here

Flow microfesto
Extensive certification over hands-on experience
Copying methodologies over thinking for yourself
Tool-driven confusion over building working software
Endless meetings over individual flow
Mandatory gamification over authentic autonomy
That is, while we ignore the things on the right, we do the things on the left
Click here

Certification
How to make money from creating a methodology
Certification
Why?
To make sure that we have real
professionals in our teams
Well, we need to make money too
In Scrum
CSM, PSM and CPO are two-day
courses
You take a multiple choice exam
And you are ready to go and coach
teams
Read more …
Flow certification
Yes, you can become a Certified
Flow Resource (CFR) too!
In our courses
Learn how to rip-off post-it notes
Learn how to move items on a Jira
board
Learn how to decorate your
workplace
Two day courses? Why not one
day?
Why not a one-hour presentation?
Read more …
Flow certification
Exams
Exams are made easier. We don’t
want people to fail them
So everyone from outside the
industry can come in too
3 multiple choice questions are
sufficient
Project managers?
We will have certification for project
managers!
We don’t want to leave them out in
the cold just as these agile folks did
Read more …
Certification
Are you ready to take the Certified Flow Resource (CFR) exam?
1. What roles do we have in Flow?
A. Manager, project managers, product owners
B. We are all one team!
C. Lots and lots - except for testers of course
D. Resources
Click here
2. What’s the goal of retrospectives in Flow?
A. To interrupt the daily flow of our resources
B. To endlessly discuss why the resources in our
project should work harder
C. To make sure we spend two days preparing demo’s
D. To watch demo’s fail together with our clients
Click here
3. We have certification in Flow because?
A. We want well-trained resources in our projects
B. It makes our methodology look important
C. Flow is so complicated you need lots of training to
become an expert
D. We want to make money
Click here
Congratulations!
You all passed!
Click here
Certified Flow Resource
Participating in the exam

During SDD London 2019
May 21th, 2019

By the way
There is an annual
continuation fee of
200 euro
Click here
In retrospective
Here’s what we
really believe
Click here
We believe
Software is built by people
Click here
We believe
Every organization or team
will create and evolve the
approach that fits them best
Click here
We believe
Personal communication
is still key
Click here
We believe
Trust and personal safety
rule
Click here
We believe
Creating software
requires
focus and flow
Click here
We believe
Continuous learning
is essential
Click here
We believe
Teams need to be(come)
truly self-organizing
Click here
We believe
Organizations need to be
flat with as little hierarchy
as possible
Click here
We believe
Experience
is more important
than certification
Click here
And never forget to have fun
Next
References
and questions
ww.sanderhoogendoorn.com
www.kimvanwilgen.com
aahoogendoorn
kimvanwilgen
sanderhoogendoorn.com/decks-and-handouts
Click here

(SDD) Flow PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

(SDD) Flow PDF

Uploaded by

Copyright:

Available Formats

@aahoogendoorn | @kimvanwilgen | Flow | SDD

Sander Hoogendoorn | Quby | ditisagile.nl | @aahoogendoorn

Kim van Wilgen

A short history of methodologies

@aahoogendoorn | @kimvanwilgen | Flow | SDD

@aahoogendoorn | @kimvanwilgen | Flow | SDD

@aahoogendoorn | @kimvanwilgen | Flow | SDD

@aahoogendoorn | @kimvanwilgen | Flow | SDD

@aahoogendoorn | @kimvanwilgen | Flow | SDD

More and more, I’m coming to see

Why yet another

We’ll keep sprints

We need good estimates!

@aahoogendoorn | @kimvanwilgen | Flow | SDD

Teams and roles … and resources

Chief architecture owner

Operations manager Process manager

Where’s the customer?

“I picked ‘DevOpsDays’ as Dev and

Flow in the enterprise

@aahoogendoorn | @kimvanwilgen | Flow | SDD

Open Floor Plans

If you want to become In Flow

@aahoogendoorn | @kimvanwilgen | Flow | SDD

@aahoogendoorn | @kimvanwilgen | Flow | SDD

Participating in the exam

May 21th, 2019

And never forget to have fun

You might also like