At DrupalCamp Toronto 2014 I talked to you about Change Management, and asked you to look inside yourselves to see why you should stick around for Drupal 8. At DrupalCon Austin I gave a variation on this talk as a core conversation. (I used the "F" word.) You can review the decks I gave for these presentations if you're interested. Now it's 2015 and you're (still) here. Yay!
In this session, Managing Change, you'll learn the steps needed to support a team through their first (Drupal 8) development project; however, the lessons can be applied to any team who is developing outside of their comfort zone.
Specifically, we'll talk about how to:
Structure an Agile schedule to ensure the best possible relationships between developers and stakeholders, through radical transparency and by breaking down a project into achievable components.
Mitigate the learning curve of a new platform by building on existing best practices, and limiting the avalanche of new information through just-in-time learning.
Keep each person on the team motivated and in the zone by customising how you engage, and by addressing--head-on--the anxiety which comes from building software when it feels like all your tools have changed.
The lessons are based on my own real-life experiences overseeing teams as a technical project manager with developers who were working with new technologies. From this session, you'll get practical take-aways as well as food for thought on how to succeed at one of the most difficult parts of software development: the people.