Addressing Cultural Problems with "Popular Theatre" Techniques

Cultural change in any organization or team is admittedly one of the most challenging processes. However, any team or group of people can be empowered to find insights and a way to address cultural issues with the techniques of "Popular Theatre" - described as theatre for the people, by the people, with the people. Participants will be taken through the simple steps of identifying challenges/problems, role-playing and creating scenes that provide a window into the issue, where everyone looks at it together and suggests steps and solutions. These scenes become a rehearsal for reality.

 
5 favorite thumb_down thumb_up 2 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

1. Participant introductions/ expectations.

2. Introduce background of Popular Theatre.

3. Exercises to assist in vocal, physical and creative freedom.

4. Identifying cultural dissonances they've experienced.

5. Self-organizing into teams.

6. Help teams through process of role-playing and collaborative scene development.

7. Presentation of scenes with audience discussion.

8. Questions.

Learning Outcome

1. A new tool: the techniques of "Popular Theatre" which can be used in diverse circumstances.

2. The effectiveness of role-playing and collaborative scene-work to solve difficulties.

3. Feeling empowered and inspired to deal with cultural dissonances.

Target Audience

Any agile practitioner at any level, working on a team, or within an organization

Prerequisite

Please wear comfortable clothing and be prepared to fully participate in the exercises and activities. Participants can expect to be thoughtfully engaged, have fun and be freely creative.

