Info313 – Week 7 – Project Quality mgmt – Flashcards

Inputs: People, equipment, space, money etc Project Outputs: New computer system, new processes, trained staff etc Outcomes: Objectives we want to realise from system Utilisation: How system "Customer" uses system

Inputs--> Project--> outputs = What = we have almost complete control over this Outcomes = Why Utilisation = we have very limited control over this.

The quality of the outputs: project mgmt The predisposition of our customers: change and communication mgmt External influences: risk mgmt

the degree to which a set of inherent characteristics fufils requirements

Project quality management ensures that the project will satisfy the needs for which it was undertaken.

Processes include: Planning Quality: Identifying which quality standards are relevant to the project and how to satisfy them. Quality assurance: Periodically evaluating overall project performance to ensure the project will satisfy the relevant quality standards. Quality control: Monitoring specific project results to ensure that they comply with the relevant quality standards.

Outputs: Quality management plan, quality metrics, quality checklists, process improvement plan, and project document updates

Perform quality assurance Outputs: Organisational process asset updates, change requests, project mgmt plan updates, and project document updates

Quality control measurements, validated changes validated deliverables, organisational process asset updates change requests, project management plan updates, and project document updates.

PLanning for a system that is fit for purpose Implies the ability to anticipate situations ad prepare actions to rbing about the desired outcome IMportant to prevent defects by: selecting proper materials training and indoctrinating people of quality planning a process that ensures the appropriate outcome

Functionality - the degree to which a system performs its intended function. Features - the system's special characteristics that appeal to users. System outputs - the screens and reports the system generates. Performance - looks at how well a product or service performs the customer's intended use. Reliability - the ability of a product or service to perform as expected under normal conditions. Maintainability - addresses the ease of performing maintenance on a product.

Project managers/directors are ultimately responsible for quality management on their projects, and Project managers/directors are held accountable through the Governance process.

Quality assurance includes all activities related to satisfying the relevant quality standards for a project. Another goal of quality assurance is continuous quality improvement.

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.

structured review of specific quality management activities that helps identify lessons learned and can improve performance on current or future projects

External QA review report outline: Based on a framework or standard Typical QA review report Review of documentation: configuration, walkthroughs, risk register, issue log, communication log, budget and project plan Interviews with key project staff and stakeholders Highlights risks to the project, and Incorporates recommendations for change to processes, outputs and risk mediation See sample risks & recommendations

...The main outputs of quality control are: Acceptance decisions Rework Process adjustments

tools and techniques include: Cause-and-effect diagrams (Ishikawa/fishbone diagram) Pareto analysis Quality control charts Statistical sampling Six Sigma also Run Charts, Scatter Diagrams, Histograms

diagram that traces complaints about quality problems back to the responsible production operations to help find the root cause. Also known as fishbone diagram or Ishikawa diagram

involves identifying the vital few contributors that account for the most quality problems in a system Also called the 80-20 rule, meaning that 80 percent of problems are often due to 20 percent of the causes. Pareto diagrams are histograms, or column charts representing a frequency distribution, that help identify and prioritize problem areas.

The seven run rule states that if seven data points in a row are all below the mean, above the mean, or are all increasing or decreasing, then the process needs to be examined for non-random problems

A comprehensive and flexible system for achieving, sustaining, and maximizing business success; 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.

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

Define: define the problem/opportunity, process, and customer requirements Measure: define measures, then collect, compile, and display data Analyze: scrutinize process details to find improvement opportunities Improve: generate solutions and ideas for improving the problem Control: track and verify the stability of the improvements and the predictability of the solution

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 functionally grouped components. System (end-to-end) testing tests the entire system as one entity. User acceptance testing (UAT) is an independent test performed by end users prior to accepting the delivered system. Performance/ Stress testing used to determine the speed and capacity of the system and system robustness under stress

Establish standards to be used Define acceptance test criteria Identify broad test scenarios Create test scripts based on scenarios, including: Step by step process Expected outcome from each step, and acceptance criteria Space to record "defects" that prevent satisfactory completion of the test Space for detailed notes, permitting remediation of the "defect" Space to record the re-test of the script and to record the outcome of the re-test Sign-off of test script as acceptable Run test script Record "defects" in the defect log Provide remediation for "defects" Re-test as needed until acceptable

Requires customer satisfaction Prefers prevention to inspection Recognizes management responsibility for quality

Establish leadership that promotes quality A large percentage of quality problems are associated with management, not technical issues Understand the cost of quality (both conformance & nonconformance) Focus on organizational influences and workplace factors that affect quality (Refer next 2 slides) Follow maturity models e.g. The Software Engineering Institute's Capability Maturity Model Integration is a process improvement approach that provides organizations with the essential elements of effective processes.