Latest article
3 mins read
Why I Built SprintPulse: A Developer's Take on Retro Tools
I have spent 30 years building software and have sat through more retrospectives than I can count.
Read articleSprintPulse blog
Practical writing for retros that lead somewhere.
Notes on facilitation, action items, AI summaries, psychological safety, and the habits that keep teams from having the same retro twice.
3 mins read
Remote Retros Don't Have to Suck
Remote retrospectives fail for predictable reasons.
Read article
3 mins read
From Insight to Impact: Closing the Retro Loop
A retrospective can feel productive and still change nothing.
Read article
4 mins read
Retro Anti-Patterns That Quietly Break Team Improvement
Most bad retros do not fail in a dramatic way. People still join the call. Notes still get written. Someone still says "good discussion" at the end.
Read article
3 mins read
How Startups Can Run Retros Without the Ceremony
Startups often avoid retrospectives because the word sounds heavy. It suggests a calendar invite, a board, a facilitator, a long debate and a set of actions nobody will touch...
Read article
4 mins read
Anonymous Feedback Is a Temporary Fix, Not a Long-Term Strategy
Anonymous feedback has a place in retrospectives. It can give people enough cover to say the thing everyone is thinking, especially when trust is thin.
Read article
5 mins read
What AI Can (And Can't) Do for Your Retros
AI has arrived in retrospective tools, which means the claims can get silly fast.
Read article
4 mins read
The First 5 Minutes of Every Retro Should Be the Same
Retrospectives can use different formats. The opening should not change much.
Read article
5 mins read
Retro Metrics That Actually Matter
A team can run a retrospective every sprint and still fail to improve.
Read article
5 mins read
How to Rotate Retro Facilitators Without Chaos
If one person runs every retrospective, the team learns to treat the retro as that person's meeting.
Read article
4 mins read
Why Action Items Belong in Jira, Not a Google Doc
Google Docs are useful for notes. They are a bad place to manage retro action items.
Read article
4 mins read
Your Retro Tool Is Killing Your Retro
A retro tool can look busy and still fail the team.
Read article
4 mins read
The Prime Directive Is Not Just a Nice Quote
Every useful sprint retrospective starts with a small act of trust.
Read article
4 mins read
How to Run a Retro When Nobody Has Time
The release is late. A production bug is still open. Support is waiting for an answer. Someone looks at the calendar and asks the question everyone expected:
Read article
4 mins read
One Retro Format That Works for Most Teams
If you had to choose one retrospective format for ordinary sprint work, choose Plus/Delta.
Read article
4 mins read
What Google's Project Aristotle Taught Us About Better Retros
Google's Project Aristotle looked at why some teams worked well together while others struggled. The public write-up is still worth reading because it moved the focus away from...
Read article
5 mins read
The Real Reason Your Team Hides in Retros
Look at the next retrospective as if you were watching it for the first time.
Read article
4 mins read
Stop Picking Retro Formats Like You're Choosing a Netflix Film
You open your retro tool and get a wall of templates.
Read article
5 mins read
The Action Item Graveyard: Why Retro Improvements Die
Every team has a place where retro action items go to disappear.
Read article
5 mins read
Why Your Retrospectives Feel Like a Waste of Time
A bad retrospective has a rhythm you can recognise before the first card is written.
Read article