Skip to content
David Pratten edited this page Nov 20, 2017 · 17 revisions

Quick links to detailed documentation.

Background

The open source add-in for MS Project called “PMQu” assists project managers to create, and maintain, quality-checked project information. Firstly, we review the benefits of quality checking project information, and then, after pointing to the sources of the quality checks, the PMQu add-in is introduced and the introduction concludes with a short invitation to use the software tool.

Context, and why perform quality checks?

Managing quality, including that of project plans, is a challenge involving both people and process. PMQu will automate just one aspect of process, which is, checking the conformance of plans to pre-agreed quality standards. This is an activity which is impractical to perform manually on real-world plans.

PMQu is intended for the professional PM and PMO where each project’s WBS and Schedule Network may be contained within a single stand-alone MS Project plan of up to 300-350 activities. There are at least four reasons for checking the quality of project information. Quality checking can:

  • Reduce, or eliminate, many common WBS and Schedule Network mistakes,
  • Improve the flexibility of schedules under rolling wave planning,
  • Improve the transferability of project plans between project managers,
  • Assist managers to induct new project managers to use a common style for project information.

For this context, from where has the author drawn the quality checks?

Sources of Quality Checks

Firstly, PMQu checks the coherence between the WBS and Schedule Network using the Schedule Network 100 percent rule and the Add and Prune Dependencies algorithm. For a backgrounder on these checks, I advocate here for greater coherence between the WBS and Schedule Network, and then here I introduced the means to automate this coherence by applying the Schedule Network 100 percent rule and the Add and Prune Dependencies algorithm.

Secondly, and equally importantly, PMQu performs quality checks according to best practice guidance found in the following six recommended sources:

Naturally, not every piece of advice is checked. Instead, PMQu checks an integrated set of guidance drawn from all these sources.

PMQu Add-in for MS Project

The PMQu open source add-in for MS Project 2010/2013 reads the current project and creates a report in the user’s browser covering about 50 separate checks. PMQu does not alter the current project. Table 1. contains a breakdown of the quality checks by area with some examples:

Quality Check Area #checks Example Checks
Project 18 Schedule From [Project Start Date].
Task Identity 5 Every task must have a unique name.
WBS/ PBS 9 The WBS will be coherent with the Schedule Network; Summary Tasks may not have dependencies.
Network 6 Summary Tasks may not have dependencies; All tasks will participate in the Schedule Network.
Resources 4 Summary Tasks may not have resources assigned.
Scheduling 8 All tasks must have a duration specified.
Progress 5 Milestone’s %Complete must either be 0% or 100%.
Total 55

Table 1. – A breakdown of the quality checks with some examples

Next steps

You are invited to install, and use, PMQu under the open source MIT license. The software is a robust prototype rather than a "single click installer" type product and your comments and questions are welcome via GitHub issues.

The author relies on the PMQu add-in for MS Project to check project information quality for his projects. How will you use it? The MIT license for the software means that you are free to use the intellectual property in this software for anything, including running your projects, as a resource for your PMO, for training project managers, and creating commercial opportunities. Go for it!