DrupalCampNYC 10

Saturday 12 · 10 · 2011

Building Beauty on Deadline: Project Management, Development, and Deployment When All Hands are On Deck

This session is a comprehensive case study of the re-launch of the site for Studio Daniel Libeskind (master planner for the Ground Zero memorial and redevelopment). The designer-driven project meant special challenges for overall theming and presentation in mobile devices.*

We will provide an informative and thorough case study of the highs and lows, highlighting what worked and what was learned from what didn't work. Business and planning practices will be open to inspection as well as code, and we invite interrogation and critique in the closing discussion portion of the session.

This session was well-received in Pacific Northwest Drupal Summit in October 2011 (unfortunately sessions there were not recorded, but here are the visuals and notes). This is our premier presentation for Drupal's premier December event, and we will pull out all the stops to cram it with practical knowledge. As a case study session, the focus will be on how things really work, not an ideal model. It will also cross all tracks: Site Building, Development, Presentation, Business & end users, Sysadmin & performance, and especially the somewhat missing Project Management.

This session will answer:

  • How large a project can a small team handle?
  • How does a fluid team (core plus hired talent) do feature triage, dividing up tasks, and effective use of Redmine project management?
  • What development practices will save you time (also known as money) and are must haves for effective collaborative development, especially for remote teams?
  • Why does User Centered design works and how do you integrate the principles into your development process?
  • What to do to make an innovative design that makes responsive design difficult shine on tablet, iPad, iPhone, Android, and Blackberry devices?

*(Mobile and tablet versions will be complete in late November. As will be presented, the design and timeline of the site prevented responsive, mobile first development.)