Using Standards and Processes

To benefit from the use of embedded standards and processes, you must constantly monitor that everything is done according to an established agreement, and you get exactly the result you planned. All that is not regularly used, sooner or later ceases to exist. This is the law of human behavior.

An integrated software process maturity model ( CMMI - Capability Maturity Model Integration ) implements this through audits (CMMI defines auditing as a Quality Assurance activity, because this model tests processes, not a product). When using agile techniques, for example Extreme Programming or SCRUM, an instructor is hired for this purpose. It doesn't matter how the check itself happens and how you call it - all this brings only qualitative benefits.

If you encounter a situation where an accepted standard or process is ignored, you need to find out why this is happening, because the reasons may be completely different. For example:

• The person simply forgot to use any standard or process. Remind him
• The person simply did not know about the existence of a standard or process or did not know how to use it. Improve communication in a team or conduct training
• The standard or process is not suitable for this task. Either adapt the process itself, or try to find an alternative way.
• The standard or process was ineffective or too “cumbersome” for a given situation. Simplify it so that it meets the needs of the project.

Every violation of a standard or process is an opportunity to study and improve it to meet the needs of the team.