Mis 448 Ch8 - Quality

Front 1

What Is Project Quality

Back 1

Conformance to requirements: the project’s processes and products meet written specifications

Front 2

What Is Project Quality

Back 2

Fitness for use: a product can be used as it was intended

Front 3

Project quality management ensures

Back 3

that the project will satisfy the needs for which it was undertaken

Front 4

Quality Processes include

Back 4

Planning quality: identifying which quality standards are relevant to the project and how to satisfy them; a metric is a standard of measurement

Front 5

Quality Processes include

Back 5

Performing quality assurance: periodically evaluating overall project performance to ensure the project will satisfy the relevant quality standards

Front 6

Quality Processes include

Back 6

Performing quality control: monitoring specific project results to ensure that they comply with the relevant quality standards

Front 7

Plan Quality

Back 7

Qulity Management plan, Quality metrics, quality checklists, process improvement plan, project document updates

Front 8

Executing: Perform quality assurance

Back 8

organizational process asset updates, change requests, project management plan updates, project document updates

Front 9

Monitoring and Controlling: Perform quality control

Back 9

quality control measurements, validate changes, validate deliverables, organizational asset updates, change requests, project management plan updates, project document updates

Front 10

Scope Aspects of IT Projects: functionality

Back 10

is the degree to which a system performs its intended function

Front 11

Scope Aspects of IT Projects: features

Back 11

are the system’s special characteristics that appeal to users

Front 12

Scope Aspects of IT Projects: System outputs

Back 12

are the screens and reports the system generates

Front 13

Scope Aspects of IT Projects: Performance

Back 13

addresses how well a product or service performs the customer’s intended use

Front 14

Scope Aspects of IT Projects: Reliability

Back 14

is the ability of a product or service to perform as expected under normal conditions

Front 15

Scope Aspects of IT Projects: Maintainability

Back 15

addresses the ease of performing maintenance on a product

Front 16

Who’s Responsible for the Quality of Projects

Back 16

Project managers are ultimately responsible for quality management on their projects

Front 17

Quality assurance includes

Back 17

all the activities related to satisfying the relevant quality standards for a project

Front 18

Benchmarking generates

Back 18

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

Front 19

A quality audit is

Back 19

a structured review of specific quality management activities that help identify lessons learned that could improve performance on current or future projects

Front 20

The main outputs of quality control are

Back 20

Acceptance decisions, rework, Process adjustments

Front 21

Seven Basic tools of Quality

Back 21

Cause and effect diagrams (fishbone, Ishikawa diagrams, 5 whys), quality control charts, run chart, scatter diagram, histograms, pareto charts, flow charts

Front 22

Statistical Sampling

Back 22

involves choosing part of a population of interest for inspection

Front 23

Six Sigma is

Back 23

a comprehensive and flexible system for achieving, sustaining, and maximizing business success. Six Sigma is uniquely driven by close understanding of customer needs, disciplined use of facts, data, and statistical analysis, and diligent attention to managing, improving, and reinventing business processes

Front 24

DMAIC is

Back 24

a systematic, closed-loop process for continued improvement that is scientific and fact based

Front 25

DMAIC stands for

Back 25

Define, Measure, Analyze, Improve, Control

Front 26

sigma means

Back 26

Standard deviation measures how much variation exists in a distribution of data

Front 27

Six 9s of quality is Six 9s of quality is

Back 27

a measure of quality control equal to 1 fault in 1 million opportunities

Front 28

Testing should be done

Back 28

during almost every phase of the IT product development life cycle

Front 29

Unit testing tests

Back 29

each individual component (often a program) to ensure it is as defect-free as possible

Front 30

Integration testing occurs

Back 30

between unit and system testing to test functionally grouped components

Front 31

User acceptance testing is

Back 31

an independent test performed by end users prior to accepting the delivered system

Front 32

Watts S. Humphrey

Back 32

a renowned expert on software quality, defines a software defect as anything that must be changed before delivery of the program

Front 33

Humphrey suggests

Back 33

that people rethink the software development process to provide no potential defects when you enter system testing; developers must be responsible for providing error-free code at each stage of testing

Front 34

As Joseph M. Juran said

Back 34

It is most important that top management be quality-minded. In the absence of sincere manifestation of interest at the top, little will happen below

Front 35

The cost of quality is

Back 35

the cost of conformance plus the cost of nonconformance

Front 36

Conformance means

Back 36

delivering products that meet requirements and fitness for use

Front 37

Cost of nonconformance means

Back 37

means taking responsibility for failures or not meeting quality expectations

Front 38

Five Cost Categories Related to Quality

Back 38

prevention, appraisal, internal failure, external failure, measurement and test equipment costs

Front 39

Prevention cost

Back 39

cost of planning and executing a project so it is error-free or within an acceptable error range

Front 40

Appraisal cost:

Back 40

cost of evaluating processes and their outputs to ensure quality

Front 41

Internal failure cost:

Back 41

cost incurred to correct an identified defect before the customer receives the product

Front 42

External failure cost:

Back 42

cost that relates to all errors not detected and corrected before delivery to the customer

Front 43

Measurement and test equipment costs

Back 43

capital cost of equipment used to perform prevention and appraisal activities

Front 44

Organizational Influences, Workplace Factors, and Quality

Back 44

A dedicated workspace and a quiet work environment were key factors to improving programmer productivity

Front 45

Study by DeMarco and Lister

Back 45

showed that organizational issues had a much greater influence on programmer productivity than the technical environment or programming languages

Front 46

Expectations and Cultural Differences in Quality

Back 46

Expectations also vary by:

Front 47

Maturity models are

Back 47

frameworks for helping organizations improve their processes and systems

Front 48

The Software Quality Function Deployment Model focuses

Back 48

on defining user requirements and planning software projects

Front 49

CMMI levels, from lowest to highest, are:

Back 49

incomplete, performed, managed, defined, quantitatively managed, optimizing

Front 50

PMI’s Maturity Model

Back 50

Addresses standards for excellence in project, program, and portfolio management best practices and explains the capabilities necessary to achieve those best practices