schedule Submitted 2 months ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Paul J. Heidema
    By Paul J. Heidema  ~  3 weeks ago
    reply Reply

    This looks both joyful and highly participatory, Valerie! It is just what we need in our agile community - a new approach to engagement and collaboration. Superb!

    • Valerie Senyk
      By Valerie Senyk  ~  3 weeks ago
      reply Reply

      Thanks Paul - I believe I CAN make a contribution to the agile community - I appreciate your vote of confidence!


  • Liked Chris Murman
    keyboard_arrow_down

    Chris Murman - Things Are Broken: A Case Study In Moving Tooooooooo Fast

    Chris Murman
    Chris Murman
    Sr. Agile Consultant
    Solutions IQ
    schedule 4 weeks ago
    Sold Out!
    60 mins
    Talk
    Intermediate

    Speed.

    It's been a driver in our industry before it was even an industry. The more Agile becomes more mainstream, the more we think it's part of the package. Books are out promising that certain frameworks can deliver twice as much in half the time. And yet, teams still struggle delivering what's expected of them.

    Once I started asking people of all levels of leadership what they thought speed would give them, it allowed me to develop some experiments around those expectations.

    Please join me for a case study where we discuss the need for speed, the origins of that desire, and the ways it manifests itself into deliverables. My desire is for the audience to take away some powerful learning into their places of work. Only by understanding the expectations around speed can we reset them into an environment built around trust and support for motivated individuals.

  • Liked Johanne Boyd
    keyboard_arrow_down

    Johanne Boyd - Why can't the business be agile too? How ADP is incorporating business Agile practices to keep up with technology

    40 mins
    Talk
    Beginner

    Does your business struggle to catch up and understand the technical deliverables from your Sprint Reviews? Is there unnecessary re-work and scope creep because requirements are not properly described by the business? ADP has sought to address these issues by incorporating business Agile practices to keep up with technology. The result? Clearer requirements, strong engagement during Sprint Reviews and a collaborative solution with business readiness aligning with technical deliverables. Join our session to find out more!!

  • Liked Steve Zhang
    keyboard_arrow_down

    Steve Zhang - The Joy Of Functional Programming

    60 mins
    Talk
    Intermediate

    The popularity of Functional Programming is booming! Are you still wondering what all of the fuss is about? Come to this session and find out! This is an introduction to the power of functional programming. It covers functional programming's basic concepts, and shows you how functional programming will make software simple, elegant, easy to test, and lead to cleaner code. I will share my experiences learning, so you can avoid some of the pitfalls. So if you enjoy coding, love clean code, then you should start learning Functional Programming right now.

  • Liked Mishkin Berteig
    keyboard_arrow_down

    Mishkin Berteig - JIRA is the Worst Possible Choice

    90 mins
    Workshop
    Intermediate

    A rant, with evidence, on why electronic tools in general, and JIRA in particular, are anti-Agile. Participants will use the Agile Manifesto to evaluate the electronic tools they are currently familiar with. JIRA is used as a case study.

    NOTE: Scrum asks us to have courage. The Agile Manifesto asks us to value individuals and interactions over processes and tools. I hope the organizing committee will consider this proposal despite the risk that it might offend some tool vendors. If we can't speak freely about our experiences with tools, we will fail as a community.

  • Liked Dave Dame
    keyboard_arrow_down

    Dave Dame - Design Thinking for Organizational Change

    40 mins
    Talk
    Beginner

    We all know how people use design thinking to create better products and deliver delightful experiences to our users. However, design thinking can be an excellent tool to use for organizational change. In the case of organizational change, our product is the change that we are trying to drive, and our customers are those people who are impacted (internally and externally) and have to live with that change. In the same way that design thinking puts the user front-and-centre for products, it can be used to put people in the organization front-and-centre. In this talk we will discuss how design thinking works and, as a case study, how we have applied it at Scotiabank to help drive adoption of the Bank’s NPS customer insights into building solutions that serve our customers. In that program, previous internal processes were ineffective in pushing relevant data to delivery teams at the right time. Using a Lean or Agile approach would have provided some benefit, but taking a design thinking approach uncovered an array of useful insights to make the whole process more purposeful. Learn from this example to explore how you might incorporate design thinking to drive greater effectiveness and relevance for your team’s body of work.

  • Liked James Gifford
    keyboard_arrow_down

    James Gifford - 5 Metrics to Create Safety and High Performing Teams

    60 mins
    Talk
    Intermediate

    Description:

    I see that a lot of organizations use metrics in inappropriate ways to measure teams. At the heart of these metrics, nine times out of ten, are velocity and story points. These metrics lead to a lot of mistrust, fear, and bad technical practices. This talk will focus on shifting the focus to diagnostic metrics.

     Before shifting focus to diagnostic metrics, we need to understand what inappropriate metrics are. When questioning teams about why their velocity was lower from one sprint to another, teams are more likely to inflate their estimates to avoid questions in the future. This is one of my scenarios. We will explore this case and my other top-ten based on the 165 teams I have interacted with. Focusing on one metric does not provide a balanced view of the team.

    For balance, I promote five metrics. The combination of metrics balances each other. These five metrics are lead time, quality, happiness, agile maturity, and business value. Focusing on these five metric areas can be used as a diagnostic tool to help teams grow and support coaching. During the session, we will use my Excel-based tool and visual model to simulate this balance.

    When you push shorter lead times (how fast) on a team with a lower agile maturity, the first thing to change is quality, followed by happiness and then the delivery of value. Conversely, if a team focuses on TDD, the first thing to change is quality, followed by agile maturity, reduction in lead time, and increased delivery of value.  

    Teaching teams to harness data in a positive way will help them to flourish.

  • Liked Paul J. Heidema
    keyboard_arrow_down

    Paul J. Heidema - Think Agile Retrospectives are Boring? Think Again: Let's Create a Whole New Set of Activities

    90 mins
    Workshop
    Beginner

    Last year, I was at an Agility Day in New Jersey for my company (ADP). During this day of fun, we uncovered and created new ways of improving retrospectives and new retrospective activities.

    You don't have to always do "Start, Stop, Continue" or "Pluses and Deltas". There are plenty of activities that are more creative and more joyful for teams and groups!

    In this workshop, we will follow a powerful technique to brainstorm ideas, filter down to the best ones, and then try them out on each other to uncover new and more effective retrospective activities. Come prepared to contribute to a new group of retrospectives!

    Gamestorming - Divergent Emergent Convergent

    We will go through a divergent process, and emergent process, and a convergent process in creating our new retrospective techniques. These and other powerful techniques will be utilized from the book Gamestorming to harness the power of the participants to create powerful and useful retrospective activities.

  • Liked Taimur Mohammad
    keyboard_arrow_down

    Taimur Mohammad - Surviving Disruption with Agile: Innovate or Die

    40 mins
    Experience Report
    Intermediate

    Lean-Agile is easily & often associated with customer centric products and solution. The “customer facing” nature of the product allows for thin slicing, feedback and iteration which in turn leads to greater business agility and customer satisfaction. While there have been many exceptional case studies that demonstrate this, applying lean-agile to non-customer facing solutions has often been dismissed. Why is this? The risk is too high to thin slice? There’s no way to get customer feedback? There’s no way to deliver using iterative approaches?

    Over the last 16 months a group within a leading financial services client was brought to a cross roads. Their traditionally stable market was on the verge of being disrupted due to emerging innovation and competition from smaller, more nimble competitors. They knew to operate the same way would result in significant losses in market share over the next decade. To survive, they had to lead the innovation. Change was becoming the norm, and their focus shifted from being solely focused on final solutions, to also re-thinking how they got to these solutions.

    Enter lean & agile principles and practices. Initially dismissed because this client’s business model operated as the backbone of the institution. Much of the work they did was in facilitating payment origination and transaction settlement systems. Applying lean & agile required some significant tailoring.

    In this talk we will discuss this client’s journey, how they changed the entire culture within the organization to focus on survival through agility. We’ll discuss how common lean-agile principles and practices can be applied and tailored to support transforming legacy eco-systems with back-end facing solutions where the concept of a real life "customer" is quite foreign. We'll visit our experiences in encouraging the transparency that is synonymous with an agile approach and how that fostered better partnerships and trust across many groups. We’ll explore how a culture of learning has established early wins for the client and set them on a path towards leading innovation, agility and empowered being first to market.

  • Liked Tyler Motherwell
    keyboard_arrow_down

    Tyler Motherwell - Divide And Conquer

    40 mins
    Experience Report
    Intermediate

    Conway’s Law tells us that the products an organization produces will mirror the communication structures within themselves. Many organizations struggle to organize in a way that facilitates both agility and bringing quality products to market. However, this is a problem that exists, not just within IT, but across the entire enterprise. Imagine you’re the (somewhat mythical/revered) business. How do you organize yourselves in this brave new world? Many of the common patterns (systems, application/application layer) that we commonly apply in technology aren’t good fits.

    In this session, you will learn how to use a structured method to organize your most important resource (your people) around your most important goals. Additionally, you will learn about team types outside of your typical cross-functional team! We will use an actual industry case study to help illustrate usage, as well as give inspiration to how you might do the same in your organization

  • David Sabine
    David Sabine
    Scrum Trainer
    BERTEIG
    schedule 6 days ago
    Sold Out!
    60 mins
    Experience Report
    Advanced

    Products are not Projects — simple.

    A project is:

    "a set of interrelated tasks to be executed over a fixed period and within certain cost and other limitations."
    "What is a project? definition and meaning". BusinessDictionary.com. Retrieved 2016-04-19.

    Product development cannot be constrained to "certain cost" and products do not have a prescribed end date...so no "fixed period". So long as the organization finds innovative ways to meet market demands, the products they develop will evolve.

    So, why all the projects?

    I teach Scrum — it's a process framework that has been used to manage complex product development. Yet:

    • ~55% of the people in my classes are "Project Managers"
    • ~90% work daily in "project teams" (sic)
    • and ~0% are ready to let go of Project Charters!?

    Project charters in a complex problem domain create an illusion of safety, certainty, and confidence, but are wholly inappropriate in most organizations represented at this conference for one simple reason: the nature of our work is complex and therefore it is not possible to predict a "set of interrelated tasks to be executed over a fixed period and within certain cost and other limitations".

  • Liked Alistair McKinnell
    keyboard_arrow_down

    Alistair McKinnell - Don't Settle for Poor Names

    60 mins
    Talk
    Advanced

    I get frustrated with code that is sprinkled with poorly named classes, methods, and variables.

    Whenever I work on a team or coach a team, I put a lot of energy into choosing good names and sensitizing my teammates to the power of naming.

    I've noticed that developers spend most of their days reading code rather than writing code. I suspect you've noticed too. Creating understandable code is a high leverage activity for any team. And naming is where I start.

    The core of the session is an example that illustrates the process and power of choosing good names. The example comes from a recent project. There will be code.

    I will connect the example to specific techniques and patterns for choosing good names and share resources that you can use right away.

    My goal for this session is to sensitize you to the power of naming.

  • 60 mins
    Talk
    Intermediate

    In today’s fast paced world, we in the Agile community have gotten better at organizing and prioritizing work. We have learned how to focus on high value and eliminate waste in our processes. And yet so much of Agile these days is focused on how we move work from an idea to production while ignoring or undervaluing how to build high quality working software. Our focus is on how to hold retrospectives, collaborate with product owners, and hold daily standups but very little attention has been paid to how we write and test code. This puts your business at risk.

    Join Cheezy as he talks about how we often miss the target in our “Agile Implementations”. Instead, he will challenge us to focus on technical excellence as the true Path to Agility. His lightweight approach for teams to deliver software with Zero Defects strips most methodologies down to their bare essence. This allows teams to focus on what is really important - rapidly delivering working software to customers. If you’re ready to take the next step in your agile journey then you won’t want to miss this talk.

  • Liked Louise Heldoorn
    keyboard_arrow_down

    Louise Heldoorn - How Kanban Propelled our DevOps Team to New Heights

    Louise Heldoorn
    Louise Heldoorn
    Lead Release Engineer
    ADP
    schedule 2 weeks ago
    Sold Out!
    40 mins
    Experience Report
    Beginner

    Description/Summary
    Development Operations is a team that has requests from many sources, many of which have conflicting priorities. How do we move from being reactive, switching priorities, getting buried with stress of delivering on time with high quality to being proactive, innovative highly productive.

    In this session I will walk through the journey my team took to move from reactively treading water to becoming an extremely innovative highly efficient development operations team.

  • Liked Paul J. Heidema
    keyboard_arrow_down

    Paul J. Heidema - The Agile Coach Program: Scaling from 20 Teams to Over 60 Teams

    40 mins
    Experience Report
    Intermediate

    The number of agile teams that I support went from 20 (too many) to more than 70 (absurd) in a few months. What could I do? How could I help them?

    From this need came the Agile Coach Program that Paul created and facilitated at ADP with a small group of individuals - one was Iaroslav Torbin. These participants already support (or wanted to support) teams (be they using Scrum or Kanban) and the individuals around them. This is the story of that journey and the results.

    Feedback from the program:

    • "The agile coach program has been a valuable experience both personally and professionally. It was a fun, interactive and engaging."
    • "I really enjoyed being a part of this program. With its interactive and constructive parts."
  • Liked Paul J. Heidema
    keyboard_arrow_down

    Paul J. Heidema - Vital Behaviours of Successful Scrum Masters and How to Make Them Stick

    90 mins
    Workshop
    Intermediate

    Agile failure is most felt by Scrum Masters. Why do so many fail to properly support their teams? Why do so many fail to inspire meaningful change in the level of leadership? Why do so many fail to guide transformation in their organisations?

    In this workshop, we will harness the knowledge and experience of the participants!

    Influencer Book

    Why?
    Because everyone can contribute to the learning of the entire group. It will dynamic, full or energy, and joyful - woohoo!

    Who can benefit the most from the session and the power of harnessing the group?

    • Scrum Masters that are struggling to do this role well
    • Leaders that are not seeing the results needed for an effective Scrum team through a weak/unskilled Scrum Master
    • Agile coaches that are coaching Scrum Masters without meaningful or consistent results
    • Project managers trying to make the transition to becoming a successful Scrum Master

    This workshop will use concepts and the model from the book "Influencer"

    Prepare to work together to co-discover the Scrum Master vital behaviours!

    Many people are taking on the mantle of Scrum Masters across agile teams around the world. Unfortunately, many of them have come from more traditional work structures that don't develop effective Scrum Masters. There is a misconception about the purpose of a Scrum Master. Often the Scrum Master becomes the facilitator or the project manager. This has to stop. Effective leaders, agile coaches, and Scrum Masters take advantage of vital behaviours in supporting scrum masters or by building mastery within these behaviours.

    Influencer - the model

    During this workshop, participants will go through a series of exercises to identify the purpose of a Scrum Master, how we can measure success, identify potential vital behaviours, learn from others to determine the vital behaviours, and then create a sound influence strategy to enable effective Scrum Masters and the work that they do. This workshop will use concepts and the model from the book "Influencer" (by Joseph Grenny et all) which details the three (3) keys to a successful change initiative and uses the six (6) sources of influence.

    Prepare to work together to co-discover the Scrum Master vital behaviours!

  • Liked Mike Bowler
    keyboard_arrow_down

    Mike Bowler - Running with the Mob: Extreme collaboration with Mob Programming

    90 mins
    Workshop
    Intermediate

    Mob programming is collaboration taken to the extreme, eliciting the best from every member of the team. In this session, you will experience the dynamics of mob programming and learn how to use this technique successfully in your own environments.

    After mobbing with well over thirty teams, we've seen definite patterns emerge, that we'll discuss here.

  • Liked David Sabine
    keyboard_arrow_down

    David Sabine - Your Favourite "Agile" Tool Sucks!

    David Sabine
    David Sabine
    Scrum Trainer
    BERTEIG
    schedule 5 days ago
    Sold Out!
    40 mins
    Talk
    Intermediate

    • Ball Cap: Your Favourite Agile Tool SucksNote cards and stickies? Everybody scoffs at them!
    • Jira? Evil!
    • Trello? Sucks!
    • Pivotal, Rally, Blossom, Asana, Basecamp, Sprintly? Argh!

    The problem with every tool is actually simple: they solve for someone else's problems...not yours. Few aspects of the modern workplace receive as much attention and create as much controversy. Let's explore how "Agile Tools" impact our work.

  • Liked Corey Stewart
    keyboard_arrow_down

    Corey Stewart - How the CBC Management Team stopped worrying and learned to love agile

    Corey Stewart
    Corey Stewart
    Agile Coach
    CBC-Radio Canada
    schedule 1 week ago
    Sold Out!
    40 mins
    Talk
    Intermediate

    Volumes have been written about what an agile organization looks like, but less has been said about what managers do to build and sustain an organization transitioning to agile. This talk will explain what the CBC’s management team is discovering during our agile transformation, the many forks in the road that we had to navigate (e.g.: organizational structure, cultural change and building trust with our stakeholders), and how the job of a manager evolved as the organization we lead changed. You’ll hear about the CBC’s ongoing four year journey and how we continue to collaborate, learn and improve.

    About CBC/Radio-Canada

    CBC/Radio-Canada is Canada's national public broadcaster and one of its largest cultural institutions. CBC Digital is the country’s biggest digital startup, taking on the challenges of innovating how media is made, sent and received. We are trying new things. We are growing. As an entity of our own. As a voice for our country. As a team.

  • Liked Matt Dominici
    keyboard_arrow_down

    Matt Dominici - Breaking Scrum: A Tale Of Two Scrum Masters

    60 mins
    Experience Report
    Beginner

    Join Jon & Matt on a journey of enlightenment and witness their transformation from "Command and Control" to "Servant Leadership". Through their journey, discover the tips and tricks that helped two budding tech workers discover, embrace and live the Agile values. Discover common pitfalls and the resources that are available to help you overcome them.

    As many in our industry are learning, becoming and living as a Scrum Master is no easy task. Scrum Masters come from many different disciplines - sometimes from outside of the technology space all together! Becoming a Scrum Master requires self-guided learning, coaching, experience, and, (most importantly) failure.

    Jon & Matt will walk through their own journeys and make stops along the way to discuss the failures they experienced as well as the resources and materials they used to continue on their journey. They will also touch on what's next: Potential career paths for scrum masters, and how existing Scrum Masters can continue their own agile journeys

  • Liked Ron Ijack
    keyboard_arrow_down

    Ron Ijack - Why we got rid of SCRUM to become agile again

    Ron Ijack
    Ron Ijack
    VP Technology
    Upstream Works Software
    schedule 2 weeks ago
    Sold Out!
    40 mins
    Experience Report
    Intermediate

    Agile is not about doing scrum, kanban, lean or any other flavour of the process. An organization cannot be “doing” agile, they must “be” agile. They must believe in and understand the agile principles. After going through a successful agile transformation and running scrum for 3 years we realized that it’s just not working for us anymore. The team was suffering from scrum fatigue. It felt like there was a sprint planning, stand up or retrospective meeting happening all the time. We decided to take a hard look at how we were working and turn it on its head. We looked at all the different agile options such as scrum, kanban, lean, xp, etc and decided to take the best part from all of these instead of sticking with one approach. This session will take you through our journey and share what worked for us that could also work in your organization.