Project Management Fundamentals and Methodologies Questions

Swimlanes and WIP limits make capacity visible and enforce focus so a team doesn't overcommit across initiatives. Swimlanes separate concurrent work streams (e.g., Product A, Product B, Technical Debt) so stakeholders instantly see where effort is going. WIP limits cap how many items can be in a column (typically “In Progress” or “Doing”) per swimlane or globally, preventing context-switching and exposing bottlenecks.

Example configuration for a team balancing two core products + tech debt (6 devs, 2 QA):

• Swimlanes (horizontal): Product A, Product B, Tech Debt.
• Columns: Backlog | Ready | Doing | Review | Done.
• WIP limits:
  • Doing (per swimlane): Product A = 2, Product B = 2, Tech Debt = 1 (total Doing ≤ 5).
  • Review (global): ≤ 3 to avoid QA backlog.
    Rules: Team pulls only when Ready and within WIP; urgent bug can borrow Tech Debt slot with explicit swap and stakeholder notice. This setup ensures predictable flow, makes trade-offs explicit, and helps the PM re-prioritize when swimlane limits are consistently hit.

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.