It seems like everyone in the Drupal world is either succeeding at using some interpretation of Agile project management, failing at it or are looking into doing one or the other. This has resulted in all sorts of discussions around the applicability of Agile methods and ideas to web projects (that traditionally have lots of upfront design) or even wether or not Agile is the right fit for consultancies at all.

At the same time the DevOps conversation in the Drupal world is focussed mainly around new shiny tools that can promise to automate our entire workflow with a single button press so that we can all go to pub.

This session takes a step back in both perspective and time and looks at the Agile principles as they were originally written - from the software developer's perspective - and how a refocussing on these ideas is a clearer path to healing the business/technology divide.

It will focus on how to really get the most out of your development teams using Agile ideas and methods (mainly XP, Scrum and Kanban) focussing primarily on the first principle in the agile manifesto and how it relates to the DevOps concept of culture (the C in DevOps CAMS).

Along the way we will explore some of the latest practices to improve both customer interactions and developer interactions:

Improving customer interactions:

- The BDD approach
- User story mapping, feature injection, impact mapping
- The "3 Amigos" ritual

Improving developer interactions:

- Test Driven Development as a design tool and a knowledge sharing technique
- Coding katas
- Pair programming
- Developer "ease", morale and general mental health

Other topics:

- Where processes and tools should really come from
- Avoiding the tool fetish trap
- Team culture over project culture
- Moving away from command and control work assignment to a "pull" system
- Getting developers from self-organisation to self-actualisation