Quality management for IT student, Slides of Project Management

ICT 302 IT professional Practice Project

Typology: Slides

2020/2021

Uploaded on 01/16/2022

tomclacklly0000
tomclacklly0000 🇻🇳

4 documents

1 / 3

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Project Quality Management
Quality is “the degree to which a set of inherent characteristics fulfills requirements”, and is
based on:
Conformance to requirements: the project’s processes and products meet written
specifications
Fitness for use: a product can be used as it was intended
Project quality management ensures that the project will satisfy the needs for which it was
undertaken, in accordance with specified quality standards.
Project quality management processes include:
1. Planning quality: identifying which quality standards are relevant to the project and how
to satisfy them. The application of metrics provides a standard of measurement.
Planning quality implies the ability to anticipate situations and prepare actions to bring
about the desired outcome. It is important to prevent defects by:
Selecting proper materials
Training and indoctrinating people in quality
Planning a process that ensures the appropriate outcome
Scope Aspects of IT Projects Related to Quality:
Functionality: is the degree to which a system performs its intended function
Features: are the system’s special characteristics that appeal to users
System outputs: are the screens and reports the system generates
Performance: addresses how well a product or service performs the customer’s
intended use
Reliability: is the ability of a product or service to perform as expected under
normal conditions
Maintainability: addresses the ease of performing maintenance on a product
2. Performing quality assurance: periodically evaluating overall project performance
(including all the project activities) to ensure the project will satisfy the relevant quality
standards.
Benchmarking generates ideas for quality improvements by comparing specific project
practices or product characteristics to those of other projects or products within or outside
the performing organization.
A quality audit is a structured review of specific quality management activities that help
identify lessons learned that could improve performance on current or future projects.
3. Performing quality control: monitoring specific project results to ensure that they comply
with the relevant quality standards. The main outputs of quality control are:
Acceptance decisions
Re-work (if quality is not acceptable or requires updating)
Process adjustments
There are Seven Basic Tools of Quality that help in performing quality control:
1. Cause-and-effect diagrams: trace complaints about quality problems back to the
responsible production operations. They help find the root cause of a problem.
2. Quality control charts: provide a graphic display of data that illustrates the results of a
pf3

Partial preview of the text

Download Quality management for IT student and more Slides Project Management in PDF only on Docsity!

Project Quality Management

Quality is “the degree to which a set of inherent characteristics fulfills requirements”, and is based on:  Conformance to requirements : the project’s processes and products meet written specifications  Fitness for use : a product can be used as it was intended Project quality management ensures that the project will satisfy the needs for which it was undertaken, in accordance with specified quality standards. Project quality management processes include:

  1. Planning quality : identifying which quality standards are relevant to the project and how to satisfy them. The application of metrics provides a standard of measurement. Planning quality implies the ability to anticipate situations and prepare actions to bring about the desired outcome. It is important to prevent defects by:  Selecting proper materials  Training and indoctrinating people in quality  Planning a process that ensures the appropriate outcome Scope Aspects of IT Projects Related to Quality:  Functionality: is the degree to which a system performs its intended function  Features: are the system’s special characteristics that appeal to users  System outputs: are the screens and reports the system generates  Performance: addresses how well a product or service performs the customer’s intended use  Reliability: is the ability of a product or service to perform as expected under normal conditions  Maintainability: addresses the ease of performing maintenance on a product 2. Performing quality assurance : periodically evaluating overall project performance (including all the project activities) to ensure the project will satisfy the relevant quality standards. Benchmarking generates ideas for quality improvements by comparing specific project practices or product characteristics to those of other projects or products within or outside the performing organization. A quality audit is a structured review of specific quality management activities that help identify lessons learned that could improve performance on current or future projects.
  2. Performing quality control : monitoring specific project results to ensure that they comply with the relevant quality standards. The main outputs of quality control are:  Acceptance decisions  Re-work (if quality is not acceptable or requires updating)  Process adjustments There are Seven Basic Tools of Quality that help in performing quality control:
    1. Cause-and-effect diagrams: trace complaints about quality problems back to the responsible production operations. They help find the root cause of a problem.
    2. Quality control charts: provide a graphic display of data that illustrates the results of a

process over time. The main use of control charts is to prevent defects, rather than to detect or reject them. Quality control charts allow you to determine whether a process is 'in control' or 'out of control'.

  1. Run charts: display the history and pattern of variation of a process over time. It is a line chart that shows data points plotted in the order in which they occur. Can be used to perform trend analysis to forecast future outcomes based on historical patterns.
  2. Scatter diagrams: help to show if there is a relationship between two variables. The closer data points are to a diagonal line, the more closely the two variables are related.
  3. Histograms: bar graphs of a distribution of variables. Each bar represents an attribute or characteristic of a problem or situation, and the height of the bar represents its frequency.  Pareto diagrams are a histogram that can help you identify and prioritize problem areas. Pareto analysis is also called the 80-20 rule, meaning that 80 percent of problems are often due to 20 percent of the causes.
  4. Flowcharts: provide a graphic display of the logic and flow of processes that help analyze how problems occur and how processes can be improved. They show activities, decision points, and the order of how information is processed.
  5. Statistical Sampling: involves choosing part of a population of interest for inspection. The size of a sample depends on how representative you want the sample to be. One sample size formula is: Sample size = (certainty factor/acceptable error)^2 x 0. Testing: this should be done during almost every phase of the IT product development life cycle, not just near the end. Four types of tests:  Unit testing tests each individual component (often a program) to ensure it is as defect-free as possible  Integration testing occurs between unit and system testing to test the functionally of grouped components  System testing tests the entire system as one entity  User acceptance testing is an independent test performed by end users prior to accepting the delivered system The cost of quality is the cost of conformance plus the cost of non-conformance:  Conformance means delivering products that meet requirements and fitness for use  Non-conformance means not meeting quality expectations OR taking responsibility for failures