Saturday, September 1, 2012
Project Management - 5 Traits of effective tools
There is a not-so-tall-tale of the project manager who has apparently spent hours completing and updating of models. These templates were deemed necessary for each project by the Director of the PMO. The project manager spent so much time with his models that had their own models that had little time to manage its vision into reality. In short, he was a slave to his tools. This not-so-tall-tale, in fact, takes place daily throughout PMO. There are 5 characteristics models to ensure that you are not the main character this story. These are:
1. Simple
This recommendation seems at odds with what project managers do every day. Our jobs are safe is not that simple and certainly not easy. Why should our tools? After all, does not that give sponsors and team members the false impression that our jobs are really simple and easy? The answer is to encourage the full participation of sponsors and team members to make their job as simple and easy even if you risk your ego and empire building. Before adding a new model to the library protocol to ask:
a) What is the goal I'm trying to achieve with this model?
b) Can the model of at least 80% of the type of projects only partly reaches the target?
c) are two elements within the model that asks the same question?
2. Transparent
There is some truth in saying that if you have to explain a joke, not funny. The same applies to project templates. If you must go to great efforts to explain or justify a goal models' to your sponsors and team members, then the model are not necessary. Strive to remove swollen models, complicated and not targeted by your library.
3. Flexible
Contemporary thinking suggests that companies must have five or fewer levels of hierarchy, projects should be agile and answer real change means having the ability to turn on a dime. The same thoughts must be applied to your models. Models should be very flexible with the following characteristics:
one. Has existing models achieve their goal? For those who only partially achieve its goals, these models can be modified?
b. The model can be used in 80% of the projects? If your sponsors, team members or project manager has an idea / initiative for the regular models to meet the remaining 20%?
c. And 'feedback from sponsors / team / project manager on the model discussed and considered before deciding whether to integrate the change?
4. Concise
Verbal communication is often richer than written communication. Often it is easier to be told what to do about what to read what to do, especially if such a reading is made up of blocks of text in 8 point font. The model should be targeted (use bullets where possible) allow "breathing eye" space (white space), outlining where the information is needed (boxes, lines, check boxes) and save the trees (in two pages does not say what it can be said in a). Concise.
5. Evolve
As the theory of man, the model needs to learn, grow and keep his own. A model created and maintained with evolution in mind displays the following characteristics:
one. It has a feedback of models has been revised and supplemented, if necessary?
b. Are you willing to admit that the model does not work or modify its entirety, in another model or remove it entirely?
c. The model was completely controlled within the PMO or is simply a model inherited from the last exercise best practices PMO?
5 The above mentioned features, together aim and ensure that the models used within a PMO are the best (efficient, responsive, targeted) may be. Avoid the central feature in the story not-so-high. Make sure that the models are simple, transparent, flexible, concise and evolve in order to avoid being a slave to them .......
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment