and EffectiveFor each of these, I’ll describe principles and practices thatrelate... show how and why they’re not easy but why theycontribute to success.Many items could appear in different headings and they inter-relate.That’s why principles matter....
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 talenteddevelopers but also accuse devs of wanting agile so they can bereckless
Processes together form a rigorous structure within which to workBroken builds, style monitors, continuous peer review, etc....
Sustainable Not just iterative (mini-waterfalls) Balance of short and long term Scope control limits waste The Agile Contract No need for heroesScrum as mini-waterfalls
The team selects the processes, empowering them and making it sustainableCollective ownership of project and process allows team to buy inand look to make things work over the long run for allstakeholders. Broad team means broad ownership and sharedsuccess.
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 takersOpportunities come from being responsive
Embracing and exploiting opportunities as they appear and dealing with issues as they ariseHow much more effective can you be?