Prioritised CMS Requirements for Greenpeace UK

Projects | Tools & Techniques

About a month ago, I posted the list of six activities the Greenpeace UK web team and I plan to perform by the beginning of June. So far, we've completed the first three:

• We've defined and prioritised the organisational/team objectives we're undertaking the CMS project to achieve
• We've identified and prioritised the user types we're undertaking the CMS project to serve
• We've defined and prioritised our CMS requirements given the above

We've also chosen the 3 open source CMS products we plan to evaluate given our prioritised requirements, and they are (in alphabetical order):

1. Drupal;
2. OpenACS (or rather, the current Greenpeace International implementation of OpenACS, "Planet 2"); and
3. Plone

Our next step, then, is to reach out to members of each of these communities, and to ask for their help as we conduct our evaluation. Specifically, we're looking for consultants from each community to take us through a demonstration of each respective system, so we can score all 3 based on how well they meet each of our critical and high priority requirements.

So without further ado, our prioritised requirements: Prioritised CMS Requirements for Greenpeace UK (741 KB)

If you're an experienced Drupal or Plone shop (we'll work with Greenpeace International on the Planet 2/OpenACS front) and are interested in working with us on this, please comment here or send me an email — rob[at]importantprojects[dot]co[dot]uk.

And thanks!

projectmanagement, softwaredevelopment, nptech, importantprojects, greenpeace, prioritise, open source, cms, requirements

Posted by Rob at 10:03 PM