Project Management Fundamentals and Methodologies Questions

Scrum:

• What it is: Timeboxed, iterative Agile framework with fixed-length sprints (usually 2–4 weeks), defined roles (Product Owner, Scrum Master, Dev Team), sprint planning, daily standups, sprint reviews and retrospectives. Emphasizes committed sprint goals, incremental delivery, and frequent stakeholder feedback.
• When to use: New feature-driven product where cross-functional alignment and predictability are important.
• Example: Consumer mobile app launching major new features every quarter. Scrum helps the PM prioritize a sprint backlog, get regular demos for usability feedback, and adjust the roadmap each sprint based on metrics and user testing.

Kanban:

• What it is: Continuous flow system visualizing work on a board, limiting work-in-progress (WIP) to reduce bottlenecks, and optimizing cycle time. No fixed-length iterations; focus on throughput and continuous delivery.
• When to use: Maintenance, ops-heavy, or unpredictable incoming work with variable priorities.
• Example: SaaS platform’s customer support and bug-fix stream. Kanban lets the PM and engineering react to high-priority incidents, manage WIP limits to avoid context switching, and continuously deliver fixes.

Waterfall:

• What it is: Linear, phase-gated approach (requirements → design → implementation → testing → deployment). Changes are costly once requirements are locked.
• When to use: Projects with stable, well-defined requirements, heavy regulatory or safety constraints.
• Example: Medical device firmware where regulatory documentation, fixed specifications, and extensive validation are required. Waterfall provides clear documentation, traceability, and formal sign-offs aligning with compliance needs.

Trade-offs summary for a PM:

• Scrum = predictable cadence + iterative learning, requires discipline and cross-functional teams.
• Kanban = flexible flow + reduced lead time, requires strong process visibility and WIP control.
• Waterfall = upfront clarity and regulatory compliance, but low adaptability to changing market needs. Choose based on uncertainty, stakeholder cadence, and regulatory constraints.