Thought leaders in the Agile and Traditional camps: there is very little cross-over here, so the camps are remaining separate despite the fact that projects are increasingly relying on both of these at once.

Traditionalists are now being required to join or work with Agile teams

Discussion followed up on this last theme: What Agilists and Traditionalists have in common is that they need to work together in a given organisation. Such interfaces can still exist between:

A suggestion: that we can use 3rd-party training materials, along the lines of Scott`s book Agile Database Techniques or agiledata.org website to encourage colleagues to adopt agile practices for their work. Such books are starting to appear for other cross-team functions as well (QA, SCM).

once we make them available to them, they have the choice to join and change or stay the same and pay the eventual consequences (some feel the consequence of obsolescence is inevitable).

The benefits to those who do change: job growth, enter the 21st century paradigm of iterative incremental development, become more effective in their job, benefit their organisation

Idea: do we need new contracts for people working in these traditional groups? If they are held to non-agile contracts there is no payoff to switching to agile.

Objective: bring traditionalists and their important specilisations into the agile teams.

Make educational info more available thru an Agile Reading list wiki on agilenetwork.ca

OpenSpaceWorld.ORG is funded by contributions, maintained by MichaelHerman, and open to ALL friends and practitioners. If you'd like to add to the read-only pages here, email webmaster@openspaceworld.org and say something about who you are and what you'd like to post. Then we'll tell you how!