1. |
Preparation |
|
Understand the end-user’s needs: |
| |
|
Identify the actual end-users. |
|
Ask questions in the language that the users understand. For example, sketch various scenarios of which one is close to the planned solution. |
|
Remember: Few people can describe a service/project which does not exist yet. |
|
|
|
2. |
Determine WHAT needs to be done |
2.1 |
Organise this in manageable units |
|
a) Objectives |
|
b) Deliverables |
|
c) Tasks |
2.2 |
Describe each unit with reference to the SMART principles: |
| |
Spesifiek: |
What exactly is the scope? |
Meetbaar: |
How are you going to measure whether the task has been completed? |
"Achievable": |
Is it achievable? A delegated impossibility is still impossible! |
Realisties |
How long will it How long will it really take, not how long we hope it will take if we ignore all the undesirable facts take, not how long we hope it will take if we ignore all the undesirable facts. |
Tydgebonde |
A specific beginning and end; realistic target dates |
|
2.3 |
Be very exact in terms of the tasks: As long as the task has been included, resources can be allocated. Even if the time calculation is not 100% accurate, the planning will not be completely overthrown. |
2.4 |
If unsure about the nature of a task, create a generic "place holder" task and allocate its time. The detail can be provided as progress is made with the project. |
|
2. |
Determine HOW LONG each unit will take |
|
3. |
Determine WHO will perform each task |
|
4. |
Determine WHAT MATERIAL will be required for each unit |
|
5. |
Determine the LOGISTICAL RELATIONSHIP between the units |
5.1 |
Identify task for task inputs from other tasks. |
5.2 |
Control mechanism: Start at the end of the project and see if each task has the required inputs in order to continue. |
|
6. |
Determine COSTS |
