What’s REALLY Going On? An Observational Skills Workshop

schedule Sep 23rd 01:00 - 01:45 PM place Ballroom C people 20 Interested

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? Perhaps you are seeing interactions and team dynamics at play without truly realizing what you are observing. And when you do observe, are you injecting your own biases into those observations? Observation is a powerful tool, but one which we may not take advantage of to its true potential. After all, what exactly should we be observing, anyway?

By learning how to expand our observational skills in a non-biased and non-judgmental manner, we can gain a deeper understanding of team dynamics and interactions allowing us to offer more meaningful and impactful support, coaching, and empathy. Because there are many observational aspects that pass us by, the best way to become more observant is through deliberate practice. So, let’s practice together with a group exercise in a fun and safe setting!

In this highly interactive workshop, we’ll start by sharing tools and tips to make you a better observer. Then we’ll ask for a small group of volunteers (“builders”) to be observed performing a brief task. The remaining attendees will practice applying the observation techniques, and, after the builders finish, will share their observations in small groups. We’ll conclude with a full-group debrief and discussion of the key takeaways and opportunities to improve our effectiveness and observations.

If you’re looking for new ways to connect with your team, to enhance your agilist toolkit, or simply participate in an informative and interactive workshop, this session is for you!

 
 

Outline/Structure of the Workshop/Game

(Note: the slides and video are from a longer version of this workshop, but the outline below reflects how this workshop has been tailored for a 45-minute session)

This session is highly interactive and will include a small amount of delivered content, followed by a small group exercise and discussion, and conclude with a large group debrief. The small group exercise is a modified version of an activity run by Esther Derby and Don Gray in their "Coaching Beyond the Team" course.

1) SESSION INTRODUCTION & WARM-UP (5 min)

  • Introduce facilitators & learning objectives
  • Warm up prompt

2) CONTENT INTRODUCTION (10 min)

  • Sets up the learning outcomes and small group portion of the workshop.
  • Highlight how learning and practicing observational skills is a tool in a coach or Scrum Master’s toolbox allowing us to offer more meaningful and impactful support, coaching, and empathy.
  • Highlight some potential observation areas (body language, tone of voice, use of pronouns, use of physical space, type of collaboration, decision-making process, mode of information sharing, etc.)
  • Review tips for effectively sharing observations with others (ex. factually stating in neutral language, withholding interpretation and judgement).

3) PRACTICE OBSERVING & SHARING OBSERVATIONS (20 minutes)

  • Ask for eight volunteers to serve as “builders” performing a simple and fun task in the front of the room (all building supplies will be provided). The building challenge will last 5-minutes.
  • Before the building starts, observers at each table group will discuss and agree on what each person will focus on observing. It is recommended that each observer pick just one area to observe and that observers in the same group don't all focus on the same thing. A worksheet with a list of potential observation areas will be provided.
  • During the building challenge, a large timer will be running to help keep track of remaining time. Observers will write notes in real-time as they observe the builders (Pens and post-its will be provided to observers).
  • After the building exercise, small groups will spend ~10 minutes sharing their observations with each other.

4) FULL GROUP DEBRIEF AND CLOSE (10 minutes)

  • Facilitators will ask for several of the small groups to share their key takeaways, then open up to a larger debrief and full-group discussion.
  • What did you learn about being an observer?
  • What was it like focusing on only one observation area?
  • Was it difficult to keep your observations neutral and avoid interpretation?
  • What did you learn about how it feels to be observed?
  • How might improving your observation skills enable you to better help your team(s)?
  • What will you try to work on after the session to improve your observation skills?

Learning Outcome

  • Learn new tools and tips to enhance your observational skills
  • Practice observing different types of interactions
  • Build empathy for what it feels to be observed
  • Learn how to share observations in neutral, non-judgmental language

Target Audience

Scrum Masters, agile facilitators, team members, and anyone who wants to improve their observational skills!

Prerequisites for Attendees

None

schedule Submitted 5 months ago

Public Feedback

