The aim of the session is to share the experiences I have had delivering large scale multi year projects using Agile as well as LEAN Agile when delivering to challenging time scales for startups or whilst rescuing projects. There is no one Agile fits all model out there, Agile is agile because of its adaptability to the ecosystem it is being used in. The 'train track' Agile mindset is something I see time and time again in agencies I am hired to manage Agile programs for, where Agile radicals forget the ethos of being Agile.

With over 16 years of experience practising Agile to deliver software products, individual client side projects and taking Agile in to non-technical environments designing and delivering International development programs there has been much adaptation to the core frameworks of the Agile methodologies I have selected for individual programs, projects and products.

Over the years I have learned which framework to use for what sort of projects and clients, be it Agile with stringent governance when working with Government departments, Agile with a just the essential governance processes with an emphasis on speed or Agile with flow control to manage multiple projects within a small team. With large non-Drupal agencies, top tier 1 consultancies moving into the Drupal ecosystem the existing service providers in the ecosystem need to compete in ways other than size! Agile is more than a framework for delivery, it is a state of being for a company and if a company can tap into that state it automatically becomes part of an elite club of service providers who learn and adapt to a fluid landscape with efficacy seldom found in any ecosystem.

The learning objectives of the session are to:
+ Assist delegates recognise patterns to determine which flavour of Agile ought to be used
+ How Agile can be successfully used in small teams where the team does not meet the 7 +/- 2 criteria or can not afford to dedicate its entire talent pool to a single project
+ How to review Agile teams when the HR policy is geared towards individualism whilst the methodology in use is geared towards collectivism
+ How Agile can be extended beyond the delivery team and used by the entire company from business development to hiring new talent, and lastly
+ How to build agility into your service contracts so that you are legally protected in a fluid environment and your clients understand the impact of Agile on contractual obligations.