kaczor.info

I got it totday in email from my manager. I don't know the original source

"Three Scrums for the Sr Management in the sky,
Seven for the Product Managers in their cubicals of cloth,
Nine for Developers doomed to open office,
One for the Dark Scrum Master on his dark throne
In the Land of Agile where the Stories lie.
One Scrum to rule them all, One Scrum to find them,
One Scrum to bring them all and in the backlog bind them."

Sometime this year and I guess it was July 2011 looking at the version available online Scrum Guide on scrum.org was changed. If the Scrum Guide is change, the framework is also changed. The list of changes is following:

Today's post is going to be from both technical and soft skills areas of the skills that effective Scrum Master needs to have. Using Scrum involves close cooperation between so called Business and IT. and you need things from the business. It can be more resources, requirements, good User Stories, Product Backlog to be ready for next iterations or just simple yes/no answers. On some projects you will meet Product Owner that doesn't want to cooperate, doesn't know about Scrum and Agile or just doesn't want to take any responsibility.

This is continuation of the New Scrum Team - New Agile Coaching Approach Part post.

This week I started to work on a new project as ScrumMaster and Agile Coach for the new Scrum Team. All the team members are not familiar with Scrum.

One team member is working on more than one task at the same time. If these two tasks need to be worked on in parallel, why were they separated and estimated separately?

Here are three videos published on YouTube. Ken Schwaber is presenting about "flaccid Scrum" and succeeding with Scrum on a conference in Montréal. The conference was organized by Pyxis Technologies (http://pyxis-tech.com).

"Scrum In Depth" program was renamed to "Professional Scrum Master". You can read it as war with Scrum Alliance, which provides Certified Scrum Master certificates. In my opinion. The word Professional and slogan "A Credible Standard" are used here to differencaite level of knowledge and strict rules of passing exam comparing to nearly no assesment in case of Certified Scrum Master certification. Rules of Scrum.org are quite tough and will be tougher from August 15:

I am glad I found it now. It goes well with previous post as a follow-up. This time Elisabeth Hendrickson tells us more in detail about her experiences and lessons learned from Agile testing on XP projects. You can avoid mistakes and learn some of the best practices by watching it. Someone said that the best wasy to learn is to learn on mistakes and preferably somebody-else's mistakes.

It's not possible not to notice transformation of speaker since 2005. Nice job Elisabeth!

Abstract that goes with it: