Differences

This shows you the differences between two versions of the page.

--- collaboration_at_scale_-_keeping_retrospectives_fresh_by_ben_linders [2017/03/09 10:22] – created hpsamios
+++ collaboration_at_scale_-_keeping_retrospectives_fresh_by_ben_linders [2018/05/31 10:19] – hpsamios
@@ Line 1: / Line 1: @@
+====== Collaboration At Scale: Keeping Retrospectives Fresh ======
 ====== Premise ======
 Scrum Alliance pitch
-“Meeting Description
+“Retrospectives are great … except when they’re not. Without care and attention, retrospectives become stale, boring, and ineffective. And this is especially likely with distributed teams, where it is easy to put yourself on mute and start answering email instead of focusing on your team.
-Retrospectives are great … except when they’re not. Without care and attention, retrospectives become stale, boring, and ineffective. And this is especially likely with distributed teams, where it is easy to put yourself on mute and start answering email instead of focusing on your team.
 In this Collaboration at Scale webinar, we’ll explore how you can keep retrospectives fresh, engaging, and impactful. We’ll focus especially on helping distributed teams identify the frameworks that allow them to explore different ways they can improve performance."
@@ Line 16: / Line 12: @@
 Scrum centric with more than 10 teams. Interactive webinar.
-Presenters
+====== Presenters ======
 Ben Linders (consulting coach)
@@ Line 25: / Line 21: @@
 Conteneo is co-presenter.
-Actions
+====== Materials ======
-Start reviewing the scrum at scale through scrum Alliance
+My version: {{ :wiki:cas_webinar_03082017.pdf |}}
-Idea: role of external coach as external facilitator to help teams and share / spread knowledge
-Idea: create list of exercise for retrospectives (and make sure people that people know this). See Ben Linder’s site benlinders.com/exercises and /posts-retrospectives
+====== Actions ======
-retrospectivewiki.org/index.php
-Idea: pilot retrospective (large team)
+  * Idea: role of external coach as external facilitator to help teams and share / spread knowledge
-Notes
+  * Idea: create list of exercise for retrospectives (and make sure people that people know this). See Ben
+  * Linder’s site benlinders.com/exercises and /posts-retrospectives
+  * retrospectivewiki.org/index.php
+  * Idea: pilot retrospective (large team)
+====== Notes ======
 From the poll questions:
-Summary we do it a lot, but not always effective
-Warning signs of ineffective?
+Summary we do it a lot, but not always effective. Therefore need to understand:
-Why do it?
+  * Why do it?
-Want to find ways to improve
+  * Want to find ways to improve
-Do it for the right reasons
+  * Do it for the right reasons
 Warning signs:
-Doing things is not the same as getting things done – are things getting done?
+  * Doing things is not the same as getting things done – are things getting done?
-Lack of ownership (great conversation but no clear ownership about what we are going do about it)
+  * Lack of ownership (great conversation but no clear ownership about what we are going do about it)
-Repeated root cause (rehashing the same problem)
+  * Repeated root cause (rehashing the same problem)
-People not attending
+  * People not attending
 Coaching questions to drive conversation about improving retrospectives:
-Are you doing them?
+  * Are you doing them?
-Do you like doing them?
+  * Do you like doing them?
-Are you seeing the benefits?
+  * Are you seeing the benefits?
 Why are retrospectives less than effective?
