#scrum #backlogrefinement #StoryPoints

#SilentRefinement 6/8

If a non-native speaker struggles with the spoken word, have we made things better by asking for written comment? As a native English speaker I might shock you when I say I struggle with writing clearly.

Have you tried this and did it work? What pros and cons have I missed?

#EffectiveMeetings #BacklogRefinement

#SilentRefinement 5/8

My questions remain around clarifying User Stories - according to Ron Jeffries - were supposed to honour the 3C's Card, Conversation and Confirmation. https://ronjeffries.com/xprog/articles/expcardconversationconfirmation/ - "The conversation is largely verbal, but can be supplemented with documents."

#EffectiveMeetings #BacklogRefinement

#SilentRefinement 4/8
…The author discourages this, saying prefer reading/writing over talking.

For any silent meeting to work you need a tool that allows you to see other people’s comments/edits in realtime. Hint not JIRA. Mural, Miro, Google docs etc are designed for this.

## My Response
Silent Meetings have been used for estimation for years (ex Bucket, Affinity est) and in some cases for prioritization. I would totally agree its good in this context.

#EffectiveMeetings #BacklogRefinement

For Backlog Refinement the author proposes taking the Product Backlog and making it the Table Read. Each Story would have a: Title, Story Description, Additional Info and Acceptance Criteria.

## Refinement Process
Arto proposes using silent refinement for the whole refinement process.

You need a tool that allows people to see each others comments and questions. If the comment/question is too difficult to write people revert to spoken word.

#EffectiveMeetings #BacklogRefinement

3/8

We (re)write the User Story in response to this conversation. Does silence work as well?

Arto is adapting the Silent Meeting. From Amazon see: https://medium.com/swlh/the-silent-meeting-manifesto-v1-189e9e3487eb

## Table Read
In the Amazon version of the process, there is 4-6 page narrative document, shared meeting start. It outlines the idea that is to be discussed. It is assumed that participants don’t have time to read before a meeting starts, so they start by reading the document.

#EffectiveMeetings #BacklogRefinement

2/8

# Silent Backlog Refinement Meetings - A Dream or Nightmare?
Reading Trumps listening, it engages quiet people and non-native speakers. Reading avoids domination by people who speak easily.

Rereading: Arto Kiiskinen's article https://www.eficode.com/blog/silent-backlog-refinement-meetings-a-more-effective-agile-meeting - I'm troubled. In traditional Product Backlog Refinement, I've found the back and forth discussion around what a customer needs to be the key value.

#EffectiveMeetings #BacklogRefinement

Thread 1/8

Basic and Good Reminder - Why isn't #BacklogRefinement not just part of sprint planning? and Why isn't refinement something the product owner does on their own? from Joel Bancroft-Connors again https://resources.scrumalliance.org/Article/product-backlog-refinement

#EffectiveMeetings I reviewed 168 sources on #ProductBacklogRefinement so you wouldn't need to. Needless to say most of them had no useful tips. In partnership with @bernie and @anil 

“Backlog refinement takes you from Vision to Value.”
Ellen Gottesdiener und Jeff Sutherland

Unser Artikel zum ist jetzt über ein Jahr alt, aber noch genauso aktuell:
#BacklogRefinement als Erfolgsfaktor für Scrum-Teams in hochkomplexen Umgebungen

https://entwickler.de/agile/backlog-refinement

#entwickler_de #HPT #Scrum

Im BASTA! Whitepaper 2022 sind zwei Artikel zu lesen, die Nils Hyoma, Shobhit Pradhan und Wuk Petrovic und ich gemeinsam geschrieben haben:

#UX und #Scrum – Scrum in Design Studio

und

#BacklogRefinement – Erfolgsfaktor für Scrum in einer hochkomplexen, fast chaotischen Umgebung

Zu finden und kostenfrei zu lesen unter
https://basta.net/basta-whitepaper-2023-1/

#Design #Read #CoCreation #Agile