Scrum Gathering London 2018: What's Really Going On? An Observational Skills Workshop
•
1 like•75 views
Slides from our workshop at the Global Scrum Gathering London 2018 - "What's Really Going On? An Observational Skills Workshop"
Report
Share
Report
Share
Recommended
Agile + DevOps East 2018: Observation Workshop
This document describes an observational skills workshop where participants practice observing and providing factual observations without interpretations. The workshop is split into rounds where groups take turns building a structure or having a discussion while being observed. Observers focus on one area like body language, tone of voice, or decision making and take factual notes without judgments. After each round, observers share their notes and participants discuss their experiences observing and being observed. The goal is to help participants learn to provide useful observations and feedback by focusing only on facts rather than interpretations.
Facebook retrospective
This document describes a retrospective method called the "Facebook retrospective" designed by the author. It involves printing topics related to the Scrum process on cards and having team members vote on whether they "like" or "dislike" each topic. The results are analyzed to identify topics the team agrees or disagrees on, and actions are generated for topics of disagreement. The retrospective is timeboxed to one hour and includes an energizer, voting activity, discussion of results, and generating actions for the next sprint. Feedback from trying this method is to allow a neutral option for voting and to allow custom topic cards.
Improving understanding
This document discusses the importance of understanding each other and avoiding assumptions. It includes exercises where participants observe images and write down their inferences to illustrate how mental models can shape perspectives. The debrief discussions emphasize co-creating shared visions and making assumptions explicit to prevent beliefs from hindering understanding. The goal is to improve comprehension between individuals by recognizing unconscious biases and discussing differing viewpoints in a constructive manner.
Agile 2020 Ball Point Game
In this revised version of Boris Glogger’s Ball Point Game, you and your teammates will be given a simple task that is challenging to execute. Working together, you’ll learn to self-organize to improve your workflow as you continuously find improvements to complete your task more effectively.
Ben landau - Block 1 presentation
This document provides guidance on conceptualizing and articulating a research project. It recommends developing methods for critical thinking and decision making by questioning the needs of the site, audience experience, and goals for the project. It also suggests mapping out the project conceptually to clarify the abstract narrative and research approach. Finally, it emphasizes the importance of "mateship," or collaboration with a "buddy" who can provide critical feedback and support throughout the process.
Scrum Gathering 2014 - Enabling Distributed Agile Teams
In this scrum gathering talk I introduced some common issues in distributed teams. I used an exercise to generate working agreements for distributed teams call the negation exercise. Additionally, there are a few tool discussion slides and a great communication kata to help get your teams to a better state of flow.
The Art of the Retrospective: How to run an awesome retrospective meeting
The drive to inspect and adapt is one of the most important aspects of agile software development. A great way to bake this approach into your process is by having regular retrospective meetings that engage and challenge the team to solve their own problems and make things better. However, these meetings can be difficult to run well and drive improvement. In fact, many teams sleepwalk through sessions, treating them as a box-ticking exercise that signals the end of the iteration.
Maybe its time we tried a bit harder to make retrospective meetings work?
In this talk, Chris explains how to put together an awesome sprint retrospective. He discusses the following:
* Why retrospectives can be unpopular
* Structuring the meeting to succeed
* Setting the right tone
* Activities to gather data
* Activities to generate insights
* How to decide what to do
* How to manage retrospective actions
Definition of Your First Release Game
This is the slide deck for the game I created to help people (product owners in particular) experentially understand how a product vision, story map, and stories are used to develop the direction of a product. It was based off of Chris Chapman's #NoEstimates Puzzle Experiment Game. Thanks to him for sharing!
Recommended
Agile + DevOps East 2018: Observation Workshop
This document describes an observational skills workshop where participants practice observing and providing factual observations without interpretations. The workshop is split into rounds where groups take turns building a structure or having a discussion while being observed. Observers focus on one area like body language, tone of voice, or decision making and take factual notes without judgments. After each round, observers share their notes and participants discuss their experiences observing and being observed. The goal is to help participants learn to provide useful observations and feedback by focusing only on facts rather than interpretations.
Facebook retrospective
This document describes a retrospective method called the "Facebook retrospective" designed by the author. It involves printing topics related to the Scrum process on cards and having team members vote on whether they "like" or "dislike" each topic. The results are analyzed to identify topics the team agrees or disagrees on, and actions are generated for topics of disagreement. The retrospective is timeboxed to one hour and includes an energizer, voting activity, discussion of results, and generating actions for the next sprint. Feedback from trying this method is to allow a neutral option for voting and to allow custom topic cards.
Improving understanding
This document discusses the importance of understanding each other and avoiding assumptions. It includes exercises where participants observe images and write down their inferences to illustrate how mental models can shape perspectives. The debrief discussions emphasize co-creating shared visions and making assumptions explicit to prevent beliefs from hindering understanding. The goal is to improve comprehension between individuals by recognizing unconscious biases and discussing differing viewpoints in a constructive manner.
Agile 2020 Ball Point Game
In this revised version of Boris Glogger’s Ball Point Game, you and your teammates will be given a simple task that is challenging to execute. Working together, you’ll learn to self-organize to improve your workflow as you continuously find improvements to complete your task more effectively.
Ben landau - Block 1 presentation
This document provides guidance on conceptualizing and articulating a research project. It recommends developing methods for critical thinking and decision making by questioning the needs of the site, audience experience, and goals for the project. It also suggests mapping out the project conceptually to clarify the abstract narrative and research approach. Finally, it emphasizes the importance of "mateship," or collaboration with a "buddy" who can provide critical feedback and support throughout the process.
Scrum Gathering 2014 - Enabling Distributed Agile Teams
In this scrum gathering talk I introduced some common issues in distributed teams. I used an exercise to generate working agreements for distributed teams call the negation exercise. Additionally, there are a few tool discussion slides and a great communication kata to help get your teams to a better state of flow.
The Art of the Retrospective: How to run an awesome retrospective meeting
The drive to inspect and adapt is one of the most important aspects of agile software development. A great way to bake this approach into your process is by having regular retrospective meetings that engage and challenge the team to solve their own problems and make things better. However, these meetings can be difficult to run well and drive improvement. In fact, many teams sleepwalk through sessions, treating them as a box-ticking exercise that signals the end of the iteration.
Maybe its time we tried a bit harder to make retrospective meetings work?
In this talk, Chris explains how to put together an awesome sprint retrospective. He discusses the following:
* Why retrospectives can be unpopular
* Structuring the meeting to succeed
* Setting the right tone
* Activities to gather data
* Activities to generate insights
* How to decide what to do
* How to manage retrospective actions
Definition of Your First Release Game
This is the slide deck for the game I created to help people (product owners in particular) experentially understand how a product vision, story map, and stories are used to develop the direction of a product. It was based off of Chris Chapman's #NoEstimates Puzzle Experiment Game. Thanks to him for sharing!
The Slippery Slope
This document discusses how teams can unintentionally slip away from Agile practices over time if they are not careful. It provides examples of common "slippery slopes" such as skipping story estimation, not using relative sizing, carrying stories between sprints, and stopping daily standups. The author urges coaches to focus on helping teams form good habits in the first 3-6 months and celebrate successes while also constructively pointing out areas for improvement. Teams are reminded that Agile requires discipline and that changing habits is difficult, so they should avoid picking up bad practices.
Agile Engineering for Managers Workshop
The document discusses agile engineering practices and concepts. It begins by outlining objectives like understanding practices teams can use to handle complexity and the benefits they provide. The agenda then covers topics like what is meant by agile engineering, how practices relate to agile principles, iterative processes, user stories, and specific practices like source code control, pair programming, continuous integration, and testing. It emphasizes that these practices help produce quality code, allow for reliable and frequent deployments, and protect teams from issues.
Agile scrum-retrospective
What is Agile retrospective, and what is its importance. When and Why you should be doing it. The Do's and Dont's of Agile retrospective.
Retrospectives
This document discusses retrospectives, which are meetings where teams reflect on how to improve effectiveness. It explains that retrospectives are important for continuous improvement. Reasons to change retrospectives include getting stuck in routines, repeatedly facing the same issues, and lack of progress on problems. Different frameworks are presented for retrospectives, including Sailboat for identifying help/hindrances, Starfish for reviewing practices, and Three Little Pigs for evaluating processes and teamwork. Tips are provided such as using dot voting and rotating the facilitator role. Distributed tools for remote retrospectives are also listed.
Agile Retrospectives
The document discusses agile retrospectives and provides guidance on facilitating effective retrospectives. It outlines a 5-step format for retrospectives: 1) set the stage, 2) gather data, 3) generate insights, 4) decide what to do, and 5) close the retrospective. The facilitator's role is to make sure everyone contributes and a plan is created without solving problems for the team. The Scrum Master reflects the team's behavior back to help them improve. Team members should focus on the content, discuss openly, and make decisions. Retrospectives help teams continuously improve and change their definition of done, working agreements, and generate action items.
December 2009 Collaboration
This is a presentation I gave to pre-service teachers at Lake Forest College, December, 2009. The focus was on the "What, Why and How of Collaboration" in the classroom.
From Flab to Fab! Design Secrets for Overweight Interfaces
This document provides five design secrets for creating less overwhelming interfaces: 1) Use neutral base colors and strong accent colors with restraint and balance. 2) Create a strong anchor through placement, contrast, and indicating what users should focus on. 3) Vary box styles, create horizontal terraces, and reduce visual noise to "de-boxify". 4) Ensure consistent spacing, margins, and styles to "sweat the details". 5) Any combination of these secrets can be used to improve interface design outcomes.
How to go from structureless to structured without losing your vibe
The document discusses moving from a flat organizational structure to one with more hierarchy and leadership roles at a company. It notes that as engineering teams grow past a certain size, the flat structure breaks down, and it's time to consider roles like VP of Engineering or Director of Engineering. However, it emphasizes that these new leadership roles need clearly defined responsibilities and expectations to avoid confusion and ensure accountability. It advocates creating an engineering ladder or level system to establish clarity around hiring, pay, promotion criteria and growth opportunities for team members at different career stages.
Agile2019_Observational Skills Workshop
The document describes an observational skills workshop presented by Julie Wyman and Mark Grove. The workshop includes exercises to practice observation skills by having participants observe a team building a structure and noting observations without interpretation. The goal is to help participants learn to provide better coaching support to teams by improving their ability to objectively observe team behaviors and interactions.
MHA 2020 observational skills workshop
Imagine you are asked to sit in on a team’s sprint review and retrospective. The team has been having difficulty forming and the Scrum Master has asked you to observe the team dynamics during these two sessions. Are you simply going to watch what’s going on or is there more you can do?
Agile Leadership 201: Enriching Management for AgileNoVA
This document outlines an agenda for a presentation on agile leadership and servant leadership. The presentation defines servant leadership as serving others first before leading, discusses common frustrations managers face when adopting this model, and provides exercises for attendees to brainstorm ways to address these frustrations. The presentation also covers topics like observing work processes, demonstrating curiosity, problem-solving proactively, and effectively delegating responsibilities. The goal is to help managers shift from a traditional leadership role to one that enriches their teams through servant leadership approaches.
Agile Leadership 201: Enriching Management
This is the latest in my series of leadership workshop sessions; this presentation includes the exercises and learning points. To see some of the text properly, you will need to get the free font Dark Roast.
Agile Leadership 201 for TriAgile
Enriching management is a key way to build Agile Leadership. This presentation helps make this concept of enrichment a bit clearer and how in turn management can learn to enrich its workforce as well. This provides some concrete mechanisms to make servant leadership real, without necessarily calling it servant leadership (shich sometimes doesn't resonate with people).
Ball Point Game: Self-organizing Your Flow of Work
In this revised version of Boris Glogger’s Ball Point Game, you and your teammates will be given a simple task that is challenging to execute. Working together, you’ll learn to self-organize to improve your workflow as you continuously find improvements to complete your task more effectively.
A Take on Different Retrospectives
The document discusses retrospectives and provides guidance on when and how to conduct them. It begins with questions to ask before a retrospective to plan objectives and considerations. It then discusses why retrospectives are important for process improvement and examples of when to conduct various types, such as pre-retrospectives before major initiatives. Personal retrospectives are suggested as a way for individuals to reflect and improve. Finally, different retrospective techniques are presented, such as constellation mapping to gather team feedback. The overall document serves as a guide for successfully facilitating retrospectives.
Kanban in Action Workshop
This two-part interactive workshop begins with a detailed look at how to interpret Kanban boards and ask thoughtful questions so that you can improve the work of your teams. We will provide an overview of the Kanban Method and then proceed through a series of eight short exercises that will give you an opportunity to review and interpret various Kanban board configurations with other attendees at your table. After a short break, part two of the session now puts the attendees in the driver’s seat to create their own board configurations. We provide eight business scenario exercises and ask the attendees how they would go about configuring their Kanban board given the unique system constraints for each scenario.
Your Agile Leadership Journey: Leading People-Managing Paradoxes - Agile Char...
This is the workshop Nicole and I gave at Agile Charm 2020 on Leading people through paradoxes, some of which are described directly in the Manifesto for Agile Software Development. It helps you understand how to use Polarity Maps as leaders for a thinking tool to understand your system.
5+Dysfunctions+of+a+Team_Final_20200228.pptx
Talks about dysfunctions of a team as per theory and practice
There are 9 team roles as per Belbin's team inventory.
Your Agile Leadership Journey: Leading People, Managing Paradoxes
The document outlines an agenda for a workshop on managing paradoxes as an agile leader. It introduces the concept of paradoxes and polarity maps to understand seemingly contradictory situations. The workshop discusses four paradoxes leaders face and has participants analyze them using polarity maps to identify positives and negatives of each side, and signals to manage transitions. It emphasizes that managing paradoxes requires understanding context and proactively taking actions like anticipating signals to move to the upside. The goal is for participants to recognize paradoxes they face and apply strategies for managing them better.
Euro com 27 april
The document outlines the agenda and activities for an away day team building event on April 27th, 2012. The day includes sessions on prioritizing work, effective communication, and social styles. It will conclude with the teams working together to create company boards describing their strengths, weaknesses, mission, and vision.
Editing your Doc
This document outlines the editing process for a documentary film project. It discusses key stages including organizing footage, creating sequences for each character, doing a first assembly, rough cut, fine cut, and adding sound, color correction, and other finishing elements. Test screenings of the rough cut are emphasized as important for getting feedback to improve the film. Guidelines are provided for constructive criticism during screenings. The final sections list upcoming rough cut screening times and attendees.
A personal journey to opening bigger space of possibilities
The document provides instructions for a team-building exercise involving building shapes with materials and lowering them to the ground as a team. Teams must self-organize, build a simple or complex shape, and lower it to the ground without anyone losing contact with the shape. More sophisticated shapes earn more points. Participants are to complete a personal reflection identifying their own and others' action logics, how they act under pressure, how the exercise made them feel, and what they can learn from others' perspectives. They should reflect on how their typical action logic impacts results and the state of being and action logic they want to develop.
More Related Content
What's hot
The Slippery Slope
This document discusses how teams can unintentionally slip away from Agile practices over time if they are not careful. It provides examples of common "slippery slopes" such as skipping story estimation, not using relative sizing, carrying stories between sprints, and stopping daily standups. The author urges coaches to focus on helping teams form good habits in the first 3-6 months and celebrate successes while also constructively pointing out areas for improvement. Teams are reminded that Agile requires discipline and that changing habits is difficult, so they should avoid picking up bad practices.
Agile Engineering for Managers Workshop
The document discusses agile engineering practices and concepts. It begins by outlining objectives like understanding practices teams can use to handle complexity and the benefits they provide. The agenda then covers topics like what is meant by agile engineering, how practices relate to agile principles, iterative processes, user stories, and specific practices like source code control, pair programming, continuous integration, and testing. It emphasizes that these practices help produce quality code, allow for reliable and frequent deployments, and protect teams from issues.
Agile scrum-retrospective
What is Agile retrospective, and what is its importance. When and Why you should be doing it. The Do's and Dont's of Agile retrospective.
Retrospectives
This document discusses retrospectives, which are meetings where teams reflect on how to improve effectiveness. It explains that retrospectives are important for continuous improvement. Reasons to change retrospectives include getting stuck in routines, repeatedly facing the same issues, and lack of progress on problems. Different frameworks are presented for retrospectives, including Sailboat for identifying help/hindrances, Starfish for reviewing practices, and Three Little Pigs for evaluating processes and teamwork. Tips are provided such as using dot voting and rotating the facilitator role. Distributed tools for remote retrospectives are also listed.
Agile Retrospectives
The document discusses agile retrospectives and provides guidance on facilitating effective retrospectives. It outlines a 5-step format for retrospectives: 1) set the stage, 2) gather data, 3) generate insights, 4) decide what to do, and 5) close the retrospective. The facilitator's role is to make sure everyone contributes and a plan is created without solving problems for the team. The Scrum Master reflects the team's behavior back to help them improve. Team members should focus on the content, discuss openly, and make decisions. Retrospectives help teams continuously improve and change their definition of done, working agreements, and generate action items.
December 2009 Collaboration
This is a presentation I gave to pre-service teachers at Lake Forest College, December, 2009. The focus was on the "What, Why and How of Collaboration" in the classroom.
From Flab to Fab! Design Secrets for Overweight Interfaces
This document provides five design secrets for creating less overwhelming interfaces: 1) Use neutral base colors and strong accent colors with restraint and balance. 2) Create a strong anchor through placement, contrast, and indicating what users should focus on. 3) Vary box styles, create horizontal terraces, and reduce visual noise to "de-boxify". 4) Ensure consistent spacing, margins, and styles to "sweat the details". 5) Any combination of these secrets can be used to improve interface design outcomes.
How to go from structureless to structured without losing your vibe
The document discusses moving from a flat organizational structure to one with more hierarchy and leadership roles at a company. It notes that as engineering teams grow past a certain size, the flat structure breaks down, and it's time to consider roles like VP of Engineering or Director of Engineering. However, it emphasizes that these new leadership roles need clearly defined responsibilities and expectations to avoid confusion and ensure accountability. It advocates creating an engineering ladder or level system to establish clarity around hiring, pay, promotion criteria and growth opportunities for team members at different career stages.
What's hot (8)
From Flab to Fab! Design Secrets for Overweight Interfaces
From Flab to Fab! Design Secrets for Overweight Interfaces
How to go from structureless to structured without losing your vibe
How to go from structureless to structured without losing your vibe
Similar to Scrum Gathering London 2018: What's Really Going On? An Observational Skills Workshop
Agile2019_Observational Skills Workshop
The document describes an observational skills workshop presented by Julie Wyman and Mark Grove. The workshop includes exercises to practice observation skills by having participants observe a team building a structure and noting observations without interpretation. The goal is to help participants learn to provide better coaching support to teams by improving their ability to objectively observe team behaviors and interactions.
MHA 2020 observational skills workshop
Imagine you are asked to sit in on a team’s sprint review and retrospective. The team has been having difficulty forming and the Scrum Master has asked you to observe the team dynamics during these two sessions. Are you simply going to watch what’s going on or is there more you can do?
Agile Leadership 201: Enriching Management for AgileNoVA
This document outlines an agenda for a presentation on agile leadership and servant leadership. The presentation defines servant leadership as serving others first before leading, discusses common frustrations managers face when adopting this model, and provides exercises for attendees to brainstorm ways to address these frustrations. The presentation also covers topics like observing work processes, demonstrating curiosity, problem-solving proactively, and effectively delegating responsibilities. The goal is to help managers shift from a traditional leadership role to one that enriches their teams through servant leadership approaches.
Agile Leadership 201: Enriching Management
This is the latest in my series of leadership workshop sessions; this presentation includes the exercises and learning points. To see some of the text properly, you will need to get the free font Dark Roast.
Agile Leadership 201 for TriAgile
Enriching management is a key way to build Agile Leadership. This presentation helps make this concept of enrichment a bit clearer and how in turn management can learn to enrich its workforce as well. This provides some concrete mechanisms to make servant leadership real, without necessarily calling it servant leadership (shich sometimes doesn't resonate with people).
Ball Point Game: Self-organizing Your Flow of Work
In this revised version of Boris Glogger’s Ball Point Game, you and your teammates will be given a simple task that is challenging to execute. Working together, you’ll learn to self-organize to improve your workflow as you continuously find improvements to complete your task more effectively.
A Take on Different Retrospectives
The document discusses retrospectives and provides guidance on when and how to conduct them. It begins with questions to ask before a retrospective to plan objectives and considerations. It then discusses why retrospectives are important for process improvement and examples of when to conduct various types, such as pre-retrospectives before major initiatives. Personal retrospectives are suggested as a way for individuals to reflect and improve. Finally, different retrospective techniques are presented, such as constellation mapping to gather team feedback. The overall document serves as a guide for successfully facilitating retrospectives.
Kanban in Action Workshop
This two-part interactive workshop begins with a detailed look at how to interpret Kanban boards and ask thoughtful questions so that you can improve the work of your teams. We will provide an overview of the Kanban Method and then proceed through a series of eight short exercises that will give you an opportunity to review and interpret various Kanban board configurations with other attendees at your table. After a short break, part two of the session now puts the attendees in the driver’s seat to create their own board configurations. We provide eight business scenario exercises and ask the attendees how they would go about configuring their Kanban board given the unique system constraints for each scenario.
Your Agile Leadership Journey: Leading People-Managing Paradoxes - Agile Char...
This is the workshop Nicole and I gave at Agile Charm 2020 on Leading people through paradoxes, some of which are described directly in the Manifesto for Agile Software Development. It helps you understand how to use Polarity Maps as leaders for a thinking tool to understand your system.
5+Dysfunctions+of+a+Team_Final_20200228.pptx
Talks about dysfunctions of a team as per theory and practice
There are 9 team roles as per Belbin's team inventory.
Your Agile Leadership Journey: Leading People, Managing Paradoxes
The document outlines an agenda for a workshop on managing paradoxes as an agile leader. It introduces the concept of paradoxes and polarity maps to understand seemingly contradictory situations. The workshop discusses four paradoxes leaders face and has participants analyze them using polarity maps to identify positives and negatives of each side, and signals to manage transitions. It emphasizes that managing paradoxes requires understanding context and proactively taking actions like anticipating signals to move to the upside. The goal is for participants to recognize paradoxes they face and apply strategies for managing them better.
Euro com 27 april
The document outlines the agenda and activities for an away day team building event on April 27th, 2012. The day includes sessions on prioritizing work, effective communication, and social styles. It will conclude with the teams working together to create company boards describing their strengths, weaknesses, mission, and vision.
Editing your Doc
This document outlines the editing process for a documentary film project. It discusses key stages including organizing footage, creating sequences for each character, doing a first assembly, rough cut, fine cut, and adding sound, color correction, and other finishing elements. Test screenings of the rough cut are emphasized as important for getting feedback to improve the film. Guidelines are provided for constructive criticism during screenings. The final sections list upcoming rough cut screening times and attendees.
A personal journey to opening bigger space of possibilities
The document provides instructions for a team-building exercise involving building shapes with materials and lowering them to the ground as a team. Teams must self-organize, build a simple or complex shape, and lower it to the ground without anyone losing contact with the shape. More sophisticated shapes earn more points. Participants are to complete a personal reflection identifying their own and others' action logics, how they act under pressure, how the exercise made them feel, and what they can learn from others' perspectives. They should reflect on how their typical action logic impacts results and the state of being and action logic they want to develop.
AgileDC 2018: Team Splitting Experience Report
AgileDC 2018 Experience Report by Julie Wyman and Hunter Tammaro - Breaking Up is Hard to Do: How to Split a Team (Without Breaking It)
Outdoor game squares
1. The document describes an exercise where groups of 5 people are tasked with assembling puzzle pieces into squares of equal size without verbal communication.
2. Each group member is given pieces in an envelope to assemble their square, with the goal being to complete all squares at the same time since the task is not finished until all are equal in size.
3. Observers monitor the groups and take note of non-verbal communication attempts and how group members help or do not help each other reach the goal within the time limit.
Being the BEST we can be
Presentation given to Agile South Coast on the BEST View improvement model. Discussing why metrics are important, the format of the BEST View, how to create a BEST View and then leading the group through a practical.
Design Box Working Paper FDG 2014
The design box is a tool developed to aid in getting to the elevator pitch for a game or other creative product. It is intended as a tool to help groups deeply understand a problem and pitch creative solutions. This was presented at the Foundations of Digital Games 2014 conference aboard Liberty of the Seas as a work in progress.
Hands on with the Design Studio Method
In this hands-on, interactive session, Len will share some basic principles of the design studio method, share how you can use the design studio method to rapidly generate ideas for your own digital products, and then facilitate a mini design studio challenge that is sure to leave you with practical skills to apply to your work and bonded with meetup attendees.
Showcase Lego Serious Play
Imagine a methodology that boosts your meetings towards an innovative process for enhancing innovation and business performance. LEGO® SERIOUS PLAY® is developed based on research which shows that hands-on, minds-on learning produces a deeper, more meaningful understanding of the world and its possibilities. It deepens the reflection process and supports an effective dialogue – for everyone in the organization.
Similar to Scrum Gathering London 2018: What's Really Going On? An Observational Skills Workshop (20)
Agile Leadership 201: Enriching Management for AgileNoVA
Agile Leadership 201: Enriching Management for AgileNoVA
Ball Point Game: Self-organizing Your Flow of Work
Ball Point Game: Self-organizing Your Flow of Work
Your Agile Leadership Journey: Leading People-Managing Paradoxes - Agile Char...
Your Agile Leadership Journey: Leading People-Managing Paradoxes - Agile Char...
Your Agile Leadership Journey: Leading People, Managing Paradoxes
Your Agile Leadership Journey: Leading People, Managing Paradoxes
A personal journey to opening bigger space of possibilities
A personal journey to opening bigger space of possibilities
More from Julie Wyman
The Feedback Effect @ Global Scrum Gathering 2022
The document summarizes a workshop on improving feedback delivery. It discusses challenges with giving and receiving feedback, provides models for impact and clean feedback, and teaches how to reframing destructive criticism into constructive feedback. Participants practiced delivering impact and clean feedback through scenarios and reframing destructive examples constructively. The workshop aimed to help understand challenges with feedback, improve delivery techniques, and leave with actionable insights to apply when next providing feedback.
Limiting WIP @ SM Summit_5.17.22
The document discusses limiting work in progress (WIP) to improve productivity. Some key points:
1. Limiting WIP to 1-3 items leads to faster delivery, better quality, and less stress by avoiding multitasking. It also makes bottlenecks more visible.
2. Studies show multitasking is inefficient and can reduce productivity by 40% due to switching costs. Limiting WIP reduces context switching.
3. With too much WIP, teams spend most time waiting rather than working. Limiting WIP improves flow and enables faster response to changes.
InnoVAte 2022: KonMari Your Backlog
The document discusses applying the KonMari tidying method to product backlogs. It suggests taking five steps: 1) define the product vision, 2) find all product backlog items (PBIs) and put them in one place, 3) sort PBIs by category, 4) start with easier items, and 5) only keep PBIs that "spark joy" for customers. Story mapping is recommended for increased visibility and prioritization support. Regularly tidying the backlog facilitates better decision-making and leads to better products.
Agile for Humanity 2022: The Feedback Effect
The document discusses challenges and best practices for providing and receiving feedback. It aims to help participants understand their own fears around feedback, improve how they deliver feedback, and learn to respond openly when receiving feedback. The workshop covers recognizing destructive feedback patterns, using impact and clean feedback models, reframing criticism constructively, and a six-step framework for receiving feedback. Participants practice these skills and discuss how to apply the lessons to create a healthier feedback culture.
Top 3 Product Owner Challenges
The document discusses the top 3 challenges faced by Product Owners and recommendations to address them. The challenges are: 1) Trouble prioritizing work and finalizing decisions due to a lack of knowledge and direction. 2) Not attending meetings and having slow response times due to being overutilized with not enough bandwidth. 3) Constantly changing scope mid-sprint due to gaps in knowledge, interest, and process understanding. The document provides root cause analysis and recommendations such as establishing a clear product vision, deepening domain knowledge, increasing organization, and empowering the Product Owner role.
The Feedback Effect @ Music City Tech 2021
Feedback Workshop delivered by Julie Wyman and Nicole Spence-Goon at Music City Tech Conference on 9/17/2021
Agile2021 - The Feedback Effect
Slides from The Feedback Effect Workshop presented at the virtual Agile2021 conference by Nicole Spence-Goon and Julie Wyman on July 21, 2021
The Feedback Effect 2021
Almost everyone says that they REALLY REALLY want to receive feedback…so why does it feel like we hardly ever get meaningful, constructive feedback at the point in time when it would actually make a difference? Why do we come up with a list of reasons why we should just let something go, so that we can avoid having to deliver feedback ourselves? For many of us, the giving of feedback can feel like an awkward and uncomfortable task. And it’s because we avoid it whenever possible that we don’t improve these skills and we miss out on opportunities to help ourselves, our teammates, and our Agile teams grow.
In this interactive workshop, we hope to reduce anxiety around delivering feedback. First, briefly review some feedback anti-patterns, then introduce several different frameworks and approaches that you can use to prepare and organize your feedback. Then, since the best way to improve our skills is through deliberate practice, we’ll breakout into pairs to practice together through a series exercises in a fun and safe setting. We’ll swap roles as we go, so that everyone has equal opportunity to practice giving and receiving feedback.
If you are looking to improve your personal feedback skills, searching for ways to help your team become more open and willing to share feedback with each other, or interested in how simple practice and exercises can improve learning and build up skills, then this session is for you!
Limiting WIP: Doing Less to Do More
This session will review the concept of WIP and explore in-depth the reasons for limiting WIP: enhancing focus, reducing cycle time, optimizing flow and making bottlenecks visible. We will give strategies for starting out with WIP limits and suggestions for what to do when a limit is reached. Finally, we'll put theory to practice by running a short, virtual simulation that all attendees can participate in.
KonMari Your Backlog: Tidying Up Those PBIs
The document discusses applying the KonMari tidying method to product backlogs. It recommends defining a product vision, finding all product backlog items (PBIs) and putting them in one place, sorting PBIs by category, starting with easier items, and keeping only those PBIs that "spark joy" or delight customers. It provides tips on storage methods like story mapping and vertical folding. The goal is to simplify the backlog to facilitate decision-making and focus on the most important work.
Agile Lessons from Antarctica: Responding to Change over Following a Plan
This document discusses how planning and responding to change were balanced on an Antarctic cruise. While extensive planning is needed for safety and regulations, crews must also be flexible due to the remote, unpredictable environment. Lessons included continuing to plan but having adaptable plans, setting clear expectations, keeping goals while adjusting approaches, and changing goals if needed. Empathy is also key when plans change, as it is difficult but important that all understand changes. The takeaway is that both planning and responding to change are important to address unpredictable circumstances.
The Feedback Effect
In this this highly interactive workshop, we hope to reduce anxiety around delivering and receiving feedback. First, we’ll discuss what makes giving feedback such a challenge and then introduce several different frameworks and approaches that you can use to prepare and organize your feedback and your response. Then, we’ll practice together through a series exercises in a fun and safe setting. We’ll be swapping roles as we go along, so that everyone has equal opportunity to practice giving and receiving feedback.
Music City Agile - KonMari your Backlog: Tidying up those PBIs
The document discusses applying the KonMari tidying method to product backlogs. It recommends finding all product backlog items (PBIs), sorting them by category, and only keeping items that "spark joy" for customers. A 5-step process is outlined: 1) define product vision, 2) find all PBIs and consolidate, 3) sort by category, 4) start with easier items, 5) keep only items sparking joy. Story mapping and vertical folding techniques are suggested for organizing the backlog. Applying KonMari principles can lead to simpler, clearer backlogs that facilitate decision-making and development of better products.
Music City Agile 2019 - Measuring Flow: Metrics that Matter
The document discusses different metrics that can be used to measure workflow and flow, including throughput, lead time, cycle time, and cumulative flow diagrams. Throughput measures the number of work items completed over time and can be used for predictability. Lead and cycle times measure how long work items take to move through different stages. Cumulative flow diagrams visualize the number of work items in each stage over time to identify bottlenecks and work-in-progress. Improving flow through metrics can deliver work earlier, increase feedback, and smooth workloads.
#KonMari Your Backlog: Tidying up those PBIs
The document discusses applying the KonMari tidying method to product backlogs. It recommends five steps: 1) define your product vision, 2) find all PBIs and put them in one place, 3) sort PBIs by category, 4) start with easier items, and 5) only keep PBIs that "spark joy" for customers. Organizing PBIs using story mapping and treating them respectfully according to INVEST principles is advised. Tidying the backlog facilitates better decision-making and leads to better products.
BASD 2019 - Measuring Flow: Metrics that Matter
The document discusses various metrics that can be used to measure workflow and identify bottlenecks, including throughput, cycle time, lead time, and cumulative flow diagrams. It explains that prioritizing flow over utilization results in more rapid workflow and shorter response times. Various flow metrics are defined and examples are provided to illustrate how they can be collected and used to visualize trends, predict delivery times, and identify areas for improvement.
AgileDC2018: Agile Lessons from Antarctica
The document discusses how teams on Antarctic cruises must be able to adapt their plans in response to changing conditions, using penguin spotting plans as an example. It notes that teams must have a clear goal, understand forces outside their control can require changes, and emphasize increased empathy since change can be difficult. The key lesson is that responding and adapting to change is more important than rigidly following pre-made plans when operating in unpredictable environments like Antarctica.
Agile Dev West 2018_Measuring Flow: Metrics that Matter
The document discusses different metrics for measuring workflow, including lead time, cycle time, throughput, and cumulative flow diagrams (CFDs). It explains that lead time is the total time from start to finish of a work item, while cycle time does not include wait time. Throughput measures the number of work items completed within a time period. CFDs visualize the number of work items in different workflow stages over time to identify bottlenecks. The document provides examples of charts for these different metrics and discusses how teams can use metrics to understand their workflow and improve predictability.
Limiting WIP: Doing Less to Do More @ Big Apple Scrum Day_5.11.18
The document discusses limiting work-in-progress (WIP) to improve productivity. It explains that limiting WIP leads to better quality, faster delivery, and less stress by improving flow. Too much WIP results in long wait times and slow response to changes, while just enough WIP keeps work moving with some idle time used for improvements. The document advocates starting with small WIP limits and using slack time as a signal to address bottlenecks. An exercise demonstrates teams completing a paper airplane assembly task faster with limited WIP by reducing waste and improving flow.
Scrum Gathering Minneapolis_4.18.18_Managing Resistance with Kanban
The document discusses how Kanban and change management principles can help address organizational resistance to agile methods. It recommends focusing on identity, incremental change, feedback loops, and reducing disruption when implementing changes. Kanban emphasizes small, evolutionary changes through continuous improvement and limiting work in progress to reduce resistance and disruption compared to large transformations. Change management aims to engage stakeholders, manage expectations, and provide clarity around details of the transition to support lasting change.
More from Julie Wyman (20)
Agile Lessons from Antarctica: Responding to Change over Following a Plan
Agile Lessons from Antarctica: Responding to Change over Following a Plan
Music City Agile - KonMari your Backlog: Tidying up those PBIs
Music City Agile - KonMari your Backlog: Tidying up those PBIs
Music City Agile 2019 - Measuring Flow: Metrics that Matter
Music City Agile 2019 - Measuring Flow: Metrics that Matter
Agile Dev West 2018_Measuring Flow: Metrics that Matter
Agile Dev West 2018_Measuring Flow: Metrics that Matter
Limiting WIP: Doing Less to Do More @ Big Apple Scrum Day_5.11.18
Limiting WIP: Doing Less to Do More @ Big Apple Scrum Day_5.11.18
Scrum Gathering Minneapolis_4.18.18_Managing Resistance with Kanban
Scrum Gathering Minneapolis_4.18.18_Managing Resistance with Kanban
Recently uploaded
Digital Banking in the Cloud: How Citizens Bank Unlocked Their Mainframe
Inconsistent user experience and siloed data, high costs, and changing customer expectations – Citizens Bank was experiencing these challenges while it was attempting to deliver a superior digital banking experience for its clients. Its core banking applications run on the mainframe and Citizens was using legacy utilities to get the critical mainframe data to feed customer-facing channels, like call centers, web, and mobile. Ultimately, this led to higher operating costs (MIPS), delayed response times, and longer time to market.
Ever-changing customer expectations demand more modern digital experiences, and the bank needed to find a solution that could provide real-time data to its customer channels with low latency and operating costs. Join this session to learn how Citizens is leveraging Precisely to replicate mainframe data to its customer channels and deliver on their “modern digital bank” experiences.
Skybuffer SAM4U tool for SAP license adoption
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
June Patch Tuesday
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
Astute Business Solutions | Oracle Cloud Partner |
Your goto partner for Oracle Cloud, PeopleSoft, E-Business Suite, and Ellucian Banner. We are a firm specialized in managed services and consulting.
The Microsoft 365 Migration Tutorial For Beginner.pptx
This presentation will help you understand the power of Microsoft 365. However, we have mentioned every productivity app included in Office 365. Additionally, we have suggested the migration situation related to Office 365 and how we can help you.
You can also read: https://www.systoolsgroup.com/updates/office-365-tenant-to-tenant-migration-step-by-step-complete-guide/
Building Production Ready Search Pipelines with Spark and Milvus
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
5th LF Energy Power Grid Model Meet-up Slides
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...
Folding is a recent technique for building efficient recursive SNARKs. Several elegant folding protocols have been proposed, such as Nova, Supernova, Hypernova, Protostar, and others. However, all of them rely on an additively homomorphic commitment scheme based on discrete log, and are therefore not post-quantum secure. In this work we present LatticeFold, the first lattice-based folding protocol based on the Module SIS problem. This folding protocol naturally leads to an efficient recursive lattice-based SNARK and an efficient PCD scheme. LatticeFold supports folding low-degree relations, such as R1CS, as well as high-degree relations, such as CCS. The key challenge is to construct a secure folding protocol that works with the Ajtai commitment scheme. The difficulty, is ensuring that extracted witnesses are low norm through many rounds of folding. We present a novel technique using the sumcheck protocol to ensure that extracted witnesses are always low norm no matter how many rounds of folding are used. Our evaluation of the final proof system suggests that it is as performant as Hypernova, while providing post-quantum security.
Paper Link: https://eprint.iacr.org/2024/257
JavaLand 2024: Application Development Green Masterplan
My presentation slides I used at JavaLand 2024
Apps Break Data
How information systems are built or acquired puts information, which is what they should be about, in a secondary place. Our language adapted accordingly, and we no longer talk about information systems but applications. Applications evolved in a way to break data into diverse fragments, tightly coupled with applications and expensive to integrate. The result is technical debt, which is re-paid by taking even bigger "loans", resulting in an ever-increasing technical debt. Software engineering and procurement practices work in sync with market forces to maintain this trend. This talk demonstrates how natural this situation is. The question is: can something be done to reverse the trend?
Programming Foundation Models with DSPy - Meetup Slides
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...
The typical problem in product engineering is not bad strategy, so much as “no strategy”. This leads to confusion, lack of motivation, and incoherent action. The next time you look for a strategy and find an empty space, instead of waiting for it to be filled, I will show you how to fill it in yourself. If you’re wrong, it forces a correction. If you’re right, it helps create focus. I’ll share how I’ve approached this in the past, both what works and lessons for what didn’t work so well.
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
Leveraging the Graph for Clinical Trials and Standards
Katja Glaß
OpenStudyBuilder Community Manager - Katja Glaß Consulting
Marius Conjeaud
Principal Consultant - Neo4j
Best 20 SEO Techniques To Improve Website Visibility In SERP
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectors
Join us to learn how UiPath Apps can directly and easily interact with prebuilt connectors via Integration Service--including Salesforce, ServiceNow, Open GenAI, and more.
The best part is you can achieve this without building a custom workflow! Say goodbye to the hassle of using separate automations to call APIs. By seamlessly integrating within App Studio, you can now easily streamline your workflow, while gaining direct access to our Connector Catalog of popular applications.
We’ll discuss and demo the benefits of UiPath Apps and connectors including:
Creating a compelling user experience for any software, without the limitations of APIs.
Accelerating the app creation process, saving time and effort
Enjoying high-performance CRUD (create, read, update, delete) operations, for
seamless data management.
Speakers:
Russell Alfeche, Technology Leader, RPA at qBotic and UiPath MVP
Charlie Greenberg, host
"Choosing proper type of scaling", Olena Syrota
Imagine an IoT processing system that is already quite mature and production-ready and for which client coverage is growing and scaling and performance aspects are life and death questions. The system has Redis, MongoDB, and stream processing based on ksqldb. In this talk, firstly, we will analyze scaling approaches and then select the proper ones for our system.
Introduction of Cybersecurity with OSS at Code Europe 2024
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
Recently uploaded (20)
Digital Banking in the Cloud: How Citizens Bank Unlocked Their Mainframe
Digital Banking in the Cloud: How Citizens Bank Unlocked Their Mainframe
Astute Business Solutions | Oracle Cloud Partner |
Astute Business Solutions | Oracle Cloud Partner |
The Microsoft 365 Migration Tutorial For Beginner.pptx
The Microsoft 365 Migration Tutorial For Beginner.pptx
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Building Production Ready Search Pipelines with Spark and Milvus
Building Production Ready Search Pipelines with Spark and Milvus
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...
JavaLand 2024: Application Development Green Masterplan
JavaLand 2024: Application Development Green Masterplan
Programming Foundation Models with DSPy - Meetup Slides
Programming Foundation Models with DSPy - Meetup Slides
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Leveraging the Graph for Clinical Trials and Standards
Leveraging the Graph for Clinical Trials and Standards
Best 20 SEO Techniques To Improve Website Visibility In SERP
Best 20 SEO Techniques To Improve Website Visibility In SERP
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectors
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectors
Introduction of Cybersecurity with OSS at Code Europe 2024
Introduction of Cybersecurity with OSS at Code Europe 2024
Scrum Gathering London 2018: What's Really Going On? An Observational Skills Workshop
- 1. What’s REALLY Going On? An Observational Skills Workshop Julie Wyman Mark Grove
- 3. excella.com | @excellaco Imagine… You’ve recently joined a team as coach, consultant, or Scrum Master. You decide the best way to start is to “simply” observe the team working. • What do you notice? • What do you look for?
- 4. excella.com | @excellaco More than simply what you see on the surface.
- 5. excella.com | @excellaco Getting below the surface Some examples
- 6. excella.com | @excellaco Body Language • Crossed arms? • Leaning closer? Leaning away? • Pointing?
- 7. excella.com | @excellaco Tone of Voice • Whose voice is louder? Softer? • When does it get louder? • When does it get softer?
- 8. excella.com | @excellaco Pronouns • “He” or “she” instead of peoples’ names? • “Me” and “you” instead of “we”?
- 9. excella.com | @excellaco Physical Space • How are people positioned? • Are people facing each other? • What in the space is being used? Not used?
- 10. excella.com | @excellaco Collaboration • Is there a director? Doers? • Solo work vs. group work? • Who tends to offer ideas? Who tends to respond? • Is disagreement shared?
- 11. excella.com | @excellaco Decision Making • Do people think out loud? • How are decisions made? Consensus? Consultation? Direction?
- 12. excella.com | @excellaco Information Sharing • Verbal? • Visual? • Written?
- 13. excella.com | @excellaco Sharing your observations Some tips
- 14. excella.com | @excellaco When sharing observations… • Do factually state what you observed in neutral language • Avoid interpretation and assigning meaning to actions
- 15. excella.com | @excellaco Time to practice! Modified from a Coaching Beyond the Team activity
- 16. excella.com | @excellaco General instructions • Let’s practice – observing and sharing observations! • Two rounds: • One group will build while the other group observes • After the first round, roles will switch
- 17. excella.com | @excellaco Round 1: Instructions • Set up: Split into small groups groups (in each group, ½ will be builders & ½ will be observers) • Observers: Each pick one area to observe & use Post-Its to take notes (1 observation per Post-It) • Builders: Build a 5-foot tall structure out of index cards in 5 minutes or less
- 18. excella.com | @excellaco 5 minute timer Google timer
- 19. excella.com | @excellaco Round 1: Small group debrief • Share • Observers: share the notes from your post-its • Builders: share what it felt like being observed • Discuss • How did it feel to observe just one area? • Was it hard to write down only facts? • Did you notice any jumps to interpretation?
- 20. excella.com | @excellaco Round 2: Instructions • Set up: Builders & observers switch roles • Observers: Each pick one area to observe & use Post-Its to take notes (1 observation per Post-It) • Builders: Determine in 5 minutes the 3 most important characteristics of a high-performing team
- 21. excella.com | @excellaco 5 minute timer Google timer
- 22. excella.com | @excellaco Round 2: Small group debrief • Share • Observers: share the notes from your post-its • Discuss • Did you do anything differently as observers this round having previously been observed yourselves? • How did it feel to observe just one area? • Did you notice any jumps to interpretation?
- 23. excella.com | @excellaco Wrapping it up And keeping it going
- 24. excella.com | @excellaco • What did you learn about being an observer? • What did you learn about how it feels to be observed? • What will you do differently next time? Time to reflect…