-Overuse of the same facilitator (too much of the same perspective, same biases (especially wrt to how people work together) (one recommendation have external facilitate new teams else otherwise the internal facilitator is trying to do too much.)
+  * Overuse of the same facilitator (too much of the same perspective, same biases (especially wrt to how people work together) (one recommendation have external facilitate new teams else otherwise the internal facilitator is trying to do too much.)
-Overuse of the same goal – try to set different goals for different times. Not just “improve” but what are you trying to improve at the moment.
+  * Overuse of the same goal – try to set different goals for different times. Not just “improve” but what are you trying to improve at the moment.
-Overuse of the same framework / technique (e.g. What went well, what can be improved, actions)
+  * Overuse of the same framework / technique (e.g. What went well, what can be improved, actions)
 Who should attend
-Anyone who has involvement
+  * Anyone who has involvement
-Also has benefit that in that it helps for social bonds
+  * Also has benefit that in that it helps for social bonds
-Up to facilitator to ensure safe environment
+  * Up to facilitator to ensure safe environment
-How do we keep retrospectives fresh
+How do we keep retrospectives fresh?
 The key is variation
-Vary the goal
+  * Vary the goal
-Find new technologies – what do we need to get to get in the future
+    * Find new technologies – what do we need to get to get in the future
-Celebrate success – we’ve done really well – what did we learn from this
+    * Celebrate success – we’ve done really well – what did we learn from this
-Share best practices
+    * Share best practices
-Mix up timing – don’t always have to do at end
+    * Mix up timing – don’t always have to do at end
-Varying goal also could mean bringing in other stakeholders
+    * Varying goal also could mean bringing in other stakeholders
-Goal will you set the cadence – err on the side of more frequent than less – idea is to focus on feedback
+    * Goal will you set the cadence – err on the side of more frequent than less – idea is to focus on feedback
-Vary the framework (note: called framework rather than exercise)
+  * Vary the framework (note: called framework rather than exercise)
-Speed boat (nice metaphor). Add in rocks to represent risks, not just winds and anchors
+    * Speed boat (nice metaphor). Add in rocks to represent risks, not just winds and anchors
-Going well (why is it going well)
+    * Going well (why is it going well)
-box – happy, sad, ideas, kudos
+    * 4 box – happy, sad, ideas, kudos
-Remember the future the retrospective (aka futurespective)
+    * Remember the future the retrospective (aka futurespective)
-Start your day
+    * Start your day
-Backpacking – new teams. You are on a journey. What do you take with you? What do you want to leave behind (things that we don’t want to do going forward). Can only take 5 things (as hand baggage along metaphor) to help focus.
+    * Backpacking – new teams. You are on a journey. What do you take with you? What do you want to leave behind (things that we don’t want to do going forward). Can only take 5 things (as hand baggage along metaphor) to help focus.
-Make small tweaks to the base framework
+    * Make small tweaks to the base framework
-Vary the environment
+  * Vary the environment
-Over lunch / coffee
+    * Over lunch / coffee
-Offsite happy hour
+    * Offsite happy hour
-Outdoors
+    * Outdoors
-Where people feel comfortable
+    * Where people feel comfortable
-Bring in lunch
+    * Bring in lunch
-Length of time (e.g. Running retrospective)
+    * Length of time (e.g. Running retrospective)
-Vary the facilitator
+  * Vary the facilitator
-A professional
+    * A professional
-A close friend
+    * A close friend
-A scrum master from another team
+    * A scrum master from another team
-Rotate roles with the team (especially if the goal relates to a specific area of interest for a team member)
+    * Rotate roles with the team (especially if the goal relates to a specific area of interest for a team member) As much as possible should be independant (not involved in the topics) of the approach. Don’t facilitate if you have a big stake in the outcome
-As much as possible should be independant (not involved in the topics) of the approach. Don’t facilitate if you have a big stake in the outcome
+  * Vary the amount of negativity (problems vs learning vs successes)
-Vary the amount of negativity (problems vs learning vs successes)
+    * What did we learn (not what went wrong) is primary focus
-What did we learn (not what went wrong) is primary focus
+    * Some times need to vent (express pain)
-Some times need to vent (express pain)
 Three key tips for distributed teams
+  * Vary The Who feels the pain
+  * Give the introverts a chance (e.g. Running retrospective)
+  * Use online tools (e.g. Weave, Retrium, Boardthing) as a way to level the playing field, and better than a conference call
+  * Leverage video conferencing (e.g. Google hangouts is free for up to 10 people)
-Vary The Who feels the pain
-Give the introverts a chance (e.g. Running retrospective)
-Use online tools (e.g. Weave, Retrium, Boardthing) as a way to level the playing field, and better than a conference call
-Leverage video conferencing (e.g. Google hangouts is free for up to 10 people)
 Just because you have distributed people it does not mean you cannot do an exercise
 Use the same thinking for distributed teams as well and adapt to being distributed
 Vary exercise, environment, goal
-How to deal with problems that team cannot deal with alone
+How to deal with problems that team cannot deal with alone?
 Create large / multi team retro
 Note this can be another reason that retros become stale
@@ Line 120: / Line 124: @@
 Make results of actions visible
-How do you deal with dependent teams? Make that the goal of the retrospective and pull in people to participate
+How do you deal with dependent teams?
+Make that the goal of the retrospective and pull in people to participate
-How do you deal with technical retrospective issues? Perhaps make it a hack-a-thon to be the retrospective
-A couple of poll questions
-How often?
-How effective?
-Next Webinar?
+How do you deal with technical retrospective issues?
+Perhaps make it a hack-a-thon to be the retrospective
 {{tag>Webinar Ceremony ScrumMaster Video Learning Retrospective}}
-~~LINKBACK~~
-~~DISCUSSION~~