Jan
Goals are promises we make to our future selves. But too often, we forget how we felt the last time we set them. FAST goals remind us to keep those promises visible, frequent, and alive—so we can align today’s actions with tomorrow’s ambitions. If you’re ready to rethink how your team sets and achieves goals, let’s explore why FAST goals might be the game-changer you’ve been looking for.
FAST vs. SMART Goals: A Guide for Agile Scrum Masters
As an Agile Scrum Master, you know that goal-setting is a cornerstone of effective team performance. For years, many of us relied on SMART goals—Specific, Measurable, Achievable, Relevant, and Time-bound. But recently, I’ve switched to FAST goals, and the results have been transformative. If you’re looking to improve how your teams set and achieve goals, let me explain the difference between SMART and FAST goals, when to use each, and how to apply FAST goals in your Agile environment.
What Are SMART Goals?
SMART goals have been the gold standard for decades. They are designed to be clear and actionable, with each letter representing a criterion:
- Specific: The goal is well-defined.
- Measurable: Progress can be tracked.
- Achievable: The goal is realistic.
- Relevant: It aligns with broader objectives.
- Time-bound: It has a deadline.
For example, a SMART goal might be: “Increase sprint velocity by 10% within the next three months.”
This goal is clear, measurable, and time-bound, but it has limitations in fast-paced Agile environments.
What Are FAST Goals?
FAST goals—Frequently discussed, Ambitious, Specific, and Transparent—are better suited for Agile teams because they emphasize adaptability, collaboration, and ambition.
Here’s how FAST goals differ:
- Frequently Discussed: Goals are revisited and adjusted regularly, aligning with Agile’s iterative nature.
- Ambitious: Goals push teams to think big and innovate, rather than settling for incremental improvements.
- Specific: Like SMART goals, FAST goals are clear and actionable.
- Transparent: Goals are visible to everyone, fostering accountability and alignment.
FAST goals thrive in environments where change is constant, and teams need to pivot quickly. They encourage continuous feedback and learning, which are central to Agile principles.
Industry Experts on FAST Goals
The shift from SMART to FAST goals has gained traction among industry leaders. Donald Sull, a senior lecturer at MIT Sloan School of Management and co-author of the Harvard Business Review article that introduced FAST goals, explains:
“FAST goals are designed for today’s dynamic business environment. They emphasize frequent discussions and transparency, which are critical for teams that need to adapt quickly. Unlike SMART goals, which can become rigid, FAST goals encourage ambition and flexibility.”
Similarly, Charles Duhigg, author of The Power of Habit and Smarter Faster Better, highlights the importance of transparency and ambition in goal-setting:
“When goals are transparent and ambitious, they create a shared sense of purpose. Teams are more likely to collaborate effectively and push boundaries when everyone understands the bigger picture.”
These insights underscore why FAST goals are particularly effective in Agile environments, where adaptability and collaboration are key.
When to Use SMART vs. FAST Goals
To help you decide when to use each type of goal, here’s a matrix that outlines their ideal applications within the Scrum framework:
| Scenario | SMART Goals | FAST Goals |
|---|---|---|
| Sprint Planning | Use SMART goals to define clear, measurable sprint objectives (e.g., “Complete 20 user stories this sprint”). | Use FAST goals to set ambitious, team-wide objectives (e.g., “Deliver a fully integrated feature by the end of the sprint”). |
| Daily Stand-ups | Not typically used here. | Use FAST goals to keep the team aligned on daily priorities and progress. |
| Sprint Reviews | Use SMART goals to evaluate whether sprint objectives were met. | Use FAST goals to discuss what worked, what didn’t, and how to improve. |
| Retrospectives | Not typically used here. | Use FAST goals to set ambitious improvement targets for the next sprint. |
| Backlog Refinement | Use SMART goals to define specific, time-bound tasks (e.g., “Refine 10 backlog items by Friday”). | Use FAST goals to align the team around ambitious refinement outcomes (e.g., “Ensure all backlog items are sprint-ready by the next planning session”). |
| Personal Development | Use SMART goals for individual growth (e.g., “Complete a certification in three months”). | Use FAST goals for team-wide skill development (e.g., “Upskill the entire team in DevOps practices within six months”). |
Crafting FAST Goals: Examples for Agile Teams
Let’s look at how you can craft FAST goals for your team. Suppose you’re working on a product backlog refinement process. Here’s how a FAST goal might look:
- Frequently Discussed: “Every sprint review, we’ll assess our backlog refinement process and identify one improvement to implement in the next sprint.”
- Ambitious: “We aim to reduce backlog grooming time by 50% while improving the clarity of user stories.”
- Specific: “We’ll achieve this by introducing a new story-pointing technique and training the team on it.”
- Transparent: “Our progress will be tracked on the team’s Kanban board, and updates will be shared during daily stand-ups.”
Another example could focus on team collaboration:
- Frequently Discussed: “During retrospectives, we’ll evaluate how effectively we’re collaborating across functions and adjust our approach as needed.”
- Ambitious: “We aim to eliminate silos between development and QA, ensuring zero handoff delays.”
- Specific: “We’ll achieve this by co-locating QA engineers with development teams and holding joint planning sessions.”
- Transparent: “Our progress will be visible on a shared dashboard, and blockers will be escalated immediately.”
Why FAST Goals Fit Agile Frameworks
FAST goals align perfectly with Agile frameworks like Scrum, Kanban, and LeSS. They encourage teams to think big while remaining flexible. For example, in Scrum, FAST goals can be integrated into sprint planning and retrospectives. In Kanban, they can guide continuous improvement efforts. And in LeSS, they help align multiple teams around a shared vision.
Making the Switch
If you’re used to SMART goals, transitioning to FAST goals might feel unfamiliar at first. Start small. Introduce one FAST goal in your next sprint and see how the team responds. Encourage frequent discussions and make progress visible. Over time, you’ll notice that FAST goals foster a culture of ambition, transparency, and adaptability—qualities that are essential for Agile success.
As an Agile Scrum Master, your role is to help your team set goals that drive meaningful progress. FAST goals are an effective way to achieve this. They encourage teams to aim high, stay aligned, and adapt—exactly what Agile is all about. Give them a try, and let me know how they work for you!
By incorporating insights from industry experts like Donald Sull and Charles Duhigg, you can confidently advocate for FAST goals as a modern, Agile-friendly approach to goal-setting.
Learn More
- User Story Templates
- How to Decompose User Stories using Google Gemini
- How to Write User Stories Manually v Google Gemini
- Connect with us on Linkedin
- Get more tips in our weekly newsletter
