Gantt & stakeholders’ time(s)

By Eugenio, on July 2nd, 2009

Gear wheels (respect and smile are the best lubricants)

It is an adult post. It starts with bees, birds and flowers.

It is not easy to apply these models to stakeholders’ taxonomy. However, these models represent three different conceptions about time (a nice post about it).

The project’s “external” stakeholders have jobs outside the IT industry. Furthermore, IT projects are not exclusively manned by developers. The multi-cultural aspects have its relevance as well (e.g. working time, time-zone, national holidays etc).

Diverse expertise implicates different rhythms. One of the main aims of the stakeholders’ analysis has to be a model (Collaboration Plan) that can help every key person (approvers) how to work out a common ground for working together.

The “common ground” has to be considered into its “spatial” dimensions:

Time (clocks and calendars have to be shared)
The unique subject at the base of the project shall be formed clearly enough to be drawn (“Product Description – Prince2”). From this document, other technical outcomes (e.g. architectural designs). After that, the Agile approach can offer good chances for clearing the way to a synergy between producers and users. In an effort to involveall other stakeholders (considering their timing).
Lingo (es). Most of the translation job is carried through by the BA. However, the communications at managerial level are based on figures and diagrams. Mostly important, they are supported by mutual trust and respect.

Once the whole matter to be produced is clear enough and the collaborations’ mechanisms (at managerial level) are working. There are subsequent actions dedicated to synchronizing:

Estimating the required resources both in terms of skills / capacity and time to be alloted.
Asking for resources (information, machine and most important people and their knowledge – either professional or company’s related).
Planning, then executing the resources’ released.
Working seamlessly people with different professional background, but common targets.

Different speeds cannot hamper the project

Working like an orchestra

One of the most important tasks of project manager (duly assisted by sponsor) is to work as a gear wheel between each stakeholder’s approver and / or influencer.

I become conscious that the concept of “Collaboration Plan” has to be developed (suggestions will be warmly welcome). Today the biggest issue is about to easily render the links between people and time.

Conclusion

Solipsism kills projects. Whenever a person (or bunch of people sharing the “same” space and similar targets) perceive themselves as the center of the universe (it could be reduces as a project), there is a huge risk for failing the delivery of the agreed outcome.

Whatever small can be a project, it is the result of many teams working together. The first and most important matter to be shared is the project’s clock. It will toll the times for controlling and then aligning all stakeholders’ teams.

“The only reason for time is so that everything doesn’t happen at once.”