kaczor.info

Finally it has come together. I organized Rapid Software Testing class with James Bach. In total from the moment we have started talking about it it took about two years. First the idea was to organize the training in Poland, but finally the training was organized in the Netherlands.

Frank: I am waiting for answer from Coen.
Krystian: Have you asked the question?
Frank: Yes, But he wasn't here.
Krystian: Ok, again. Have you asked the question? :)

You can explain Scrum framework in under 10 minutes. Good example is the movie below.

How long does it take to master Scrum? Years.

My training in Coaching and path to certification takes so much time, that I can bearly find so time for reflection. So this time they are quotes from few months.

Here they are:

• "It's already DONE. It needs to be only implemented."
• "Nothing can be done in 3 hours."
• "Estimation process in planning 'Bargaining' like the Thai cloths market"
• "Blocking task waiting.. waiting.. waiting."

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.