Autistic Bowler Achieves Dream With His First Perfect 300 Game And Joins the PBA as a Pro

On March 25, an autistic bowler who recently entered the Professional Bowlers Association achieved something he’s been dreaming about for years—his first-ever 300 game.

For most casual bowlers, a sanctioned perfect game is rare. For Matt Sipes, it represented so much more than just 12 strikes. It was the result of years of dedication, focus, and determination, and although there have been challenges along the way, he never gave up on his goal.

How to connect with AgileDad:

- [website] ⁠https://www.agiledad.com/⁠

- [instagram] ⁠https://www.instagram.com/agile_coach/⁠

- [facebook] ⁠https://www.facebook.com/RealAgileDad/⁠

- [Linkedin] ⁠https://www.linkedin.com/in/leehenson/

The “Agile” Team That Was Actually Just Doing Waterfall in Sprints

Every two weeks, they ran a sprint review. The stakeholders attended. The demos were polished. The velocity charts trended in the right direction. And nothing significant ever changed based on what anyone said in that room.

That’s not agile. That’s theater with a two-week rhythm.

I’ve coached enough product teams to know that the mimicry of processes is one of the most expensive habits in software development. It looks like agility from the outside. It absorbs all the cost — the ceremonies, the tooling, the vocabulary; but delivers almost none of the benefit. Teams often know this, but feel powerless to speak up because the ceremonies themselves have become the “proof” of professionalism.

How to connect with AgileDad:

- [website] ⁠https://www.agiledad.com/⁠

- [instagram] ⁠https://www.instagram.com/agile_coach/⁠

- [facebook] ⁠https://www.facebook.com/RealAgileDad/⁠

- [Linkedin] ⁠https://www.linkedin.com/in/leehenson/

Why Estimating and Planning Still Matter - Mike Cohn

Over the years, I’ve talked with a lot of teams who’ve been burned by estimating and planning.
They’ve seen estimates treated as promises.
Plans turned into contracts.
Teams punished for being wrong rather than rewarded for learning.
Given experiences like those, it’s understandable that many teams conclude the solution is to eliminate estimating and planning altogether.
I think that’s a mistake.
Estimating and planning still matter—not because the future is predictable, but because it isn’t.
Teams and organizations still have to make decisions about what to work on, what to delay, and what risks they’re willing to accept.
Those decisions don’t disappear just because we stop estimating.
Any time we choose one piece of work over another, we’re estimating.
The real choice isn’t whether to estimate, but whether those estimates are explicit or implicit.
In my experience, explicit estimates create transparency. Implicit estimates just hide the guessing.
One of the biggest problems with estimating is the belief that estimates exist to be accurate.
A better question is whether an estimate is good enough to support the decision being made.
When teams make that shift, estimating becomes far less stressful—and far more useful.
The same is true of planning. Planning doesn’t reduce adaptability. Over-commitment does. Good planning aligns assumptions and intent so teams can adjust quickly when things change.
I often hear people say, “Estimates are always wrong.”
Being wrong isn’t the real problem. Estimates are hypotheses, and reality supplies the data.
The real failure is treating estimates as promises and punishing teams when reality turns out to be more complex than expected.
Before estimating or planning, I encourage teams to pause and ask three questions:

• What decision does this support?
• What happens if we’re wrong?
• Who will use this information—and how?

If those questions don’t have clear answers, the problem usually isn’t how the team is estimating.
It’s why.

How to connect with AgileDad:

- [website] ⁠https://www.agiledad.com/⁠

- [instagram] ⁠https://www.instagram.com/agile_coach/⁠

- [facebook] ⁠https://www.facebook.com/RealAgileDad/⁠

- [Linkedin] ⁠https://www.linkedin.com/in/leehenson/

The Sprint That Never Delivered

Three sprints in a row. Less than half of what the team committed — delivered.

As a Scrum Master, that’s the kind of pattern that keeps you up at night. Not because of the numbers themselves, but because of what comes next: the questions from management, the looks in the retrospective, the slow erosion of the team’s belief in themselves.

This was Team A. And they were trying. That much was clear.

How to connect with AgileDad:

- [website] ⁠https://www.agiledad.com/⁠

