Most systems that fail do so due to a lack of planning.
You must fully document your plans and your planning process. You should include:

1. Objectives and Evaluation Criteria

You should produce a list of clear, measurable objectives that your project must satisfy. These will be your 'Evaluation Criteria' that you will use later to assess the success of your project. (see notes)

2. Tasks and Sub-Tasks ('Chunking Down')

You must break the project up into the different tasks that need to be done and the separate smaller sections (Sub-Tasks) that make up these tasks. (see example)

3. Formal Project Management Techniques

You should use at least two of the following techniques to plan your project:
Note - Don't forget to include time for data gathering at the start plus testing and error correction at the end.

  • Mind-Mapping ('Spider Diagrams')
    This would be a useful way of recording initial ideas at a team meeting.
  • Critical Path Analysis
    Take each Task and Sub-Task identified earlier and decide how long it would take and which other Tasks or Sub-Tasks it is dependent upon. When assessing the length of time it would take, don't forget to consider the resources that will be used (people, equipment, etc.) - remember, the same resource cannot be used for two tasks at the same time. (click here for help)
  • Gantt Charts
    Use a spreadsheet or a table to produce a plan of the tasks (from section 2) over time (days). Make sure that it is realistic as you will measure your progress against this throughout the project - therefore, if you are not going to do any work on Saturdays, don't plan to do so! Also, leave some 'slack' in the plan for unexpected elements. (click here for help)
  • PERT Charts
    As with the Gantt Chart, take the tasks identified earlier and allocate time and dependencies. Produce a printed PERT Chart, identifying clearly each milestone and explaining the time allocation and the dependencies. Again, leave some 'slack' and make sure that the milestone numbering leaves gaps for extra tasks to be added later. (click here for help)
  • Timeline
    Plan a clear timeline for your project, clearly identifying the sequence of tasks. Make sure the planned start and finish of each task is clearly identified.

4. Design your solution

Produce outline designs for each of the following elements: (Note - This will help your evaluations later as you will be able to discuss changes that you have made to these original designs)

  • The Human Computer Interface (HCI)
    Hand-draw some neat sketches showing what you plan the solution to look like. You might choose to include a number of different ideas that you have discussed and identify the prefered choice.
  • Links / Interactivity
    Produce a tree-diagram to show the different routes through the proposed solution and other interactive elements.
  • The Programme of Events
    Don't forget that a system involves more than just the technical solution, it is also the equipment, the people, the location, the time and so on.

List the planned 'Programme' for running (not creating) the solution. (see example)

  • User Support Materials
    List the type of support materials that you intend to produce for the user(s).
    For example - Printed 'User Manual'; On-line searchable help facility; Phone support; etc.
  • Test Plan
    Identify who will be involved in testing the solution before it goes 'live' and state what their role will be. (see notes)
Unit 9 - Working to a brief
Produce a Project Plan
Project Links
Other Links