software project management

24
SOFTWARE PROJECT MANAGEMENT Project Quality Management Dr. Ahmet TÜMAY, PMP

Upload: callum

Post on 30-Jan-2016

23 views

Category:

Documents


0 download

DESCRIPTION

SOFTWARE PROJECT MANAGEMENT. Project Quality Management Dr. Ahmet TÜMAY, PMP. Project Quality Management. Include all the activities of the performing organization that determine quality policies, objectives, and responsibilities so that - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: SOFTWARE PROJECT MANAGEMENT

SOFTWARE PROJECT MANAGEMENT

SOFTWARE PROJECT MANAGEMENT

Project Quality ManagementDr. Ahmet TÜMAY, PMP

Page 2: SOFTWARE PROJECT MANAGEMENT

Project Quality ManagementInclude all the activities of the performingorganization that determine quality policies, objectives, and responsibilities so thatthe project will satisfy the needs for which it was undertaken.

PQM works to ensure that the Project and Product requirements are met and validated.

Page 3: SOFTWARE PROJECT MANAGEMENT

Quality Management• Quality is “the degree to which a set of

inherent characteristics fulfill requirements”

• A critical element of quality management in the project context is to turn stakeholder needs, wants, and expectations into requirements through Stakeholder Analysis, performed during Project Scope Management.

Page 4: SOFTWARE PROJECT MANAGEMENT

Quality Management• Quality and grade are not the same.

Grade is a category assigned to products or services having the same functional use but different technical characteristics

• Precision and accuracy are not equivalent. Precision is consistency that the value of repeated measurements are clustered and have little scatter. Accuracy is correctness that the measured value is very close to the true value.

Page 5: SOFTWARE PROJECT MANAGEMENT

Modern Quality Management Principles• Customer satisfaction• Prevention over inspection• Continuous improvement• Management responsibility• Cost of quality

The cost of quality refers to the total cost of all efforts related to quality throughout the products life cycle.

Page 6: SOFTWARE PROJECT MANAGEMENT

Plan Quality • One of the fundamental principle of

modern quality management is: quality is planned, designed, and built in—not inspected in.

• The project scope baseline is a key input to quality planning since it documents major project deliverables, the project objectives that serve to define requirements (which were derived from stakeholder needs, wants, and expectations), thresholds, and acceptance criteria.

Page 7: SOFTWARE PROJECT MANAGEMENT
Page 8: SOFTWARE PROJECT MANAGEMENT

Plan Quality Management

Quality planning involves identifying which quality standards are relevant to the project and determining how to satisfy them.

Planning should be performed in parallel with the other project planning processes. Cost and schedule may be required to adjust to satisfy quality reqs.

Page 9: SOFTWARE PROJECT MANAGEMENT
Page 10: SOFTWARE PROJECT MANAGEMENT

PQ Tools and Techniques

• Cost Benefit AnalysisThe primary benefit of meeting quality

requirements is less rework, which means higher productivity, lower costs, and increased stakeholder satisfaction. The primary cost of meeting quality requirements is the expense associated with Project Quality Management activities.

• Control Charts• Cost of Quality

Page 11: SOFTWARE PROJECT MANAGEMENT

Cost of Quality

Page 12: SOFTWARE PROJECT MANAGEMENT
Page 13: SOFTWARE PROJECT MANAGEMENT

PQ Outputs• QM Plan

– that provides input to the overall project management plan and must address quality control (QC), quality assurance (QA), and continuous process improvement for the project.

– The plan should be reviewed early in the project to ensure that the earlier decisions, for example on concepts, designs and tests, are based on accurate information.

Page 14: SOFTWARE PROJECT MANAGEMENT

QP Outputs• Quality Metrics

– A metric is an operational definition that describes, in very specific terms, what something is and how the quality control process measures it. A measurement is an actual value. Some examples of quality metrics include defect density, failure rate, availability, reliability, and test coverage

• Quality Checklists– A checklist is a structured tool, usually

component-specific, used to verify that a set of required steps has been performed.

Page 15: SOFTWARE PROJECT MANAGEMENT

Perform Quality Assurance

PQA is the process of auditing the quality requirements and the results from quality control measurements to ensure appropriate quality standarts and operational definitions are used.

Page 16: SOFTWARE PROJECT MANAGEMENT

Perform Quality Assurance

• QA also provides an umbrella for continuous process improvement that reduces waste and non-value-added activities, which allows processes to operate at increased levels of efficiency and effectiveness.

Page 17: SOFTWARE PROJECT MANAGEMENT

PQA Tools and Techniques• Quality Audits

– A quality audit is a structured, independent review to determine whether project activities comply with organizational and project policies, processes, and procedures.

• Process Analysis– examines problems experienced,

constraints experienced, and non-value-added activities identified during process operation includes root cause analysis

Page 18: SOFTWARE PROJECT MANAGEMENT

Control QualityControl Quality (QC) is the process of monitoring and recording results of executing the quality activities to assess performance and recommennd necessery changes.

Page 19: SOFTWARE PROJECT MANAGEMENT
Page 20: SOFTWARE PROJECT MANAGEMENT

Control Quality• The project management team should

have a working knowledge of statistical quality control, especially sampling and probability, to help evaluate QC outputs.

– Prevention (keeping errors out of the process), inspection (keeping errors out of the hands of the customer).

– Attribute sampling (the result conforms, or it does not) and variables sampling (the result is rated on a continuous scale that measures the degree of conformity).

– Tolerances (the result is acceptable if it falls within the range specified by the tolerance) and control limits (the process is in control if the result falls within the control limits).

Page 21: SOFTWARE PROJECT MANAGEMENT

CQ Tools & Techniques• Control Charts are prepared to determine

whether or not a process is stable or has predictable performance.

• Inspection Examine the work product to determine it it conforms to documented standarts.

• Histogram A histogram is a bar chart showing a distribution of variables. Each column represents an attribute or characteristic of a problem/situation.

• Pareto Chart• Inspection

Page 22: SOFTWARE PROJECT MANAGEMENT

CQ Tools & Techniques

Page 23: SOFTWARE PROJECT MANAGEMENT
Page 24: SOFTWARE PROJECT MANAGEMENT

???