I believe I can predict with complete accuracy who makes this decision in your organization.

Relative Estimation is possible in any unit, including time. And absolute estimation is also possible in any unit, including story points.

Agile software delivery is a team sport. The team succeeds or fails together.

We face many causes or types of uncertainty when creating software. Here are a few.

I've heard both "Agile is only good for developers" and "Agile is only good for management". I think they're two modes of the same failure.

I recommend this book by Matt Parker to anyone in leadership. You may not be able to implement everything, but without a doubt you can implement something to make your business more effective, and your employees more engaged.

4 surprising ways that small batches affect us psychologically

This may seem like a perfectly reasonable question on its face. But is it? I see two problems here.

How does your team do on these 4 key metrics identified as indicators of a highly-performing software team?

I think there are two "real worlds", and they often clash. One where Agile, Scrum, XP, and DevOps make perfect sense. Another where they don't.

5 ways smaller releases, pull requests, user stories, and commits can improve your code