When embarking on a development project of any scale, communication and documented requirements are vital to success. The goal of requirements documentation is to clearly communicate what will be delivered and to ensure there is mutual consensus around in-scope functionality, and how the system will look and behave. The goal of technical specifications is to document how the site will be built, to map requirements to Drupal components (content types, views, fields, etc), and to provide developers with an outline of what they will be building.

In this session we explore best practices in project communication and associated requirements and specifications to support successful Drupal projects. Attendees will hear about:

• Lessons learned from past Drupal projects
• How a Business Analyst role can complement a project team
• How to think about functionality and requirement reuse when applicable
• How requirements help the business (non-technical) community understand how Drupal can help their organization succeed
• How technical specifications can help developers build sustainable, scalable websites

This is not a technical presentation, but it does cross the boundary between technical and business owners. It is intended for the following audience groups: Project Managers, Small business owners, Developers, Technical decision makers interested in Drupal, and Web Managers.