Quality – template & application

Template:

Quality Strategy Management

This document is used to define the quality techniques and standards to be applied to all projects are products. Quality is a specific property of the scope (see “Iron Triangle”) and dictates the standards to be used for accepting any outcome.

Creating more value with integrated templates

The production of information within the project is a matter that is almost outreaching of the Project Manager capabilities. Any stakeholder is a source of production and a destination of data; therefore, the necessity of validating the data becomes of paramount importance.  In fact, the credibility of the Project Manager depends upon the quality (reliability) of the information released with the official imprimatur. This does not avoid the presence of gossips, a certified system for granting the “usability” of the information set the difference between rumors and clear statements.

The reliability of the information has to be built through the creation of a system working on the principle of the “Business Intelligence”. Loads of data will be collected in the most neutral and efficient way. Therefore, these activities will be treated as a project itself. These are the main steps suggested by Craig Curran-Morton in his post :

• Planning
• Collection
• Storage
• Analysis
• Delivery

Planning

While the requirements are set in the Quality Management Strategy, the actual planning of the production of the procedures (scripts for manning the data collection and dispatching) will be agreed with the developers’ team. The active participation of them will increase the chances of success of the whole system.

Collection

Most if not all the work shall be done in background. Automated procedures allow the capture of the actual values with no interference or workload.

Storage

The “register” type of the templates is conceived for storing data for further analysis. This policy has to be agreed with the IT department also for logistic (space and network) reasons.

Analysis

It is a part of the Quality Management Strategy document.  One of the most important tenets is the active participation of the developers’ team. This increases the acceptance of the settings and grants the necessary maintenance and enhancements.

Delivery

This has to be synchronized with the actual production plans.