The previous BLOG provided an overview of the nature and characteristics of a project. This BLOG moves further and outlines the main "artifacts" of the project, from a delivery perspective. If one asks the question - what should a project leave behind after successful implementation, three things come to mind:
- A deliverable/product or solution
- Benefits
- Tasks
The deliverable/product/solution aims to solve a problem. In respect of this the key is to know what the problem is, whether it is real and to make sure that the deliverable, etc will solve the problem.
The benefits are derived from solving the problem, and as such it provides the basis for the business case
The tasks in a project are performed to produce the deliverable/product/solution.
Because the benefits of a project are often oversold ,the expectations of the client are not aligned with the real benefits that will be derived from production of the final deliverable. The result is that, while projects often deliver, the project is still perceived to be unsuccessful. In this regard it is important to realize that the project team can only provide the deliverable/solution/product and that the project is essentially over when this was achieved. The success and credibility of the project manager though is dependent on the extent to which expectations can be managed.
The slide-show below encapsulates the essence of the discussion and can be downloaded.
No comments:
Post a Comment