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/