At DrupalCon Chicago this past week, there was a "Core Conversations" session track, made up of sessions pitched by contributors to the core Drupal project. A wide range of topics were covered from the Butler project (a new system for context and blocks), to the built-in Help system, to Deployment strategies, to redesigning the issue queue. These sessions were shorter presentations followed by a discussion period for the attendees to give input on the topics.
When we started transitioning into using an Agile development method just over a year ago, one of the first and most constant challenges we ran into was how to make it work for our clients. Agile has been a fantastic tool for defining internal processes that really work for us at Affinity Bridge. Many of our clients, being non-profit organizations and academic institutions, however, are accountable to boards who have to review and approve their budgets ahead of time. They're not able to bill according to work done during agile sprints, without having budgeted for the work ahead of time. Here are a few tips from the lessons we've learned for doing agile development while managing estimates and budgets in a way that works for our clients.