Most software development processes are focused on tracking and delivery. Unfortunately, writing code is no longer the bottleneck. The real bottleneck is the team ability to learn about the domain complexity and do the right thing.
2. About me
@ziobrando
I do something else instead
@ziobrandoAbout me
avanscoperta
#DDD
#Agile
#Lean
#Entrepreneur
#Developer
#EventStorming
#Coach
#Facilitator
#Consultant
4. In principle there
was “waterfall*”…
*Yes, I know Royce actually meant a different thing. I just need a stereotypical
villain as a starter. And no one applies waterfall the way royce intended anyway.
11. The Pink Check (Early Waterfall)
Autonomy:
Totally depending on specs
Mastery:
Overdesigning architectures
Purpose:
Let’s not screw up everything this
time!
Note to technicians: The projector isn’t broken, it’s me. ;-)
19. in Scrum…
TEAM
iteratively* delivering quality
software in sprints
Scrum Master
removing impediments
Product owner
providing clear vision and priority
ITERATIVELY*: means that you’ll rewrite existing software, when learning new stuff,
with incremental, you can pile up crap week after week.
27. And i realise the
secret desire is
predictability*
*this color is “Boredom Grey” I took some risk in choosing it before checking the
projector. I hope you can see it
42. And of course “It Depends”
There still will always be some
boring activity still labelled
“Software development”
consolidated vs new domain
Core vs non-core (supporting or
generic)
Change might be coming from the
outside, so it’s a BET
43. More specifically
In high value / High Risk areas,
learning has a clear payoff
In low value areas, you’ll be more
likely to end up doing a watered
down, tracking oriented, version of
agile.
63. Big Picture Workshop
Invite the right people
The ones with questions
The ones with answers
a facilitator
Provide an unlimited modelling space
Surface, Markers, stickies
Start Modelling with Domain Events
76. Pink Check: User Stories as spec
Autonomy:
Need to ask to the PO, anyway
Mastery:
… mmm (feeling almost insulted)
Purpose:
deliver something on friday
86. Possible strategies
Take a bike and ride it
Ask a guy that rides a bike
Read a book about bikes
Talk to a guy that knows somebody
that has a bike
Read a specification document
written by a person that probably
interviewed some bikers
87. Even worse
Take a bike and ride it
Ask a guy that rides a bike
Read a book about bikes
Talk to a guy that knows somebody that has a bike
Read a specification document written by a person that
probably interviewed some bikers
Read a specification document written
by a guy that talked with the wheels
guy, the chassis guy, the pedal guy and
the tyres guy.
98. Lessons learned
There is a window of opportunity for
asking newbie questions
…better anticipate the learning.
Looks like I am Quoting Dan North again:
https://dannorth.net/2010/08/30/introducing-deliberate-discovery/
113. On a ‘Special Day’
People take deliberate actions to
learn as much as they can
Visiting or observing real users
Engaging with real users
Talking with experts
Studying competitors
… you name it!
115. ‘impediment list’ is long
the agenda is already planned
We can’t get out of office
we’re already committed to a
schedule
We’re not supposed to do that
We’re not paid for doing that
Travelling is expensive
116. ‘impediment list’ is longer
I won’t be able to calculate velocity
any more
It’s not my responsibility to do it
136. Without a real
purpose, we’ll
find another one
introducing new technology, pretending to write great
code, maybe becoming a dungeon master one day