This is an interesting way to frame it. I generally talk with people about making sure you got vision and horizon in your product backlog (which then requires adequate grooming). Still this sounds like a simpler to grasp wording here. Probably good for a first approach.

Lots of truth in there. Indeed the proposed "practices" when they get in just kill the promises of things like Scrum.

This is unfortunately very much true. Was only a matter of time I guess. The "grass is greener" effect is indeed the most likely reason.

Hear hear! It's not supposed to be easy, you need to hone your practices.

An advice I often give, it's nice to see the theory behind it well laid out like that.

Very interesting musing about the technical terms we often use wrongly and how it difficult it is to be understood.

Interesting take as usual. Utilization doesn't matter, throughput is what you need to keep in mind.

Good ideas to improve your user stories. I often see not so complete stories, it doesn't stop at the title, there's more to do. The proposed canvas is interesting and definitely helps.

As always, what really matters in the end is the context

Old video. A bit preachy, especially in the beginning, but then covers well the arguments of why counting stories is likely better than estimating them. In my opinion there's a catch that is not covered here though: the quality and granularity of the stories matter.

I definitely agree with this. Managing complexity is our trade.

Very good reminder that as an industry we're quick to blame external factors for our own failures. Of course we can be given a bad hand, but sometimes we'd have failed with a good hand as well.

Excellent article in French from one of the most influential people of the agile community in France. He delivers an interesting story about how state agencies started to apply some of the agile values and principles but how unfortunately this wave is already receding.

This asks very valid questions. I'm a bit less optimistic than in the conclusion though... I suspect that if it truly falls, it will be replaced by another cargo cult.

Interesting musing on the skills required, why it's actually hard to apply them... clearly it's because you never find a real place to learn them so that ends up being on the job.

Or why I'm actually glad I'm not certified even though I could be. This is a good way to stay balanced about all this. At least I'm trying to do my part trying to help people also on the technical areas which are mostly ignored by the "Scrum Industrial Complex" (as Ron Jeffries puts it). Clearly the scrum organizations are not interested in taking up that mantle so it falls onto us.

With the amount of time I spent with this particular beast I have to agree. It can be used well of course, but it's designed in a way that makes it very hard to use properly at all.

Interesting musing on how different types of companies manage their projects. I'm glad to see there's less cargo-cult Scrum than I expected. I also find funny that Scrum is perceived as "heavy weight". :-D

I have to agree there. So long and thanks for the fish I guess.

Nice extracts with comments about finding joy in your (work) life or not. Two paths really... which one are you on?

Too bad this is stretching a bit too far on the politics side (although it's not unjustified, I think it muddies the initial message in this context).