comment Suggest improvements to the Speaker

  • Liked Richard Cheng
    keyboard_arrow_down

    Richard Cheng - How to REALLY use the Agile values and principles!!

    Richard Cheng
    Richard Cheng
    Principal
    Excella Consulting
    schedule 3 months ago
    Sold Out!
    45 Mins
    Workshop/Game
    Beginner
    Your organization is doing Agile, which great, but what does that really mean? Perhaps they are implementing Scrum, or Kanban, or one of the other Agile methods, but are they really being Agile? Does it feel like you are you are doing Scrum, but you’re team isn’t really Agile? There's difference between doing Agile and being Agile and this session explores that concept.

    In this session, we’ll understand what Agile really means and how that relates to the way we implement our Agile methods within our organizations. We'll identify how we effectively use the Manifesto value points so that we can maximize the value of our products while still ensuring that we have quality and governance built into our process. This session will also explore the use of Agile principles to guide our strategic and day to day decisions.

    This sessions is great not only for beginners, but for anyone who wants to get past simply implementing Scrum or Kanban by the book, but really understand how to use Agile values and principles to build better products and organizations.
  • 45 Mins
    Talk
    Beginner

    Have you tidied up your personal life with Marie Kondo and are now wondering how to achieve the same effect in your work life? Do you have the feeling that the most valuable product backlog items (PBIs) are getting lost under a mountain of old stories, bugs, and tasks? Maybe you know a change is needed, but feel completely overwhelmed about where to start? If so, join us to learn how to make your product better through the life changing magic of tidying up your backlog.

    We’ll start by exploring the costs of a large, cluttered product backlog and share a short quiz you can use to gauge the current state of your own backlog. Next, we’ll cover how we’ve adapted the KonMari method and introduce five easy steps you can take to get started in your tidying process. We'll share real-life examples along the way, calling out potential pitfalls to avoid (don’t become a storage expert!), and illustrating how story mapping may be the magical backlog equivalent to Kondo’s “vertical folding” technique. By the end of the session, you’ll know the specific next steps to take so that you too can realize the many benefits of a tidied-up product backlog: improved visibility, increased self-organization, and easier decision-making.

  • Liked Mathias Eifert
    keyboard_arrow_down

    Mathias Eifert - Complexity is the Enemy! How Agile Practices Allow Us to Operate in a VUCA World

    45 Mins
    Talk
    Intermediate

    One of the key advantages of Agile over plan-driven approaches is that an Agile mindset acknowledges our ever-diminishing ability to usefully predict the future and focuses our efforts on managing change instead of trying to suppress it. This “new reality” has become pervasive enough to drive its own buzz word – VUCA, which stands for Volatility, Uncertainty, Complexity, Ambiguity. But beyond the hype lies a truth that Agile leaders need to understand and embrace – that certain problems really do respond differently to our attempts to manage and solve them. Why does this matter? Because problem contexts that defy straightforward cause-and-effect expectations significantly impact productivity while simultaneously presenting much higher risks to success. Even worse, applying leadership approaches that aren’t matched to the problem context dramatically increases the danger of catastrophic failure.

    In this session, we’ll examine how the Cynefin framework helps us make sense of what kinds of problems we’re dealing with and how we should approach them. We will then look at ten ways in which Agile frameworks, approaches and technical practices help us manage or even reduce complexity and one where they fall short. You will walk away with a deeper understanding of how - and why - the things we do as agilists increase stability and reduce risks for our teams.

  • Liked Mark Koenig
    keyboard_arrow_down

    Mark Koenig - Continuous Modernization

    Mark Koenig
    Mark Koenig
    Scrum Master
    Excella
    schedule 3 months ago
    Sold Out!
    45 Mins
    Talk
    Intermediate

    Rather than engaging in an intense modernization effort followed by years of minimal maintenance, a better alternative often is modernizing a system continuously, balancing operations, maintenance, and renovation. Ideally you can improve, update, and upgrade the software system one piece at a time while it continues to operate, avoiding feature freezes and scary cut-overs.

    There are always trade-offs to be made, but some approaches better fit IT systems with long-lived missions. At a certain point, a whole-sale rewrite is the best option for replacing stale, decaying software before it leads to major headaches and eventual catastrophe. Big rewrites have big risks and big failures, however. Because of the stability and enduring mandates of some software systems, long-term investments in IT systems pay off and give room for smart maintenance strategies.

  • Liked Mindy Bohannon
    keyboard_arrow_down

    Mindy Bohannon - I’m a BA Girl in an Agile World

    Mindy Bohannon
    Mindy Bohannon
    Agile Business Analyst
    Excella
    schedule 3 months ago
    Sold Out!
    45 Mins
    Experience Report
    Beginner

    Have you ever worked with a Business Analyst (BA)? Is what a BA does on an agile project much different from what is done on a waterfall project? All analysts bring excellent communication, collaboration, and trust to their work on project teams. During this session we’ll review the roles a BA can play, a BA's responsibility on the development team, and the skills a good BA possesses. For fun, lets also talk about why an Analyst is part of the 3 Amigos and the complexity of communication channels. Generally speaking, let’s discuss how BAs participate in an agile project’s success and I’ll share some stories about my experience going from waterfall to agile, how I’ve interacted with the PO, and important things I think an Analyst should be involved in.

  • Liked Adam Parker
    keyboard_arrow_down

    Adam Parker - NoEstimates at Scale in the Federal Government

    Adam Parker
    Adam Parker
    Agile Coach
    Excella
    schedule 4 months ago
    Sold Out!
    45 Mins
    Experience Report
    Advanced

    Come learn how our 3 teams, operating in a LeSS-style scaled model, experimented with a NoEstimates approach to development work and then adopted that as our way of working for a year in the Federal government. Included in our story is a switch to Kanban, returning to Scrum, and eventually returning to pointing work. It has been a remarkable journey that I'm excited to share!

  • Liked John Tanner
    keyboard_arrow_down

    John Tanner - Using Metrics for Good not Evil or: How I learned to Stop Worrying and Love the KPIs

    45 Mins
    Workshop/Game
    Beginner

    Using metrics for punitive reasons is a problem as old as time. In software, this is further complicated by the fact that people rarely agree on why we are collecting metrics in the first place. In this session we will explore how we can use metrics for good instead of evil.

    By focusing on the goal of system improvement, rather than individual performance, we can begin leveraging data to make a positive difference in how we work while also delving into why we work the way we do.

    This session will include real-world examples of problems that organizations create for themselves by using metrics for the wrong intent. We will also discuss examples of good metrics and how they can be used to make our lives better.

  • Liked Paul Boos
    keyboard_arrow_down

    Paul Boos - Agile Leadership 201: Enriching Management

    Paul Boos
    Paul Boos
    IT Executive Coach
    Excella
    schedule 5 months ago
    Sold Out!
    45 Mins
    Tutorial
    Executive

    The Agile Manifesto doesn't explicitly talk about what changes in management should happen and neither do the approaches. In fact, sometimes we hear the exact opposite from teams - "What do we need managers for..?" or perhaps "Can't they just get rid of all the impediments we have?"

    As a former manager and now as a coach, I find the words Servant Leadership sometimes doesn't resonate. It actually only paints part of the picture anyway. What we want are ways to enrich management so that they can do more for the organization and its teams. Let's discover what some of this enrichment might be.

  • Liked Nicole Spence-Goon
    keyboard_arrow_down

    Nicole Spence-Goon - Peaks or Valleys? The power of Scaling Agility in the alphabet soup of Government agencies

    Nicole Spence-Goon
    Nicole Spence-Goon
    Agile Coach
    Excella
    schedule 3 months ago
    Sold Out!
    45 Mins
    Experience Report
    Beginner

    Do you feel like Agile Scaling has become a goal rather than the means to an end for your organization? To determine where you stand on the Scaling spectrum, ask yourself a few soul-searching questions: Why do we need to scale? Is this the right time for us to scale? If you’ve checked these boxes, you may wonder “where do I go from here?”

    This talk will focus on 3 areas that emerged as common themes throughout my experience working on government Agile Scaling projects and ultimately influenced the trajectory of each agency's scaling journey:

    • Communicate vision consistently
    • Focus on your people genuinely
    • Create your own path intentionally

    I've seen successes and some struggles with Agile Scaling efforts in government agencies. Regardless of the agency acronym or the frameworks used, these key elements shaped their scaling outcomes.

  • Liked Zack Ayers
    keyboard_arrow_down

    Zack Ayers / Joshua Cohen - Andon Cords in Development Teams: Our Experience of Driving Continuous Learning through a Culture of Experimentation

    45 Mins
    Talk
    Beginner

    Summary

    In this session, you’ll learn about one team’s struggle to improve collaboration and how they sought to shorten cycle time by carefully crafting an experiment with an Andon Cord. The Andon Cord is a Toyota innovation designed to empower front-line employees to recognize issues, initiate a stoppage of work, and work together as a team to quickly identify a path forward. The emergency cable strung above assembly lines became a symbol of the Toyota Way, and has widely been copied throughout the auto industry and beyond.

    You’ll be introduced to metrics that show a surprising correlation between collaboration through Andon Cord pulls and Cycle Time!

  • Liked David Fogel
    keyboard_arrow_down

    David Fogel / David Bujard - Nine levels of Agile Hell... and how to get out!

    45 Mins
    Talk
    Beginner

    Government Agile transformations can feel like overwhelming efforts – but do not abandon hope! This interactive, audience-driven presentation reviews how government and large organizations ESCAPE common Agile adoption challenges.
    You - the audience - will prioritize your pain points; we’ll focus on the five Agile hells most highly prioritized. We will discuss real examples of “escaping” out of each Agile hell, with pro tips and success patterns you can apply.
    The Agile hells we've escaped include:

    • No Transformation hell - A federal program or department wants to change but can’t start or can’t finish
    • Too Fast hell - Newly Agile federal programs sometimes respond TOO rapidly, too often changing priorities.
    • Technical hell - Programs can become bogged down in technical debt and manual processes.
    • No Trust hell - Government delivery can be slowed by lack of trust between contractors and feds, between business and IT, or between compliance and delivery groups.
    • Product Owners hell - Government Product Owners can be unavailable, think they are managers, aren’t empowered to provide vision, or struggle with prioritization
    • Too Big hell- A frequent pattern in federal Agile! Large batches produce slow progress, low visibility and high complexity, seen in big programs, big deployments, and big contracts.
    • Collaboration hell - Government teams can struggle with collaboration within the same organization across roles and across the fed-contractor divide.
    • Stove-piped hell - Government organizations can struggle to collaborate across contractual or organizational boundaries within the same enterprise
    • Leadership hell - An organization can only be as agile as its leadership. In the government, how can you work with leaders who aren't ready to be agile?

    For each Agile hell, we focus on successful techniques to escape from these common dynamics. Unlike other presentations, we won't be doing a deep dive, but we will cover the most important challenges our audience face.

  • 45 Mins
    Talk
    Beginner

    On average Agile transformations get into trouble at about 14 months from the time they start. Have you ever wondered why?

    Is it because you started from 'the bottom up?" Or is it because you spend time, money, resources and people creating great teams and didn't pay attention to having a professional, empowered Product Owner organization?

    Agile transformations that target department level and not the organization have a very low success rate and you end up with an agile department enveloped by a traditional organization. That leads to dark work, decision delay and dysfunction.

    So, what can you do?

    Come and learn some of what I learned the "hard way" over 7 transformations.

  • Liked Dane Weber
    keyboard_arrow_down

    Dane Weber - Undercover Scrum Master

    Dane Weber
    Dane Weber
    Lead Consultant
    Excella
    schedule 3 months ago
    Sold Out!
    45 Mins
    Experience Report
    Intermediate

    After three years as a Scrum Master and Agile coach, I hit a wall coaching a team that did not want to try popular Agile engineering techniques such as TDD and pair programming. I had become a Scrum Master after four years working on the business analysis and account ownership side of things and could not speak from personal experience about engineering practices. In order to get some first-hand experience and to gain a new perspective, I chose to spend a year or two as a software developer on a Scrum team.

    The experience has been eye-opening. I experienced a tremendous cognitive load working with a wide array of technologies; this pulled my attention away from many of the collaborative and process-oriented activities I cared about as a Scrum Master. I was surprised to feel strong pressure to complete work quickly, cutting corners, even when the Product Owner and Scrum Master were not asking me to. When this pressure was explicit, it usually came from my fellow developers. On the other hand, there is real joy in writing code and seeing a system do something worthwhile that it wasn't doing before. My outlook has changed tremendously and is something I want to share with anyone who works with development teams, especially Scrum Masters and other coaches. I am still enjoying my time as a developer, but I'm looking forward to returning to coaching and incorporating this experience into my approach.

  • Liked Mark Grove
    keyboard_arrow_down

    Mark Grove - Authority and Trust: Finding the Scrum Master Balance

    Mark Grove
    Mark Grove
    Excella Consulting
    schedule 4 months ago
    Sold Out!
    45 Mins
    Talk
    Beginner

    Have you ever seen the term “process authority” used to describe the role of a Scrum Master? You don’t have to look too hard to find this description. In my experience, it has caused a lot of confusion and misunderstanding on project teams. So why is it even used? And should it?

    I worked on a new Scrum project where management informed the project teams that the Scrum Master role was given process authority over the team. There was a lot of confusion and unease about this. Questions started popping up such as “I already have a manager – is the Scrum Master now my boss,” “What does process authority mean,” and “Do we really have to do what she says?” As a result, the teams were becoming hostile to the Scrum Master role, untrusting of the Scrum Master’s responsibility, and concerned Scrum Masters had authority to tell the teams what to do. I was the project’s agile coach and needed to diffuse the confusion and better the working environment as quickly as possible. This did not happen overnight, but our journey started with this interactive discussion which we used as a foundation for the project moving forward.

    In this interactive presentation, we explore the concept of “process authority” and consider the various directions it takes us. To do that, this discussion goes far beyond a typical “the role of a Scrum Master” presentation; It explores…

    • What it should (and should not) mean when/if “process authority” is used to describe the Scrum Master role
    • How the responsibility and expectations of a Scrum Master are different than that of team members
    • How different leadership styles play into understanding the role of the Scrum Master
    • The importance of trust in a Scrum Master/team relationship

    The presentation uses real-time audience feedback to further explore these topics. Audience members will provide answers to questions given throughout the presentation, so we can explore members’ thoughts, opinions, and experiences they have had with the Scrum Master role.

  • Liked Dr. Patrick McConnell
    keyboard_arrow_down

    Dr. Patrick McConnell - The Velocity Trap: Learning to Value Enterprise Outcomes over Team Output

    45 Mins
    Tutorial
    Beginner

    Behind the creation of every Agile Framework was the intention to improve the Return on Investment for creative work, primarily through faster and richer feedback. But as team-level frameworks like Scrum are internalized by large organizations, that message gets mistranslated. Instead of, “Get better outcomes, sooner,” the drive instead becomes, “Just do more, faster.”

    A common expression of this problem is the confusion of Velocity for Value, where teams are directly managed based on their Output, but the connection between Output and Outcome is lost or ignored. This plays out in all kinds of ways that distract from achieving tangible results, and often incentivizes internal competition over collaboration. This problem can be especially tenacious in organizations with significant institutional ‘status-ing’ behaviors, where leadership struggles to translate common Agile methods like Relative Estimating into existing artifacts like Executive Dashboards or Earned-Value Management.

    In this tutorial, participants will explore the 'Velocity Trap', and will be shown how to setup a results-driven framework that prioritizes 'Maximizing Outcomes while Minimizing Output.'

  • Liked Mindy Bohannon
    keyboard_arrow_down

    Mindy Bohannon - GiveCamp Case Study: Agile and Scrum at the Speed of Light

    Mindy Bohannon
    Mindy Bohannon
    Agile Business Analyst
    Excella
    schedule 3 months ago
    Sold Out!
    45 Mins
    Experience Report
    Beginner

    Cleveland’s GiveCamp is the most magical, exhausting, and worthwhile 48 hours I’ve ever experienced professionally. In 2015, 200 techies volunteered their talents and passion to help 19 non-profits with projects including data collection, websites, GPS-enabled mobile app, an educational online game, and database applications. How does so much work get done in such little amount of time? Agile in hyperdrive – standups every 4 hours, adhoc swarming with heavy hitter devs roaming the projects, and lots of free food and drinks to keep everyone fortified. This case study reviews how so much work was done in such a short amount of time.

  • Liked Paul Boos
    keyboard_arrow_down

    Paul Boos - Overcoming Your Biases: Putting the GROW and Satir Interaction Models to Work

    Paul Boos
    Paul Boos
    IT Executive Coach
    Excella
    schedule 4 months ago
    Sold Out!
    45 Mins
    Workshop/Game
    Intermediate

    If you hold any form of leadership position, whether as a manager, scrum master, or coach, you will find that you will be at times offering guidance or advice. What unfortunately happens though is that your observation of the need and conversation to help fill that need can get tangled with your biases. Want to improve your coaching conversations? Then this workshop is for you.

    To help you work through the arc of your conversation and understand how these biases come into play, we're going to discuss the GROW conversation model and the Satir interaction model. This workshop will open with an anchoring activity. We'll then use an exercise and focused discussion to review each model and see how these played into the coaching received.

  • Liked Paul Boos
    keyboard_arrow_down

    Paul Boos / George Paci - DevOps Your Organizational Change

    45 Mins
    Workshop/Game
    Intermediate

    DevOps has become all the rage from a technical change perspective; it really has changed the game. And while it provides numerous benefits, only after you also embrace the human side of change within the organization, can you really get to full Agility.

    What if we could take advantage of a continuous delivery of change just like we do in our development pipelines? As executives, managers, Scrum masters, coaches, or anyone else in a leadership role, we should desire to make each change focused, easy, and small to contain risk. Once this is done, changes can mimic a development pipeline that delivers towards a business outcome. This workshop will help you learn how to keep the number and size of changes in check and consider how to manage the risks of deploying change.

  • 45 Mins
    Talk
    Intermediate

    Scrum is easy to understand but hard to implement. Many team members think of Scrum as a framework with roles, meetings and artifacts. They take a training class and come back to work and take on new roles, setup Sprint planning, standups, reviews, and retrospectives. They start working in Sprints using product backlogs, user stories, task boards, and burn down charts. Things start out well, however, soon difficulties arise and anti-patterns and smells emerge as teams start moving from Scrum to ScrumBut. You’ll often hear “We do Scrum but we don’t have an engaged Product Owner” or “We do Scrum but we don’t test within the Sprint”. In this interactive session we will tie elements of the Scrum Framework to the values and principles of the Agile manifesto to better understand the purpose behind the framework and it’s roles, meetings and artifacts. Come to this session to understand the reasons things are setup in a certain way so that you can assess the implications, risks and impacts of deviating from the basic framework.

  • Liked Dr. Patrick McConnell
    keyboard_arrow_down

    Dr. Patrick McConnell - How do we know when stuff will be done? Let's Play the Release Planning Game.

    45 Mins
    Workshop/Game
    Beginner

    Product Roadmapping, Release Planning, and Release Management are often difficult skills to learn for the Product Owners and Product Managers that support Agile Teams. If the estimates are fuzzy, and don't translate exactly to a linear measure like time, "How do we know when anything will be done?"

    Participants in this workshop will get hands-on experience planning and managing a product Release, and deal with the same dynamics that real Product Owners experience collaborating with Agile Development Teams. Working in Teams, participants will play The Release Planning Game, a tabletop board game created by the facilitator for use in Certified Scrum Product Owner classes.