The following tip on project management is important both for senior managers and executives and for those in the business of execution. However to explain it requires a bit of technical discussion about the feature and the software concerned. The explanation below also relates to the common computing model framework which is the subject of my research.

So I recently downloaded a very cool new feature in Microsoft Visio called “WBS Modeller Add In”. This enables a Microsoft Project Plan to be imported into Visio as a set of objects that retain their hierarchical linkages/relationships. In other words an automated import tool to view a project plan as a picture like everything else in Visio. Now of course you can do something similar in Project - but the implications of this for tightly integrating work with the system that is being worked on is important.

As of now my primary interest lies in the “model - activity” cross referencing - but as I explore the feature set more it will be interesting to see how timelines, task dependencies and milestones can integrate with the target design.

So the way that I intend to use the tool is to build a plan that is tightly coupled with the objects that are being worked on. (This is in fact analagous to the BIM technology). Here is an example - lets say one particular project task is to deploy a new server - that task and its subset of tasks can be directly linked to the server as represented in the visio diagram. I think this is very important in terms of the common computing model proposition. If its important that we have a common representation of the system concerned between the working parties - then its even more important to make sure that a plan is consistent with that model. After all a plan is a set of tasks developed by a team who believe that when those tasks are done - the target changes will be effected. Ultimately as I see it the computing model changes.

By using this feature a team can take any plan and explicitly link tasks to the computing model - and then see if anything has been missed. Objects that clearly matter - but have no tasks associated with them - can become “issues” for resolution. Further - by exploring how objects in the model are related (dependencies) - a task can be discussed in terms of risk of change and impact.

As a project manager in the field the benefits of visualization are significant - less misunderstanding - a common platform for understanding and also interestingly longer retention in memory (not computer, people). For management with insufficient time to review project plans - the “task/object cross reference” validation report can become a deliverable. By creating this additional value added output - internal consistency is given a considerable boost.

Hope this has been a useful suggestion - I know I am going to use it extensively on projects and recommend it to clients.