Tag: Meetings

Posted on

Overcoming Four Common Objections to the Daily Scrum

Some meetings are helpful and worth the time investment. Mike Cohn puts well-run daily scrum meetings in that category.

In this article, Mike Cohn shares how he handles four common objections to participating in daily scrums.

  1. We Talk A Lot Already
  2. Nothing Important Is Ever Discussed
    1. Set Expectations
    2. Determine if the Objection Is Valid
  3. Can’t We Just Do This by Email?
  4. The Meetings Take Too Long

He then shares some attributes of a well-run daily scrum so that there will be no objections to participating.

  1. Meetings Are at the Same Time and Place Each Day
  2. Meetings Start on Time
  3. The Meetings Are Kept to No More than Fifteen Minutes
  4. Problems Are Identified But Not Solved in the Meeting
  5. Participants Stay on Topic
  6. Rules Are Enforced by the Whole Team, Not Just the Scrum Master
  7. The Whole Team and Only the Team Participates

Read the complete article here: https://www.mountaingoatsoftware.com/blog/overcoming-four-common-objections-to-the-daily-scrum

Posted on

Deze 10 principes helpen je meer uit je interacties te halen

Of je nu de grote baas bent bij een multinational of net bent begonnen met je eerste serieuze baan, voor iedereen geldt: jouw succes in het leven is grotendeels afhankelijk van de interacties met de mensen om je heen. Hoe meer je uit die interacties haalt, hoe meer jij uit het leven haalt. Lijkt dat je wat? Dan vind je in de tien principes achter Liberating Structures een bijzonder effectieve methode om dat voor elkaar te krijgen.

  1. Betrek en activeer iedereen
  2. Respecteer anderen en wat anderen te zeggen hebben
  3. Bouw vertrouwen op terwijl je bezig bent
  4. Leer van je fouten
  5. Gebruik de groepsdynamiek om jezelf beter te leren kennen
  6. Benadruk vrijheid en verantwoordelijkheid
  7. Focus je op wat wél mogelijk is
  8. Omarm creatieve destructie
  9. Serieus spelen: Spelenderwijs ontdekken
  10. Start nooit zonder duidelijk doel

Lees het volledige artikel van Ruben Klerkx hier: https://thecreatorscompany.com/blogs/deze-10-principes-helpen-je-meer-uit-je-interacties-te-halen/

Posted on

IDOARRT Meeting Design

IDOARRT is a simple tool to support you to lead an effective meeting or group process by setting out clear purpose, structure and goals at the very beginning. It aims to enable all participants to understand every aspect of the meeting or process, which creates the security of a common ground to start from. The acronym stands for Intention, Desired Outcome, Agenda, Rules, Roles and Responsibilities and Time.

Step 1:

Before the meeting/process, prepare a Flipchart / Slide outlining all the points of IDOARRT. See below:

Intention – What is the intention, or purpose, of the meeting? In other words, why have it?

Desired Outcome(s) – What specific outcomes should be achieved by the end of the meeting?

Agenda – What activities will the group go through, in what order, to move toward the desired outcome?

Roles – What roles or responsibilities need to be in place for the meeting to run smoothly? Who is facilitating, and who is participating? Who is documenting, and who is keeping track of the time? What do you expect of the participants?

Rules – What guidelines will be in place during the meeting? These could relate to agreed group norms. They could also relate to use of laptops/mobiles, or practical rules related to a space. Let the participants add rules to ensure that they have ownership of them.

Time – What is the expected time for the meeting, including breaks,and at what time will the meeting end?

Step 2:

At the beginning of the meeting, introduce the IDOARRT, going through point by point. Invite participants to ask questions or make suggestions for changes. Once the group is happy with the plan, go ahead with the rest of the meeting.

Posted on

Nine Questions Scrum Masters and Product Owners Should Be Asking

In the following article Mike Cohn shares his favorite questions to ask: https://www.mountaingoatsoftware.com/blog/nine-questions-scrum-masters-and-product-owners-should-be-asking

Two Questions about Estimates

  • I’m not looking for an estimate. But if I asked for an estimate, what unit pops into your minds: Hours, days, weeks, months, or years?
  • How confident are you in that estimate?

Three Questions About Team Decisions

  • What are three other options you considered before making this decisions?
  • What’s the worst thing that could happen if we pursue this direction?
  • What has to go right for this to be the best decision?

Two Questions about Meetings

  • Do we need everyone who is here now?
  • Should anyone else be here?

One Question to Ask When Wandering Around

  • Does anyone else need to know about this?

One Question to Ask During Daily Standups

  • What do you know that I don’t know?