Agile vs waterfall project management: when to use each and how to set up SmartSuite

Executive overview

Most businesses do not run pure agile or pure waterfall — they operate somewhere in between. This video contrasts the two methodologies, explains when each applies, and walks through SmartSuite's free agile template in detail. The agile structure covers sprints, stories, bugs, epics, ideas, and team meeting logs, showing how they connect. If you cannot commit to pure waterfall, default to an agile structure — it is far easier to add waterfall-style pre-planning to an agile setup than the reverse.

Agile vs waterfall: core distinction

• Agile works in short iterative cycles (sprints), evaluating and adjusting direction after each one.
• Waterfall plans the entire project upfront and executes sequentially with no built-in loops.
• Agile suits unknown destinations, uncertain paths, and work that needs regular stakeholder feedback.
• Waterfall suits known destinations, repeatable processes, and projects requiring full cost/timeline predictability.
• Large construction or multimillion-dollar projects lean waterfall because stakeholders need predictability.
• Agile works best with small, tight-knit teams — historical context lives in team memory, not documentation.

When agile is the right choice

• Unknown destination: you know the problem to solve but not the exact solution.
• Unknown path: steps and resources are not fully defined before you start.
• Frequent feedback needed: stakeholders want to review progress at regular intervals, not just at the end.
• Iterative learning: each sprint builds on previous ones — like a detective accumulating clues across seasons.
• Throwing someone mid-project into agile is hard precisely because context is experiential, not documented.

The agile-ish middle ground

• Most real projects blend both: some pre-planning with room for change and discovery.
• Recommendation for practitioners in the middle: default to an agile structure and bend it waterfall-ward.
• Starting with a waterfall structure and adding agile elements is much harder to retrofit.
• Adjusting a handful of fields in an agile template can approximate the pre-planning feel of waterfall.

SmartSuite agile template: sprints

• Sprints are numbered, time-boxed units of work — the cyclical containers for stories and bugs.
• Each sprint record holds: date range, status, sprint name, hotfix flag, notes, linked stories, and linked bugs.
• Teams create sprint containers in advance (weekly, bi-weekly, or monthly) and populate them as each sprint arrives.
• Story and bug counts are visible at a glance from the sprint overview via summary count fields.

SmartSuite agile template: stories and issues

• Stories are chunks of value delivered to the end user — what the user gains from a feature or improvement.
• Each story record includes a narrative overview, estimation readiness, story points, responsible party, and linked epics.
• Story points use a Fibonacci sequence (1, 2, 3, 5, 8, 13…) as a relative complexity scale — not time estimates.
• Human beings are poor at estimating time but can reliably compare relative effort sizes.
• Very large story points signal the story should be broken into smaller pieces to fit within a sprint.
• Issues/bugs are chunks of problems that negatively affect the end user — tracked and connected to sprints and epics.
• Issue records include priority, severity, and problem-solving notes.
• Even non-software teams benefit from bug tracking: broken invoice links, client complaints, access gaps all belong here.
• Tracking issues prevents a perpetual firefighting loop and surfaces systemic patterns over time.

SmartSuite agile template: epics

• Epics are collections of stories that together fulfil a broader goal or feature arc.
• Two planning styles: execute one epic at a time (epic-level planning) or plan story-by-story within epics (story-level planning).
• The default template plans at story level; epic connections provide overall progress visibility.
• Epics roughly correspond to milestones for teams coming from waterfall thinking.
• Each epic shows linked stories and related bugs, giving a full picture of what went into a major accomplishment.

Ideas and team meetings

• Ideas is a quarantine zone for half-baked concepts — prevents every idea from immediately becoming a task.
• Team members can vote on ideas inside SmartSuite; vote counts surface the most valued potential features.
• Review ideas when planning future sprints to decide what becomes the next epic or story.
• Team meetings and standups centralise meeting agendas, owners, dates, types, and recurring standup questions.
• Meeting titles auto-generate from owner + date fields using SmartSuite's formula title feature.
• Standup question fields are configurable — adapt defaults to whatever your team asks on a recurring basis.
• Centralised meeting notes prevent context from being lost and keep everything in one searchable place.

What to steal if the full template is too much

• Issues tracking alone is worth adopting for any business — track every recurring problem, review regularly.
• Ideas backlog prevents reactive task creation and helps teams prioritise the highest-impact work.
• Meeting standups app is a staple regardless of methodology — waterfall, agile, or agile-ish.
• The entire template runs on SmartSuite's free plan; delete demo data in one click and start fresh.