“A rose is a rose is a rose.”

_______________________________   Gertrude Stein

We say:
A project manager is a project manager is a project manager. This means: he/she is NOT a storage specialist, java specialist, someone writing network security concepts or analyses a particular IT problem.

Fortunately best practice in project management PRINCE2 emphazises and supports this concept by deviding roles clearly.

So why even mentioning this concept? We do get requests or project offers, which point into a different direction – wanting to have the all-in-one person: project manager AND IT specialist.

Let’s come back on what “Best Practice” really means. It just means: That’s what worked proven best in a certain way within a longer/considerable time frame.

Some of the best project managements I have done were in fields, in which I had no clue about the content and therefore focussed totally on manageing the project, did not mix into content and build a win-win collaboration with the other project team members. Each project member had/has his/her role and everyone is important in his/her position contributing to the overall project outcome.

If you want to have a professionally managed project, don’t go for the all-in-one-solution when in comes to project management and specialists work. Put a professional project manager in place.

A project manager is a project manager.
A software developer is a software developer.
An IT security specialist is an IT security specialist.
No one of those is more or less important, all are needed, but everyone at his/her place.

Kathrin Held

{Kommentare gern auch in Deutsch}

One Response to “A Project Manager Is A Project Manager”