This preview shows page 1. Sign up to view the full content.
Unformatted text preview: to attend? What level of information
will you be sharing? Who else needs to be kept informed, at what level of detail, and how often?
For example, you may want to keep the project executive updated at an overview level of detail
on a weekly basis, while you keep other managers appraised at a higher level of detail.
You will also need to spell out the relationship of yourself to the project executive, in terms of
the monitoring of progress. Equally, you need to put down how you will be monitoring progress
of the allocated tasks.
There is no one right answer for how this should be done, and indeed it will vary with every
project. Make sure you think about the size and complexity of the project, and also the
organisation's ethos and current management style. Milestones
Here you need to think about how you will break up the project. Unless it is very small, you
don't want to have the entire project as one lump of work, with the only check on progress at
the very end. Instead, it makes sense to break the project up into discrete chunks, where
related tasks can be lumped together, with a sensible milestone at the end of them. For
example, in the technology refresh in the example above, you may want to break the project
down into something like:
6. Requirements Gathering
Testing 2 It makes sense to have a defined milestone, so you know when each section is completed.
There is also another benefit of breaking the project into chunks, which I'll come back to. Tolerances
You will have already looked at the resources you need. Now we need to set how far you, or the
project executive, can let the project stray from these targets before needing to sound the
alarm. For example, you could set a tolerance in terms of finance of +/- 5%, and a tolerance in
terms of time of +/- 10%. Equally, you may want to look at tolerances of quality - i.e. how far
from the quality criteria are you willing to accept?
It is remarkably unlikely that a project will not deviate from its resource or quality ta...
View Full Document
- Spring '13