Planuvis

The menu structure on the left offers all established, classic PM methods, which are also always displayed visually:

• Define goals and non-goals
• Identify and cluster environments and stakeholders
• Plan your results, services, deadlines, resources, costs and risks
• Plan your project organisation, define responsibilities or establish rules of the game
• Visualise your planning as a work breakdown structure, project organisation chart or risk matrix

One of the most important project plans and central communication tools for us is the work breakdown structure (WBS). This offers a central input option in Planuvis:

• Create phases, work packages and milestones directly in the WBS
• Move and copy tasks using drag & drop without waiting time
• Zoom in to the top bird's eye view or work package details as required
• Work with a note overlay to visualise team agreements directly in the meeting
• Use the right-hand ribbon to view or edit detailed data comprehensively

One of the most important project plans and central communication tools for us is the work breakdown structure (WBS). In Planuvis, this also offers comprehensive evaluation options:

• Visualise logical dependencies via scheduling relationships
• Highlight cost drivers and cost variances visually
• Highlight specific work packages based on a reference to delivery objects, stakeholders, risks, etc.
• Visualise progress or the traffic light status directly in the WBS

Even if many PM methods are visualised separately, elements can be meaningfully linked, which ensures consistent planning and traceability, as well as enabling highlighting in the work breakdown structure (WBS):

• Results are provided via WBS tasks.
• Stakeholders are processed via WBS tasks.
• Project core team members of the project organisation take responsibility for work packages of the WBS.
• Measures to prevent specific risks are part of WBS work packages.

Project managers decide which planning status is interesting and should be cancelled in order to track changes or interesting deviations:

• Create snapshots that can also be used to track new or deleted elements (work packages, risks, etc.).
• Comparison with the baseline plan after project release (at project initiation or project start) or any status report (of a project controlling cycle) for the current project plan.
• Basis for project status reports or similar reports (target/actual comparison).

• Reports can be designed comprehensively (an entire project manual can be generated automatically).
• Information can be integrated as text, as a table and partly as a graphic (such as PSP).
• Texts can be formatted automatically (e.g. traffic light status in the appropriate font colour).
• Configured templates can be used directly or transferred to other users (XML template).