project management

This session will cover how Drupal can be used by activists, community organizers and other small teams of people (in any setting) to manage projects effectively. I'd love to discuss this with everyone interested in activism, project management and Drupal.

The session will cover:

• How activists can get the most out of Drupal by using a variety of tools
• What the Drupal community can do to facilitate better project management tools for activists
• When CiviCRM, Open Atrium and Activism Labs are each most suitable for a site

The first thing any Drupal Project Manager learns is that clients only understand the power of the system when they see it. Once you get close to a final product, suddenly the client wants more. This new imaginative phase comes partly from the learning curve of any new system, and partly from simple human nature. Indeed, we are all prone to getting our best ideas towards the end of the project. Managed poorly, this tendency can be an enormous liability on your project budget; the term "scope creep" evokes the frightening image of a project that never ends.

Over the past two years the Drupal user base has grown to include large corporations. This talk presents experiences learnt from various projects introducing Drupal and Open Source Technologies into corporations with pre-existing environments. This discussion will be aimed at:

Are you still not using Drupal to manage your projects? Since July 2009 excuses are running thin. And if Open Atrium didn’t do everything you ever expected from your project management system, it’s about time that we join forces and build our own dog food.

In this session I’ll present a review of Drupal built tools for project management. You'll get an introduction to Open Atrium and the tools we developed for Knowledge and Project management in Open Atrium.

After working some 15 years with web projects I have been both service provider and customer for a large number of different projects. I've seen and tried number of different methods how to run web projects. After both success and failure I have come to realize that agile scrum can fail just as easily as traditional waterfall models do when dealing with Drupal projects.

Drupal lends itself well to modular, separately deployable code. This means you can often reduce quite large Drupal-based projects to sets of minimum deployable features (MDFs) - informally speaking, chunks of functionality which get a particular job done, and don't look weird on their own - which quickly start to take shape as Drupal development plans.

Acquia's engineering team have been building DrupalGardens at a fast pace for the past year and now that we are heading into open beta we decided it was time to open up and share what has worked well with the community. Chris Brookins (VP Engineering), Linea Rowe (Director Product Management) and Jacob Singh (Principal Engineer) will take you through a 21-day sprint in the life of the Drupal Gardens team.

This session is for:

<

ul>

We've all seen the pattern.

Designer cleverly fills in the boxes, design looks great, client approves design, developers implement the design, site is ready to launch once we get those boxes filled in with the real conte..... What do you mean you don't have anything to go there?

As much as we love the code, great sites live and die by their content. Unfortunately, many sites are still designed and built assuming "something" will fill in the boxes. That's no way to treat your users!

Learn how to incorporate content-centric thinking into your process and: