Managing Quality - Cronologia

Maxime.sottini: /* Quality control */

2016-04-05T17:02:22Z

‎Quality control

Maxime.sottini il 17:00, 5 apr 2016

2016-04-05T17:00:46Z

Maxime.sottini: /* Quality control */

2016-04-05T17:00:08Z

‎Quality control

Maxime.sottini: /* Quality planning */

2016-04-05T16:49:53Z

‎Quality planning

Maxime.sottini il 16:45, 5 apr 2016

2016-04-05T16:45:22Z

Maxime.sottini: Created page with "Quality is generally defined as the totality of features and inherent or assigned characteristics of a product, person, process, service and/or system that bear on its abil..."

2016-04-05T16:32:47Z

Created page with "Quality is generally defined as the totality of features and inherent or assigned characteristics of a product, person, process, service and/or system that bear on its abil..."

Nuova pagina

Quality is generally defined as the totality of
features and inherent or assigned characteristics of
a product, person, process, service and/or system
that bear on its ability to show that it meets
expectations or satisfies stated needs, requirements
or specification.

← Versione meno recente		Versione delle 17:02, 5 apr 2016
Riga 16:		Riga 16:
	Therefore the key activities in this domain is related to carrying out the quality methods, recording the results and gaining acceptance of quality results.		Therefore the key activities in this domain is related to carrying out the quality methods, recording the results and gaining acceptance of quality results.

−	This can be done with two approaches. The easiest consists of using ''[[glossary\|project activities]]'' (managed in project ''[[glossary\|Activities]]'' section) to plan and track the results of quality methods (e.g. the execution of a test). Specific quality related information can be added to ''[[glossary\|project activities]]'' in <u>''Activities''</u> section. A more advanced and flexible approach consists of configuring and using ''[[glossary\|workflows]]'' in order to support the execution of quality methods. For example a specific workflow could be designed to execute a product quality inspection. However, the use of ''[[glossary\|workflows]]''	+	This can be done with two approaches. The easiest consists of using ''[[glossary\|project activities]]'' (managed in project ''[[glossary\|Activities]]'' section) to plan and track the results of quality methods (e.g. the execution of a test). Specific quality related information can be added to ''[[glossary\|project activities]]'' in <u>''Activities''</u> section. A more advanced and flexible approach consists of configuring and using ''[[glossary\|workflows]]'' in order to support the execution of quality methods. For example a specific workflow could be designed to execute a product quality inspection. The ''[[glossary\|workflow]]'' records (and associated reporting) can be used to implement the quality register concept. However, the use of ''[[glossary\|workflows]] ''requires the activation of the [[SM - Service Desk and Service Management\|SM - Service Desk and Service Management module]].
−
−	~~<nowiki> </nowiki>~~requires the activation of the SM - Service Desk and Service Management module.

← Versione meno recente		Versione delle 17:00, 5 apr 2016
Riga 18:		Riga 18:
	This can be done with two approaches. The easiest consists of using ''[[glossary\|project activities]]'' (managed in project ''[[glossary\|Activities]]'' section) to plan and track the results of quality methods (e.g. the execution of a test). Specific quality related information can be added to ''[[glossary\|project activities]]'' in <u>''Activities''</u> section. A more advanced and flexible approach consists of configuring and using ''[[glossary\|workflows]]'' in order to support the execution of quality methods. For example a specific workflow could be designed to execute a product quality inspection. However, the use of ''[[glossary\|workflows]]''		This can be done with two approaches. The easiest consists of using ''[[glossary\|project activities]]'' (managed in project ''[[glossary\|Activities]]'' section) to plan and track the results of quality methods (e.g. the execution of a test). Specific quality related information can be added to ''[[glossary\|project activities]]'' in <u>''Activities''</u> section. A more advanced and flexible approach consists of configuring and using ''[[glossary\|workflows]]'' in order to support the execution of quality methods. For example a specific workflow could be designed to execute a product quality inspection. However, the use of ''[[glossary\|workflows]]''

−	<nowiki> </nowiki>~~quires~~ the activation of the SM - Service Desk and Service Management module.e	+	<nowiki> </nowiki>requires the activation of the SM - Service Desk and Service Management module.

← Versione meno recente		Versione delle 17:00, 5 apr 2016
Riga 13:		Riga 13:
	== Quality control ==		== Quality control ==
	Quality control is achieved by implementing, monitoring and recording the quality methods and responsibilities defined in the Quality Management Strategy and Product Descriptions (and subsequently agreed to in Work Packages).		Quality control is achieved by implementing, monitoring and recording the quality methods and responsibilities defined in the Quality Management Strategy and Product Descriptions (and subsequently agreed to in Work Packages).
		+
		+	Therefore the key activities in this domain is related to carrying out the quality methods, recording the results and gaining acceptance of quality results.
		+
		+	This can be done with two approaches. The easiest consists of using ''[[glossary\|project activities]]'' (managed in project ''[[glossary\|Activities]]'' section) to plan and track the results of quality methods (e.g. the execution of a test). Specific quality related information can be added to ''[[glossary\|project activities]]'' in <u>''Activities''</u> section. A more advanced and flexible approach consists of configuring and using ''[[glossary\|workflows]]'' in order to support the execution of quality methods. For example a specific workflow could be designed to execute a product quality inspection. However, the use of ''[[glossary\|workflows]]''
		+
		+	<nowiki> </nowiki>quires the activation of the SM - Service Desk and Service Management module.e

← Versione meno recente		Versione delle 16:49, 5 apr 2016
Riga 8:		Riga 8:

	The quality strategy is typically a document which cab be stored in ''[[glossary\|project]]'' ''<u>Documents</u>'' section or as a ''[[glossary\|project]]'' output itself (therefore as a ''delivery'' in <u>''Deliveries''</u> section).		The quality strategy is typically a document which cab be stored in ''[[glossary\|project]]'' ''<u>Documents</u>'' section or as a ''[[glossary\|project]]'' output itself (therefore as a ''delivery'' in <u>''Deliveries''</u> section).
		+
		+	Products are managed in the <u>''Deliveries''</u> section of a ''[[glossary\|project]]'' and their description can be enriched with the needed quality attributes.
		+
		+	== Quality control ==
		+	Quality control is achieved by implementing, monitoring and recording the quality methods and responsibilities defined in the Quality Management Strategy and Product Descriptions (and subsequently agreed to in Work Packages).

← Versione meno recente		Versione delle 16:45, 5 apr 2016
Riga 1:		Riga 1:
−	Quality is generally defined as the totality of	+	Quality is generally defined as the totality of features and inherent or assigned characteristics of a product, person, process, service and/or system that bear on its ability to show that it meets expectations or satisfies stated needs, requirements
−	features and inherent or assigned characteristics of
−	a product, person, process, service and/or system
−	that bear on its ability to show that it meets
−	expectations or satisfies stated needs, requirements
	or specification.		or specification.
		+
		+	Two key activities are performed concerning quality management for a ''[[glossary\|project]]'': quality planning and quality control.
		+
		+	== Quality planning ==
		+	Quality planning is about defining the products required of the project, with their respective quality criteria, quality methods (including effort required for quality control and product acceptance) and the quality responsibilities of those involved. This generally leads to the definition of a quality management strategy (which specifies the quality management system and key quality management responsibilities) and of product descriptions (including quality expectations, acceptance criteria, tolerances, methods and specific responsibilities).
		+
		+	The quality strategy is typically a document which cab be stored in ''[[glossary\|project]]'' ''<u>Documents</u>'' section or as a ''[[glossary\|project]]'' output itself (therefore as a ''delivery'' in <u>''Deliveries''</u> section).