Check out this new card deck I created!
Go get a deck or order a personalized batch for your company at scrumcards.org
I am in the Lyon airport, waiting for a rescheduled flight to Amsterdam. This gives me some time to share my thoughts on speaking at Mixit 2018.
I have been to Lyon together with Emile Silvis, since we were invited to host a workshop on System’s thinking, making Causal loop diagrams. In addition to that, I gave a lecture on Large Scale Scrum.
This article is directed to all who think that being a Scrum Master is inferior, and therefore think (ab)using the term “Agile Coach” is justified.
Note. A serious warning before you read on: If you consider yourself to be an Agile Coach and you are not up to digesting some painful transparency about your role, please stop here. Continue reading
On may 19 2018: Implementing Large Scale Scrum (real life stories).
I will be focusing on near-shoring and LeSS.
Most of the concepts in Scrum are easy to understand but extremely difficult to master. This is due to the fact that Scrum is designed for perfect, and reality never is. The same principle applies to the Definition of Done.When we start up teams, we help them to set a Definition of Done (DoD).
Teams are taught the DoD is an instrument that will provide them transparency in two ways:
- understanding what the effort of work is, considering all the tasks that need to be undertaken by the team before work can be marked as “done”.
- understanding what “done” means when an item is inspected at the end of the sprint.
Micro-skills are simple intervention techniques. When using micro-skills, you will facilitate sessions and have conversations that yield more effect and value. Using the micro-skills offers support in your facilitator or leadership role.
I have developed a workshop to train a set of 18 micro skills. In this workshop, you will learn to consciously facilitate a discussion or an interview using micro-skills.
I was going over the slides of the September LeSS conference and I was struck by the deck of Kevlin Henney. He was referring to an organizational structure that I never heard of. I have seen it before, I did not know it had a name and I was not aware that all existing classical org structures are actually wrong.
You are familiar with the classical tree:
LeSS adoption prescribes one person in the role of Product Owner (PO). Not multiple people, not a committee, just one person. Companies have a hard time in accepting the idea that one person can do this complex task for the whole product. The product is too big and there are too many customers and stakeholders the PO needs to deal with. Companies refuse to redefine the PO role description and stick to having multiple Fake PO’s. Continue reading
Just gave a lecture in Riga. The feedback question was: show your feedback using your fingers. Put up 1 finger if my session was wasteful and 5 fingers if it was very valuable.