Quality Quiz Part-2

Specification limits (goals) can be identified or modified based on historical data from projects, previous baseline reports, and customer requirements. Historical data from projects can provide insights into past performance and help determine realistic goals for future projects. Previous baseline reports can serve as a reference point for setting new goals and making adjustments. Customer requirements are crucial in determining the desired outcomes and specifications for a project. Considering all of these factors allows for a comprehensive and well-informed approach to identifying and modifying specification limits.

The correct answer is "All of the above". This is because core metrics in project management typically include Effort Variance, Schedule Variance, and Defect Density. These metrics are used to assess and measure the performance and progress of a project. Effort Variance measures the variance between planned and actual effort expended on a project. Schedule Variance measures the variance between planned and actual project schedule. Defect Density measures the number of defects per unit of measurement, such as lines of code or function points. Therefore, all three options mentioned in the question are considered core metrics in project management.

Metrics deviation analysis should be done to identify the root cause of the problem and to track the performance of the project. By analyzing metrics deviations, one can identify any deviations from the expected values or trends, which can help in identifying the underlying issues or problems causing the deviations. This analysis can also help in tracking the performance of the project by comparing the actual metrics with the planned or expected metrics. Therefore, both options (a) and (b) are correct as both are valid reasons for conducting metrics deviation analysis.

The correct answer is Both (a) and (c). Process performance baselines are the output of both project metrics data collection and business goals. Project metrics data collection helps in gathering data related to project performance, while business goals provide the context and objectives for the project. By combining these two inputs, process performance baselines are established to measure and monitor the project's performance against the desired goals.

A Project Metrics workbook should be created to monitor and control the performance of the project, measure the risks of the project, and conduct a Root Cause Analysis (RCA) in case of variances. This means that the workbook serves multiple purposes and is a comprehensive tool for managing and evaluating the project.

Both Fishbone Analysis and 5-Why Analysis are techniques used to identify the appropriate cause of defects and problems. Fishbone Analysis, also known as Ishikawa diagram, helps in identifying potential causes by categorizing them into different categories such as people, process, materials, etc. On the other hand, 5-Why Analysis involves repeatedly asking "why" to determine the root cause of a problem. By combining these two techniques, a comprehensive analysis can be conducted to identify the underlying causes of defects and problems.

The effort variance is calculated by subtracting the actual effort from the planned effort. In this case, the planned effort is 20 hours and the actual effort is 25 hours. Therefore, the effort variance is 20 - 25 = -5 hours. Since the effort variance is negative, it means that the actual effort spent exceeds the planned effort, indicating that it is not within the specification limit. Hence, the correct answer is False.

Quality audits are not a part of defect prevention. Defect prevention focuses on identifying and addressing the root causes of defects before they occur, while quality audits are conducted to assess the overall quality of a project or process after it has been completed. Quality audits help in identifying areas for improvement and ensuring compliance with quality standards, but they do not directly contribute to preventing defects from occurring in the first place.

To calculate Defect Removal Efficiency, both pre-delivery defects and post-delivery defects are required. This metric measures the effectiveness of the development process in identifying and fixing defects before and after the product is delivered. It helps in evaluating the overall quality of the software and the efficiency of the defect removal activities, such as reviews and testing. By considering both pre and post-delivery defects, the Defect Removal Efficiency provides a comprehensive assessment of the defect management process.

Nc's, Issues & Defects are prioritized with the help of Pareto Analysis. Pareto Analysis is a technique used to identify and prioritize the most significant factors contributing to a problem or issue. It is based on the 80/20 rule, which states that 80% of the problems are caused by 20% of the factors. By focusing on the vital few factors, Pareto Analysis helps in allocating resources and addressing the most critical issues first, leading to more efficient problem-solving and decision-making.