After working with Scrum for over 3 years I am finally a Certified Scrum Master. This title sounds a lot more important and heavy than it actually is, it basically means I sat through a 2 day course on basic Scrum stuff. It sure doesn’t mean everyone who participated is now “certified” to lead a Scrum team successfully IMHO.

Since I am working with Scrum already for 3 years I was familiar with most topics and fortunately it seems we are not doing bad at all. To make the training a bit more valuable for me I would try to get some 1-on-1 time with Mike around the breaks, and ask him about Scrum Alliance related issues and ask his opinion on real life situations related to eBuddy.

When talking about the Scrum Alliance, I asked him if they were going to do something about the certification program. With all due respect, I would not trust our teams to many of the newly added Certified Scrum Masters. He agreed the name was badly chosen back in the day, but that it was legacy now, and they would announce a new name within a few weeks. He did share they were going to change the name of Certified Scrum Practitioner to Certified Scrum Professional. Obviously we ended up talking about Ken leaving the Scrum Alliance and Mike rejoining the Scrum Alliance. It seems Ken wanted to start a new certification program called Certified Scrum Developer (a 5 day course focussing on Scrum and Development practices like TDD, etc.) which could be taught by Ken himself only. Apparently this lead to Ken leaving the Scrum Alliance. I asked him what would happen in Ken with and the Scrum Alliance would go their separate ways and he said that that would not make sense and that they were working very hard to keep everyone on board. Mike has had long heated phone calls with Ken in the past weeks but he thought they reached a break through. It seems Microsoft who was very much in favour of the Certified Scrum Developer program, will be working with Ken on this program and they confirmed to Mike that Ken was on board and this could all still be held under the umbrella of the Scrum Alliance. But like I mentioned before this will probably be announced in a few weeks.

I also brought up a few eBuddy specific practical situations, like how best to organize our teams when scaling up, going from 3 to 5 teams, and how to track value added  to a product, with an open ended scope opposed to a more or less closed scoped project.

Here are a few new and old ideas I will bring up in a session with the teams to see if they make sense in our case:

  • Plan releases more ahead and use the 90% confidence interval
  • Track progress with (alternative) release burndown
  • Evaluate how well we execute on our plan
  • Use these statistics in retrospectives to make things more transparent
  • Setup communities of Practice (E.g. QA, SM, TDD, etc.)