-
1.
@kevinrutherford
-
2.
xpsurgery.com
-
3.
“agile”
-
4.
cargo
cult
-
5.
continuous
emergent
test-driven
pair
mob
slicing
YAGNI
outside-in
collective
simplicity
refactoring
-
6.
working
software
-
7.
paradigm
shift
-
8.
up-front design
late integration
test phasesilos
technical debt
layers debugger
branches
-
9.
working
software
-
10.
XP practices
-
11.
@kevinrutherford
xpsurgery.com
The MANAGERS and BAs are sent on TRAINING and CONFERENCES
They change their job titles to SCRUM MASTER and PRODUCT OWNER
They create PLANS using “STORIES” on POST-IT notes and organised into SPRINTS
But no-one remembers to help the DEVELOPERS to change too
The devs have AT LEAST as much to learn and change
In order to create a working product INCREMENT EVERY TWO WEEKS
They need to know how to...
It's a long list
None of these is easy
Most of these skills are counter-intuitive
Agile methods place working software at the centre
Everything else should be subordinate
Many “agile” transformations stop with
Stand-ups
Post-its on a wall
3 amigos
If you focus on measuring ROI or management, you miss out on the biggest throughput boost...
..which is helping your DEVs with this huge paradigm shift
You may get SOME throughput improvement by moving to more frequent releases, but..
...if your devs still do these
Your “agile” will never fly
Many devs only know how to work this way
Many think of the XP PRACTICES as COUNTER INTUITIVE
So next time you implement agile, remember it's all about...
Without that you would have NOTHING TO MANAGE
Don't just train your managers and BAs...
Find someone who can mentor your devs for at least the first 6 months
Because if you don't, BDUF will DERAIL your “agile”
