Is it true that Quality is only about the product's features.?

Quality also involves process consistency (conformance) and how well the product meets customer expectations (high performance design).

Is it true that You can improve quality for free.?

Improving quality typically requires an increase in cost, time, or scope.

Is it true that Independent demand is calculated.?

Independent demand is typically forecasted, while dependent demand is calculated.

Quality Management & Project Scheduling Essentials

This cheat sheet covers core concepts in Quality Management, including conformance, performance, costs of quality, and statistical process control, alongside key project scheduling tools like WBS, Network Diagrams, Critical Path, and Slack.

Core Principles

Quality has two main components: Conformance (process quality) and High Performance Design (product attributes).
Costs of Quality include Control Costs (prevention and appraisal) and Failure Costs (internal and external).
Statistical Process Control (SPC) uses charts to monitor and control process variation.
Project scope defines boundaries; scope creep adds unapproved changes, leading to delays and increased costs.
Work Breakdown Structure (WBS) breaks projects into manageable tasks.
Network Diagrams visualize task dependencies and sequences.
The Critical Path is the longest sequence of tasks determining project duration; any delay impacts the whole project.
Slack is the amount of time a task can be delayed without affecting the project end date.
Project scheduling involves balancing Time, Cost, and Scope.
Lean philosophy aims to maximize value by eliminating waste (Muda).
Just-in-Time (JIT) production minimizes inventory and forces problem-solving.
ERP systems integrate business functions for centralized data and decision-making.
Dependent demand is calculated (e.g., via MRP), unlike independent demand which is forecasted.
Lot-sizing rules (L4L, EOQ, POQ) balance ordering and holding costs with demand.

Action Steps

Identify the type of data (attributes vs. variables) for SPC.
Choose the appropriate control chart (p-chart, c-chart, x-chart, R-chart).
Define project scope clearly and manage changes rigorously.
Break down projects into a WBS for better organization.
Construct network diagrams to understand task dependencies.
Identify the critical path to focus on essential tasks.
Calculate slack for non-critical tasks to understand flexibility.
Balance time, cost, and scope tradeoffs during scheduling.
Implement Lean principles to eliminate waste and improve efficiency.
Utilize JIT to minimize inventory and expose problems.
Leverage ERP systems for integrated business management.
Calculate dependent demand using inputs like MPS, BOM, and Inventory Records.
Select appropriate lot-sizing rules (L4L, EOQ, POQ) based on cost and inventory goals.

Formulas

Slack = Latest Start – Earliest Start
Slack = Latest Finish – Earliest Finish

Key Terms

Conformance: Quality related to how well processes meet specifications and have low variability, leading to fewer errors.
High Performance Design: Quality related to the product's attributes and how they meet customer expectations for reliability and psychological impression.
Defect: Any instance where a product or process fails to meet customer expectations.
Control Costs: Costs incurred to prevent or detect defects before they occur.
Failure Costs: Costs incurred when defects occur, either internally during production or externally after delivery.
SPC: Statistical Process Control; uses statistical techniques to monitor and improve processes.
Attributes (SPC): Qualitative, discrete data measured in counts (e.g., defective vs. non-defective).
Variables (SPC): Quantitative, continuous data measured on a scale (e.g., weight, length).
p-chart: SPC chart tracking the proportion (percentage) of defective items.
c-chart: SPC chart tracking the total number of defects per unit.
x-bar chart: SPC chart tracking the average value of a measured variable over time.
R-chart: SPC chart tracking the range (variability) within a sample.
Project Scope: Defines the boundaries of a project, including what is included and excluded.
Scope Creep: Uncontrolled addition of requirements or features after a project has started.
WBS: Work Breakdown Structure; a visual tool that breaks down a project into smaller, manageable activities.
Network Diagram: Visual representation of project activities and their dependencies using nodes and arrows.
Critical Path: The longest sequence of activities in a project, determining the shortest possible project duration.
Slack: The amount of time an activity can be delayed without delaying the project's overall completion date.
Muda: Japanese term for waste; anything that does not add value to the customer.
JIT: Just-in-Time; a production strategy that delivers goods only when needed.
ERP: Enterprise Resource Planning; an integrated system connecting all business functions.
IS: Information System; a broader term for systems that collect, process, and distribute information.
Dependent Demand: Demand for a product that is derived from the demand for another product (e.g., tires depend on car demand).
MPS: Master Production Schedule; outlines what needs to be produced and when.
BOM: Bill of Materials; lists all components needed to make a product.
L4L: Lot-for-Lot; a lot-sizing rule ordering exactly what is needed, minimizing holding costs.
EOQ: Economic Order Quantity; a lot-sizing rule balancing ordering and holding costs.
POQ: Periodic Order Quantity; a lot-sizing rule ordering enough for a set time period, reducing order frequency.

Pro Tips

Use both x-chart and R-chart together for a complete picture of process stability and consistency.
Inventory hides problems; reducing it makes issues visible and forces solutions.
Cellular flow is generally better for Lean due to reduced movement and increased flexibility.
ERP is a type of IS, but IS is a broader concept.
The key difference between IS and ERP for exams: IS = general, ERP = integrated company-wide.

Pitfalls to Avoid

Confusing Conformance with High Performance Design.
Underestimating Failure Costs; prevention is usually cheaper.
Using only one control chart (x-chart or R-chart) can be misleading.
Allowing scope creep without proper management.
Forgetting that WBS does NOT show timing or order of tasks.
Ignoring slack; non-critical tasks still have flexibility.
Trying to improve quality, reduce cost, or reduce time without considering the impact on the other factors.
Relying solely on forecasts for dependent demand.
Choosing lot-sizing rules without considering their impact on inventory and ordering costs.

Myth vs Reality

Quality is only about the product's features.: Quality also involves process consistency (conformance) and how well the product meets customer expectations (high performance design).
You can improve quality for free.: Improving quality typically requires an increase in cost, time, or scope.
Independent demand is calculated.: Independent demand is typically forecasted, while dependent demand is calculated.

Real World Examples

A car manufacturer uses SPC to monitor the dimensions of engine parts.: Using x-charts to track average engine dimensions and R-charts to track variability ensures consistent engine performance.
A software development team adds new features mid-project without formal approval.: This is scope creep, which will likely lead to project delays and increased development costs.
A construction project has a critical path involving foundation, framing, and roofing.: Any delay in these specific tasks will directly delay the entire project's completion.
A factory produces car tires.: The demand for tires is dependent demand, derived from the demand for cars.
An e-commerce company uses JIT principles.: They aim to receive inventory from suppliers only as needed for customer orders, minimizing storage costs and waste.