The Agile-Traditional Development Cooperative

In large organizations, it is simply not practical to just "flip a switch" and have your development department start doing full-on agile all at once. Newer agile teams and more traditional or waterfall teams find themselves having to work together during a long transition period or even permanently. Whether your agile-traditional project is dealing with waterfall-up-front (a project approval process), waterfall-at-end (separate system testing), or waterfall-in-tandem (products so complex that multiple teams work together to complete a release), Michele Sliger presents techniques she has used to make coexisting less painful and more productive. Find out the specific points in the project where agile and traditional teams must plan their work together. Learn the special techniques you can use to coordinate ongoing efforts of all participants and ways to review and understand each other's work patterns and artifacts. Because not all companies will move every software development project to the agile paradigm, the agile-traditional cooperative is even more important to master.

• How agile and traditional teams can work together in harmony
• The three principles of successful coexistence
• Ten keys to cooperative success between agile and traditional