How To Plan A Drupal Project

Model Method

This tutorial explains how to create a model of a project in greater and greater detail, with the final model becoming a live site.
It's writen with the idea that you're developing a project for a client, but if you're developing a site for yourself it's also useful - just think of yourself as the client.

Workflow

It's important for you and the client to have a clear idea of what is happening at each stage

Cargo Cult Development

Avoid cargo cult development
Each step should be based on the results of the previous step
There should be clear connections between elements in one step and the next
Example of what to avoid:
1) Define Users and goals
2) Add blogs as a feature - even though it doesn't solve any of the goals in step 1

Preparation

Initial planning stage where the site is modeled on paper and in documents.

Consultation

The Meeting

First step is to get information from the client about what the requirement of the site will be.
A face to face meeting with the client is vital at this stage
Schedule plenty of time for this consultation, at least a day
The client will not have a clear idea of the site's requirements, even if they think they do. It's your job to clarify the requirements.
At the start of the consultation it's important to explain to clients the process that will be followed - basically the outline of this tutorial

Avoid

Getting sidetracked
Be flexible in taking information, even if it should come at a different stage in the process, but always make sure to get back to discussing the current stage
Solutions instead of problems
The client will try to suggest solutions before a problem has been defined, e.g. adding a forum without any clear reason to do so
Client playing designer
Many clients will try to suggest designs, without having any knowledge of user interface design
Client adding useless features because other sites have them

Tools

At this stage you will need:

Notepad
Pen
Markers (several colours)
Blank cards

Not using a computer will usually make the process seem less technical and easier to follow.

Client Goals

Discuss the goals that the client is trying to achive with the project.

Write each goal on a card
Use the same colour for all goals.
Don't be too vague
e.g. "improve branding" - not useful
e.g. "associate brand with head of organisation" - useful

Users

Who?

Define who the users of the site will be.
Think about what kinds of users the client will need to attract to the site to fullfill their goals.
Write a card defining each type of user
If necessary create sub groups, one on each card, giving a more specific definition of a type of user.

Personas

To make it easier to discuss the motivations and behaviour of these users, it's useful to create personas for them - give each user type an example person, their name and a short description.

if you can think of a someone you know that fits into a user type that can be very useful.

User Goals

What?

For each user type list what their goals will be when using the site.
Write a card for each goal

In practise you will be discussing this at the same time as you define users.

Features

How?

Make a list of what features the site will provide for users to achieve their goals
Note the connection between a user-> a goal -> and a feature
Write each feature on to a card
Features can also include content

Modelling Information

Now that we've discussed with the client the who? what? and how? of their site we can start to model the information.

Tools

Model information on computer using a diagramming application

Applications

Map Information

Transfer information from cards into your diagramming application and create a map of relationships.

User & Goals
Goals & Features

Examples

Developing Features

Decide how features can be implemented in Drupal

List features

That can be implemented with existing modules
That might be implemented with existing modules
That can't be implemented with existing modules

Test modules you might use on a development site. This will be the start of the project website.

Site Map

Convert your features diagram into a site map showing sections and pages.

Then map out how user types relate to each section and page, giving you a clear view of how each user type will navigate to the parts of the site that are relevant to them.

Wireframes

Once we know how all the pages relate to each other we create wireframes for each one.

List what goes on a page then arrange the elements.
Think about creating a consitent interface accross the site.

Development

The documentation produced in the planning stage is only a starting point for development, it should be used for phase 1 of the development process, but then replaced by further consultation with the client.

Phase 1: Feature Complete Site

Develop the main functionality of the site.
Create the design of the site

Review 1

Give the client time to test out the site and give you feedback.

Phase 2: Polish Site

Configuration refinement
Appearance refinement
Functionality refinement

Review 2

Final review of project by client before it goes live.

Phase 3: Training, Documentation and Refinement

Development

Configuration refinement
Appearance refinement
Functionality refinement

Documentation

Create guide to using website

Training

Train client in use of the website

Launch Site!

Review Feedback & Behaviour

A few weeks after the project goes live analyse feedback from users and usage patterns and plan ways to improve the effectiveness of the website.

Phase 4: Post Launch Refinement

Configuration refinement
Appearance refinement
Functionality refinement