Someone in the organization wants something. There can be several reasons for this need eg. efficiency, effectivity or innovation. It is important to keep an eye on these reasons. Sometimes that reason is forgotten. In that case you will have hard work on a solution that in the end does not satisfy the need. It is important not in the end to 'have' something but to have 'achieved' something. The fun is not in the having but in the using. To have a Maserati is nice but to (keep) driving it is fun. I think it is clear what I mean: 'Think well before you start'.
In the world of projects the overview of pro's and con's is called business case. What's the cost to get and to keep, what is the profit on the longer run and how do those two compare. In the world we live in many things change in a rapid speed, also during the lifetime of projects. The cost as well as the benefit can change. Therefor a Project Board should continiously check if the business case will be met. If cost becomes higher then profit it could be a good time to reconsider continuation of the project. So, it is fine to have needs but not at all cost. Remember that benefits are not always (only) economic terms.
Next time I would like to consider the composition of the Project Board. But as with all projects, you never know if something pops up that might push us in another direction. We'll see.
No comments:
Post a Comment