- [instagram] ⁠https://www.instagram.com/agile_coach/⁠

- [facebook] ⁠https://www.facebook.com/RealAgileDad/⁠

- [Linkedin] ⁠https://www.linkedin.com/in/leehenson/

Sprint After Sprint After Sprint… When Did This Stop Feeling Like Progress?

Here’s a question I want you to sit with for a moment. When you picture a high-performing Agile team — what do you see?

Fast delivery?

Clean boards?

Strong velocity?

Stakeholders who are happy and aligned?

Now let me ask you a harder question. In that picture — how does the team feel?

Because I’ve been in organizations that had all the first things. And absolutely none of the second.
And I will tell you from experience: that is not high performance.
That is a machine consuming the people inside it.
And machines don’t have retrospectives when they break down.

They just — stop.

How to connect with AgileDad:

- [website] ⁠https://www.agiledad.com/⁠

- [instagram] ⁠https://www.instagram.com/agile_coach/⁠

- [facebook] ⁠https://www.facebook.com/RealAgileDad/⁠

- [Linkedin] ⁠https://www.linkedin.com/in/leehenson/

7 Mindsets of High Performers That Will Change How You Work

After years of working closely with teams, leaders, and organizations, one pattern becomes impossible to ignore. High performers aren’t just more talented, luckier, or even working harder than everyone else.

They think, approach growth, and respond to pressure differently. And over time, those differences compound into extraordinary results.

Mindset is the invisible architecture behind every decision, habit, and result. It shapes how people approach challenges, learn from mistakes, and keep moving forward when things get difficult.

How to connect with AgileDad:

- [website] ⁠https://www.agiledad.com/⁠

- [instagram] ⁠https://www.instagram.com/agile_coach/⁠

- [facebook] ⁠https://www.facebook.com/RealAgileDad/⁠

- [Linkedin] ⁠https://www.linkedin.com/in/leehenson/

The Unglamorous Truth About Building Trust

I spent my first few months as a Scrum Master chasing the wrong thing. I thought trust was something you earned with one big moment. Deliver a miracle sprint. Shield the team from an impossible deadline. Stand up to that one difficult stakeholder in a meeting. I was waiting for my chance to be heroic.

How to connect with AgileDad:

- [website] ⁠https://www.agiledad.com/⁠

- [instagram] ⁠https://www.instagram.com/agile_coach/⁠

- [facebook] ⁠https://www.facebook.com/RealAgileDad/⁠

- [Linkedin] ⁠https://www.linkedin.com/in/leehenson/

Not Every Backlog Item Needs Detail - Mike Cohn

Here’s something I’ve noticed over the years:
Many teams think backlog refinement means making the entire product backlog detailed and “ready.”
That’s not how a healthy backlog works.
A well-managed product backlog should have a gradient of clarity.
Items near the top of the backlog—the ones you’re likely to work on soon—should be clear and reasonably detailed. They should have acceptance criteria, clarified assumptions, and enough shared understanding that the team can confidently bring them into a sprint.
But items further down the backlog should be less detailed.
They might be nothing more than a sentence or two.
It’s not wrong to leave lower backlog items vague. It’s the right and agile thing to do.
For example, imagine you’re building a travel booking website. Early on, you might have detailed backlog items about booking airfare and booking hotels. Those are core features, so they deserve detail.
But you might also have an item about booking cabins on a cruise ship. If cruises aren’t central to your product, that item can stay vague for a long time. It doesn’t need to be “Sprint Planning ready” six months before anyone will work on it.
If you fully refine backlog items far in advance, you’re doing a lot of work on items that will change, move, or disappear.
So rather than trying to keep the whole backlog “ready,” focus your refinement effort where it matters most:
At the top.
Refinement should make sprint planning easier.
That happens when the next sprint or two is well understood—not when the product backlog is documented 50 items deep.

How to connect with AgileDad:

- [website] ⁠https://www.agiledad.com/⁠

- [instagram] ⁠https://www.instagram.com/agile_coach/⁠

- [facebook] ⁠https://www.facebook.com/RealAgileDad/⁠

- [Linkedin] ⁠https://www.linkedin.com/in/leehenson/