Decades that our industry doesn't improve its track record. But there are real consequences for users. Some more ethics would be welcome in our profession.

Interesting approach I didn't know about. Definitely worth trying. I like how it seems to bake risk management in.

I'm a bit on the fence regarding this article. That being said there's something I like about it: it's not always purely about money. It's also a good reminder that if the reward is in monetary form it's almost impossible to not somehow alter team dynamics with it.

I wouldn't frame it as always superior (I'd argue the article falls a bit in this trap). Still this can sometimes be an alternative to driving everything purely on project mode. Some organizations would benefit from such a change of perspective other less so.

There are indeed way to deal with important but lower priority tasks. You want to tackle those to avoid your teams to slow down too dramatically.

Indeed, stress can't be completely eliminated... but at least build an environment where risky situations are reduced as much as possible. So that when stress or anxiety shows up you can take notice and react. Otherwise you'll be creating vicious circles.

Indeed many projects are started without such a charter and that creates issues.

This is indeed one of the core questions on you "agile" project management. If the feedback loops are very long, you're in for trouble.

There's often confusion as to where the management responsibilities are in agile teams. This little rambling does a good job pointing it out and giving an idea of how management happens inside and around teams.

A good reminder that there's a lot of things going on in something as mundane as a stand up meeting. It needs to be organized properly for the needs of the teams.

Don't just blindly apply dailies. Make sure they really solve a problem in your team.

You have to be willing to experiment and adjust in order to truly be agile. Otherwise you indeed just do dailies and call yourself agile.

Nice check list, there's more to project life than churning out tickets.

Hear, hear! If you go through rituals without understanding the values and principles... It's not Agile anymore so stop pretending. Another certification isn't going to save you at this point.

If your team is solely in "pushing tickets out" mode, there's indeed a problem. Teams needs more agency and care for the output to actually strive long term.

A bit of a forgotten approach I think. A good way to quickly gauge projects, show the amount of work and spot the dependencies.

Definitely this, as projects scale, keeping an eye on dependencies between teams is key to efficient allocation. This will happen by trying to eliminate said dependencies, reallocating between teams.

Interesting findings about procrastination. Some effects were expected, others less so. The actions to avoid it in teams should be well known now.

Definitely this, too often I see projects treating the technical debt as one-off large tasks. Really it's something you should deal with bite sized and over time.

Don't throw estimates out of the window. Keep in mind that the more precise they are the more expensive they become.