Requirements & Drupal: Planning for Success
September 13th, 2012
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.
In this on-demand webinar presented with Acquia, we explore best practices in project communication and associated requirements to support successful Drupal projects.
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
- Technical decision makers interested in Drupal
- Web Managers
R.J. Townsend, the NavigationArts Drupal Practice Lead presents along with Jon Riekse, the NavigationArts Director of Business Analysis. The two discuss:
- 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 can requirements help the business (non-technical) community understand how Drupal can help their organization succeed?
They cover specific requirement formats for the following common Drupal functionality:
- Structured vs. Unstructured content (and associated content types)
- WYSIWYG managed vs. plain text managed content
- CKEditor customization
- Block configuration and reusability
- Non-functional requirements
- Browser support / progressive enhancement / responsive design
- 508 Compliance
- D6 to D7 migrations