10. and Effective
For each of these, I’ll describe principles and practices that
relate... show how and why they’re not easy but why they
contribute to success.
Many items could appear in different headings and they inter-
relate.
That’s why principles matter....
11. Disciplined
Pair programming, testing and continuous
integration
Unambiguous definition of done
Continual refactoring
Standups and retrospectives
Cavalier attitudes can not survive (no place to
hide)
Ironic that some orgs feel agile only applies with talented
developers but also accuse devs of wanting agile so they can be
reckless
12. Processes together form a
rigorous structure within
which to work
Broken builds, style monitors, continuous peer review, etc....
13. Sustainable
Not just iterative (mini-waterfalls)
Balance of short and long term
Scope control limits waste
The Agile Contract
No need for heroes
Scrum as mini-waterfalls
14. The team selects the
processes, empowering them
and making it sustainable
Collective ownership of project and process allows team to buy in
and look to make things work over the long run for all
stakeholders. Broad team means broad ownership and shared
success.
15. Grounded in Reality
Yesterday’s weather
Clarity of actual progress
Adaptive planning, evolutionary architecture,
emergent design...
Actually adaptive/evolutionary everything
We’re not just order takers
Opportunities come from being responsive
16. Embracing and exploiting
opportunities as they appear
and dealing with issues as
they arise
How much more effective can you be?
18. The Knitted and Lego Castles
Elegant, unified whole, but unravels with change. Again, team,
systems and business models. We live in a world that requires us
to change.
