Skip to content

Product & Projects

Product development and project management are critical capabilities for bringing new products and services to market. This topic covers both the design process (QFD, Concurrent Engineering) and project execution approaches (Waterfall, Agile). Understanding these frameworks helps organizations choose the right approach based on product characteristics, requirement stability, and time pressures.

Building a new product is like planning a big school project:

QFD (Quality Function Deployment) = Asking your classmates what they want BEFORE you build it

  • Kids say: “We want a cool, easy-to-use, colorful toy!”
  • You translate: “Cool” = has lights, “Easy” = one button, “Colorful” = 5 bright colors
  • Now you know EXACTLY what to build!

Concurrent Engineering = Everyone works TOGETHER from the start

  • Old way (Over the Wall): Designers draw it → throw it “over the wall” to builders → builders say “This can’t be built!” → back to square one
  • New way (Concurrent): Designers + builders + painters all work together from day one → fewer problems!

Waterfall = Following a recipe step-by-step

  • Step 1: Read whole recipe → Step 2: Buy ingredients → Step 3: Mix → Step 4: Bake → Step 5: Eat
  • Problem: Can’t go back! If you forgot sugar, too late!

Agile = Cooking in small batches and tasting as you go

  • Make a little → taste → adjust → make more → taste again
  • Good: Can fix mistakes early

Product development involves two key decisions:

  1. How to capture customer needs? → QFD (Quality Function Deployment) translates voice of customer into design specifications
  2. How to organize the development process? → Choose between Sequential (Waterfall) vs. Iterative (Agile) vs. Simultaneous (Concurrent Engineering)

QFD ensures the product reflects what customers value. Concurrent Engineering speeds development by having cross-functional teams work simultaneously. Waterfall provides structure for well-understood products. Agile enables adaptation for uncertain requirements.

FrameworkPurposeKey CharacteristicSource
QFDTranslate customer wants to design specsVoice of Customer → House of QualityChapter3.pptx, Slide 22-24
Concurrent EngineeringSpeed development through collaborationSimultaneous, not sequentialChapter3.pptx, Slide 26
WaterfallSequential product developmentSix phases, one after anotherChapter3.pptx, Slide 9-15
AgileIterative development with learningBuild-Test-Learn cyclesChapter3.pptx, Slide 17

QFD Example (Auto Industry): Customer expectations → Customer requirements → Vehicle specifications

  • Customer: “Car door should feel solid at highway speeds”
  • Requirement: “Door should close with satisfying sound”
  • Engineering: Door weight, seal tightness, latch specifications

Concurrent Engineering Example: Traditional: “We design it, you build it” (over the wall) Concurrent: “Let’s work together simultaneously”

  • QFD: Ensures product design reflects customer value, reduces redesign (Toyota: 60% cost reduction)
  • Concurrent Engineering: Reduces development time by up to 80%
  • Waterfall: Best for stable requirements (sporting goods, furniture, tools)
  • Agile: Best for uncertain requirements, enables learning through iteration
  • Design for Manufacturing (DFM): Designing products that are easy to manufacture
  • Rapid Prototyping: Building quick prototypes to test and learn
  • Cross-functional Teams: Teams with members from multiple disciplines
  • Voice of Customer (VOC): Customer needs stated in their own words
ConceptKey IdeaWhen to Use
QFDVoice of Customer → Design SpecsWhen customer needs must drive design
Concurrent EngineeringSimultaneous developmentWhen speed to market is critical
WaterfallSequential phasesWhen requirements are stable
AgileIterative cyclesWhen requirements are uncertain

Key Concepts Summary:

  • QFD = Voice of Customer → Design
  • Concurrent = Simultaneous
  • Waterfall = Sequential
  • Agile = Iterative

Exam Tips:

  • QFD STARTS with customer (not engineering)
  • Concurrent = SIMULTANEOUS work (not sequential handoffs)
  • Waterfall = 6 phases in order (can’t go back)
  • Agile = Build-Test-Learn cycles (high/medium priorities first)
  • Chapter3.pptx [Slide 9-15, 17, 22-24, 26]
  • Chapter4.pptx
  • MGH_book.pdf [p.50]