# ScatterSpoke

> Agile Retrospectives, Daily Stand Ups, and Developer Surveys Transformed with AI Insights

## Key pages
- [Home](https://www.scatterspoke.com/)
- [Pricing](https://www.scatterspoke.com/pricing)
- [AI Interviews](https://www.scatterspoke.com/ai-interviews)
- [Surveys](https://www.scatterspoke.com/surveys)
- [About](https://www.scatterspoke.com/about)
- [FAQ](https://www.scatterspoke.com/faq)
- [Blog](https://www.scatterspoke.com/blog)

## Blog posts
- [Why We Chose Astro for Our New Website](https://www.scatterspoke.com/post/why-we-chose-astro-for-our-new-website): Astro's Islands Architecture took our Lighthouse scores from the 70s to 90+ and cut page load times 60%. Here's how we rebuilt our content-heavy site on it.
- [3 Metrics You Should Review at Every Retrospective](https://www.scatterspoke.com/post/3-metrics-you-should-review-at-every-retrospective): Cycle time, WIP, and throughput turn subjective retros into data-driven meetings. Here's how to track all three and act on what they reveal.
- [The Power of Developer Feedback](https://www.scatterspoke.com/post/the-power-of-developer-feedback): Developers see the bugs and friction leaders miss. Build a feedback loop that collects their insights, acts on them, and closes the loop to earn their trust.
- [Why Quarterly Retros Ensure Nothing Changes in Agile Release Trains](https://www.scatterspoke.com/post/how-quarterly-retrospectives-slow-down-agile-release-trains): Two dozen RTEs told us the same thing: quarterly feedback stalls Agile Release Trains. See the five failure modes and how to tighten the loop.
- [DORA Metrics](https://www.scatterspoke.com/post/dora-metrics): DORA: A framework for efficiency and flow
- [S.P.A.C.E. Framework](https://www.scatterspoke.com/post/space-framework): SPACE: A Framework for Understanding Developer Productivity
- [5 Things You May Not Know About the SAFe Inspect and Adapt Event](https://www.scatterspoke.com/post/five-things-you-may-not-know-about-the-safe-inspect-and-adapt-i-a-event): A facilitator of ten-plus SAFe Inspect and Adapt events debunks the myths, from fishbone diagrams to what the problem-solving workshop really does.
- [How ScatterSpoke Developers Improved Developer Productivity with Cody](https://www.scatterspoke.com/post/how-scatterspoke-developers-improved-flow-state-time-with-ai-coding-assistant-cody): ScatterSpoke's developers adopted Cody, an AI coding assistant, and gained more flow state time, faster delivery, and fewer bugs. Here's what changed.
- [How Engineering Metrics Can Improve Your Software Development Process](https://www.scatterspoke.com/post/how-incorporating-engineering-metrics-into-retrospectives-can-transform-your-software-development-process): Pair engineering metrics with retrospective feedback to spot bottlenecks objectively. Best practices for baselines, visualization, and follow-through.
- [5 Tips for Facilitating Productive Team Retrospectives](https://www.scatterspoke.com/post/5-tips-for-facilitating-productive-team-retrospectives): Great retro facilitation hinges on five things: the right attendees, open discussion, no groupthink, owned action items, and simple tools.
- [5 Tools to Boost your Participation Rate](https://www.scatterspoke.com/post/5-tools-to-boost-your-participation-rate): Quiet retros stall improvement. Five facilitation moves, from opening questions to strategic silence, get your whole team talking again.
- [548 Days to Fix 1 Line of Code](https://www.scatterspoke.com/post/548-days-to-fix-1-line-of-code): How many retrospectives have you been in where improvement didn't happen? The team meets, writes stickies, forms action items, and not much changes.
- [7 Online Retro Board Templates for Remote Teams](https://www.scatterspoke.com/post/7-online-retro-board-templates-for-remote-teams): Seven retro board templates, from Sailboat and Starfish to DAKI and WARP, with guidance on when each format fits your remote team's stage.
- [Agile Retro Antipatterns Most Scrum Masters Never Realize](https://www.scatterspoke.com/post/agile-retrospective-antipatterns-that-most-scrum-masters-never-realize): Nine retrospective antipatterns quietly sabotage your sprints, from recorded retros to unowned action items. Spot them and apply the fix for each.
- [Focusing on Individuals & Interactions While Responding to Change](https://www.scatterspoke.com/post/bringing-focus-to-individuals-interactions-while-responding-to-tremendous-change): Agile coaches at Uplight share how their teams stayed connected through COVID: remote working agreements, daily check-ins, and grace under pressure.
- [Break the Ice of Your Retrospectives](https://www.scatterspoke.com/post/break-the-ice-of-your-retrospectives): When an agile team gets frustrated with the situation where nothing ever changes, it is easy to say that the retrospective became useless.
- [Coaching Through Conflict](https://www.scatterspoke.com/post/coaching-through-conflict): The tricky side of conflict is that you don't want to eliminate it all together. As long as it is healthy, conflict within a team is actually a sign of life.
- [Using Daily Retros at Agile2022 to Enable Improvement](https://www.scatterspoke.com/post/daily-retros-at-agile2022-to-enable-improvement): ScatterSpoke ran daily retrospectives at Agile2022 to sharpen its pitch fast. See what daily retros surfaced and when to shorten your own cadence.
- [Developers Hate Your Retros](https://www.scatterspoke.com/post/developers-hate-your-retros): Developers check out of retros for three reasons: identical formats, ignored action items, and dominant voices. Here's how to fix all three.
- [How to Run a Retrospective Your Team Can Get Excited About](https://www.scatterspoke.com/post/exciting-team-retrospectives): Turn the retrospective into your team's favorite meeting: send an agenda ahead, vary formats, archive learnings, and act on every takeaway.
- [Good Engineering Managers Don't Weaponize Metrics](https://www.scatterspoke.com/post/good-engineering-managers-dont-weaponize-metrics): Single-metric management breeds bad incentives and broken trust. Pair related metrics like DORA with empowerment so engineers can do great work.
- [How DORA Metrics Can Unlock Developer Potential](https://www.scatterspoke.com/post/how-dora-metrics-unlock-developer-potential): Lines of code and velocity measure the wrong things. The four DORA metrics show how your DevOps team really performs and where to improve next.
- [How to Improve Retrospective Meetings](https://www.scatterspoke.com/post/how-to-improve-retrospective-meetings): Five changes make retrospective meetings worth having: participant ownership, anonymous input, real data, follow-through, and integrated tools.
- [Improving Begins with Measuring](https://www.scatterspoke.com/post/improving-begins-with-measuring): What gets measured gets managed, but only if you measure outcomes, not just outputs. How to pick metrics, keep balance, and adjust as work changes.
- [Making meaning of cultural values and preferences through retros](https://www.scatterspoke.com/post/making-meaning-of-cultural-values-and-preferences-through-retrospectives): A team that starts standups late isn't undisciplined - it may hold different values around time. Map cultural values in your next retrospective to find out.
- [How Feedback Loops and Retrospectives Accelerate  Software Delivery](https://www.scatterspoke.com/post/power-of-feedback-loops): Feedback loops keep software delivery on track, and retrospectives are where they all meet. Learn the loop types, common pitfalls, and how to optimize them.
- [Retrospect on Your Retrospectives to Keep Them Fresh](https://www.scatterspoke.com/post/retrospect-on-your-retrospectives-to-keep-them-fresh): Ask the same retro questions and you get the same answers. Geoff Watts explains how running a retrospective on your retrospectives restores lost engagement.
- [Running Scaled Retrospectives](https://www.scatterspoke.com/post/running-scaled-retrospectives): A scaled retrospective provides the chance to expand scope of improvements beyond the individual team.
- [ScatterSpoke Retrospectives - an Atlassian Ventures Portfolio Company - Available on AWS Marketplace](https://www.scatterspoke.com/post/scatterspoke-available-on-aws-marketplace): ScatterSpoke Retrospectives is now on AWS Marketplace, so teams can purchase through an existing AWS EDP and roll out AI-powered retro analytics faster.
- [Seeing the System With the WADE Matrix](https://www.scatterspoke.com/post/seeing-the-system-with-the-wade-matrix): The WADE Matrix retrospective plots what went well against what your team can control, exposing the bigger system. Get the format plus facilitation tips.
- [Stop Wasting Time in Retrospectives](https://www.scatterspoke.com/post/stop-wasting-time-in-retrospectives): We need to talk about what to change to fix the big problems. These are not short conversations. This should be the priority of our time together as a team.
- [The Importance of Facilitation in Retrospectives](https://www.scatterspoke.com/post/the-importance-of-facilitation-in-retrospectives): Skilled facilitation turns retrospectives into safe, honest conversations. Melissa Boggs explains why it matters and how any team member can build the skill.
- [The "Theory of Everything" Retrospective](https://www.scatterspoke.com/post/the-theory-of-everything-retrospective): Built on Ken Wilber's Integral Theory, this retro format spans four quadrants - self, culture, process, and system - to build ownership beyond process fixes.
- [Three Rules for Remote Retrospectives](https://www.scatterspoke.com/post/three-rules-for-remote-retrospectives): Cameras on, silence used sparingly, and disciplined follow-up: three hard-won rules from facilitating remote retrospectives for a global project team.
- [The Importance of Retrospective Rigor for Agile Marketers](https://www.scatterspoke.com/post/the-importance-of-retrospective-rigor-for-agile-marketers): Marketers are already in too many meetings; why should they keep up with some ridiculous Agile thing that just takes up space on their calendar?
- [Why Developers Are Using The SPACE Framework For Productivity](https://www.scatterspoke.com/post/why-developers-use-space-framework): Lines of code and ticket counts distort developer productivity. The SPACE framework measures five dimensions instead, and developers prefer it.
- [Why Engineers Should Be In Charge Of Engineer Productivity](https://www.scatterspoke.com/post/why-engineers-should-be-in-charge-of-engineer-productivity): Quantitative productivity metrics frustrate engineers and reward the wrong work. Put engineers in charge with retros, trust, and tools that empower them.
- [Why Retros Are Good For Engineer Enablement](https://www.scatterspoke.com/post/why-retros-are-good-for-engineer-enablement): Retros aren't just an Agile thing, they're a critical way to empower engineers and enable them to be in charge of their own improvement.
- [Why Scaling Retros Is the Next Step in Your Agile Transformation](https://www.scatterspoke.com/post/why-scaling-retros-is-the-next-step-in-your-agile-transformation): Scale retrospectives across team, portfolio, and organizational levels to break down silos - a proven model with guidance on frequency and feedback volume.
- [Why ScatterSpoke Is Making a Big Change](https://www.scatterspoke.com/post/why-scatterspoke-is-making-a-big-change): One customer wanted surveys, engineering metrics, and retros in one tool. ScatterSpoke answered with DORA and SPACE metrics, goal tracking, and AI analysis.
- [Yet Another R.E.T.R.O Format](https://www.scatterspoke.com/post/yet-another-r-e-t-r-o-format): Matt Barcomb's R.E.T.R.O format - Reinforce, Explore, Try, Remove, Observe - reframes stale retro categories and tackles why teams disengage.
- [Your Retrospective Format Doesn't Matter](https://www.scatterspoke.com/post/your-retrospective-format-doesnt-matter): Retros fail from vague data, not boring formats. Balance five data types - stats, past, observations, kudos, events - to make every retrospective actionable.
- [How ScatterSpoke Used Daily Retrospectives at Agile2022 to Enable Improvement](https://www.scatterspoke.com/post/time-limited-event): We have clear improvement goals for our team and we wanted to maximize our learning in this fast-paced environment.