This guide provides an overview of these features with links to related help articles where you can dive in and learn more.

example of a Waffle board using labels, epics, dependencies, and milestones to organize and plan work

Labels are a great way to organize cards on a Waffle board.  Waffle uses GitHub labels which can be assigned to cards.  Labels are automatically displayed on cards, making it easy to find and filter cards.  Common labels are "bug," "customer request," "feature feedback," etc. to keep similar cards grouped together.  

Waffle boards also use labels to organize issues and pull requests into columns.

An epic can be thought of as a group of related work.  Epics provide the ability to see the status of the overall epic at a glance and quickly filter a Waffle board to only show cards related to the epic.  Epics also support nested parent / child relationships, so an epic can also be a child of a larger epics (ex. a goal, outcome, or strategy).  Waffle visually displays parent epics on child cards cards, making it easy to understand the relationship between cards at a glance.  Epics are created using keywords "parent of" or "child of"  in the description field of issues and pull requests.

A dependency is a piece of work that relies on another piece of work.  In Waffle, an card can be the one "requiring" another card or it can be the one that is "required". Waffle visually displays dependencies on cards, making it easy to see the relationships between pieces of work at a glance.  Dependencies can be created by including keywords "requires" or "required by" in the description field or title of issues and pull requests.

Milestones are a way to organize work that shares a common due date.  Waffle uses GitHub Milestones, which can be assigned to cards within the card detail modal, making it easy to filter a Waffle board to focus on work that's part of the milestone. Milestones are useful when working towards a big launch date or if you're working in sprints (ex. teams that practice Scrum).  Waffle's burndown graph  makes it easy to track progress towards a milestone.

Waffle layers in functionality on top of GitHub issues where you can estimated using story points (specifically, Fibonacci-like numbers 1-100).  Estimates, when combined with a team's capacity based on a Throughput Graph,  enable more accurate predictions of when work is likely to be delivered.

Each column on a Waffle board show the total count and story point estimate of cards in each column, making it easy for teams to plan to a certain amount of work and make sure they don't have too much work in progress.

WIP Limits

WIP limits are usually used to frame the capacity of your team and provide a warning when your team is taking on more work then there is capacity.

Release Report
Waffle's historical throughput report is useful for status reporting and shows work completed in the last 30 days. 

Columns are used to organize cards on a Waffle board based on their current status.  Columns can easily be added, removed, and customized to reflect your workflow. You can automatically move cards across your board based on your actions in GitHub by enabling WaffleBot. 

Keep Learning!

Did this answer your question?