Category: certification

Every time these organizations stamp out a new ScrumMaster, there are programmers somewhere whose lives will be made worse.

A bit of a screed about naming, triggered by a super idea from Dan Terhorst-North.

... to ScrumAlliance.org, Scrum.org, and the Scrum Community at large

Scrum is founded in the belief that self-organizing teams can figure out what they need. When true, this is sometimes not sufficient. And sometimes, particularly in software development, it seems not to be true.

Let's talk about what responsibility we have for those who never take a course from us, read our books or web sites, or even see our tweets. I think we have rather a lot.

Bashing of Scrum (and other methods) is a common form of Internet Entertainment, and not without reason. Some of the concerns are more accurate than others. Choose carefully which hill you want to die on. In this series we'll explore some hills.

You'll meet them where they are. You'll work with them where they are. And when you leave, they'll still BE where they are.

Thoughts on the state of Scrum and Agile. Pressing harder isn't the point at all. Bit of a rant, really.

That's all you need. You don't need no more.

Theory, Practice, Received Wisdom, Certification. These are not the things that make things work. Good people make things work.

I had occasion to look at a couple of articles from 2010, and things don't seem to have changed much. Should we be concerned?

It is my practice to reconsider important topics. Certification certainly is such a topic. Here are today's thoughts.

Chet and I will be meeting with both the new and the outgoing Managing Director of the Scrum Alliance. I asked for input on Twitter, and have received some. Here, some thoughts.

The Scrum Alliance is instituting a Certified Scrum Developer program (finally). Chet and I are involved. Here's why and how ...