Agile vs Waterfall Explained
Agile uses iterative sprints adapting as you go with incremental shipping. Waterfall plans everything upfront executing linearly to ship at end.
Welcome to the complete index of every article in our Project Management collection on When Notes Fly. This page lists all 15 articles in the section, organized alphabetically for easy reference. Each piece is researched, written by hand, and grounded in academic sources, professional practice, or empirical data. Whether you are diving into Project Management for the first time or returning to find a specific article, the index below gives you direct access to the full collection within Work Skills.
If you are new to Project Management, we recommend starting with the foundational explainers and definitions before moving on to specific case studies, applied frameworks, and deeper analytical pieces. Articles are written for thoughtful readers who want substance over summary, with clear explanations of how ideas connect, where they come from, and why they matter. Use this index as a navigational map: skim the titles, read the short summaries, and click through to the pieces that draw your interest. Each article also links to related material so you can follow a thread of ideas across our entire Work Skills library.
Agile uses iterative sprints adapting as you go with incremental shipping. Waterfall plans everything upfront executing linearly to ship at end.
Delivery vs quality tradeoff: Fast with low quality creates technical debt. High quality late misses opportunity. Balance with clear quality thresholds.
Execution systems turn plans into results through clear ownership of responsibilities, regular check-ins for progress reviews, and surfacing blockers early.
How to run an agile retrospective that produces real change: formats like Start Stop Continue and 4Ls, psychological safety requirements, common failure modes, and remote retrospectives.
Planning vs execution balance: Over-planning creates analysis paralysis. Under-planning causes thrashing and wasted rework. Find the right balance.
Projects fail from unclear goals, scope creep expansion, poor communication with misaligned expectations, and inadequate resources or unrealistic timelines.
Project management basics: define scope of what's being built, plan timeline for delivery, assign clear ownership, and track progress toward completion.
Most project dashboards track vanity numbers that hide real problems. Learn which metrics predict delivery and which ones you are wasting time reporting.
Project risk management: Identify risks early, assess impact severity, prioritize by likelihood times severity, mitigate to reduce probability and impact.
Scope creep: project expands beyond original plan through added features, changed requirements, and unclear boundaries causing delays and budget overruns.
Stakeholder management: identify who has influence, understand their interests and concerns, communicate proactively, manage expectations, build relationships.
Kanban is a visual workflow management method from Toyota that limits work-in-progress and improves flow. Learn how it works, its metrics, and when to use it.
Operational excellence is a systematic approach to improving performance through waste elimination, continuous improvement, and cultural change. Here is how it works.
Scope creep is one of the top causes of project failure. Learn what causes it, how change control works, and how to say no to stakeholders without damaging relationships.
When employees optimize for KPIs instead of goals, metrics lose their meaning. Learn how metric gaming happens, why it's rational, and how to design better measures.
« Back to Project Management · All Work Skills Articles · Home