Let's face it, when organizations want to "go Agile", they really want help solving a problem they can't quite put their finger on. Some of the time they may buy a tool and call themselves Agile. Other times, they'll implement a few practices but not much more. There are no shortage of tools, methods and techniques for installing Agile and there are an equal number of failure stories. At the end of day, Agile is simply a trigger for an organizational change.

In this session you'll learn 3 techniques that will help you navigate through complex change by working on a real problem with your peers. After all, a consultant or coach is only going to take you so far!

 
6 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

3 Innovative Tools for Architecting Change (20 minutes)

  • Change Canvases: how to create alignment for organizational change
  • Sphere of Influence: how to visualize where the support and resistance for your change is
  • Blast Radius: Who's affected, what they need to change, expected intended and un-intended consequences

Audtiion (10 minutes)

The audience members will be given the opportunity to present a problem they're trying to solve with respect to an organizational change, typically an Agile Transformation.  The fallback plan is to break the audience into groups and give them 15 minutes to create a scenario for another group to solve.  The fallback plan to that is to prepare scenarios in advance, just in case!

Workshop Component 45 minutes

Each group will take 30 minutes to use the tools they learned and create their solution to the problem.  The remaining 15 minutes will be for each group to present their solution and elicit feedback from other groups. 

Closing (15 minutes)

This section will be for people to ask the facilitators questions and hear stories about how others are using these ideas.

 

Learning Outcome

  • why sense-making tools are better for managing organizational change
  • how visualizing change helps align people within the organization

Target Audience

Managers, Agile Coaches, Change Managers, HR

schedule Submitted 2 years ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • Liked Ellen Grove
    keyboard_arrow_down

    Ellen Grove - Everything Is Better When We Stick Together: Building Team Working Agreements

    60 mins
    Workshop
    Beginner

    Whether a team is brand-new or seasoned veterans at working together, explicitly defining and/or refining a team working agreement will help the team to align on how they will work together effectively to meet their common goal. In this fast-paced hands-on session, participants will go through the process of building a team working agreement using LEGO Serious Play (LSP).

    Creating a team working agreement helps team members set the stage for effective communication and high performance by making assumptions about ‘what really matters to us’ and ‘how we will work together?’ explicit and negotiable.  Great working agreements address some difficult topics - what values do we share? how do we want to deal with conflict when it comes up? how will we handle problems within the team? - which are often challenging to discuss openly and honestly, especially when a team is first assembled.  This session will show you how to use LEGO Serious Play to encourage a frank and fearless discussion in order to kickstart these discussions so that a team can quickly create a powerful set of simple guiding principles for working together.  Participants will learn about the importance of team working agreements in creating team cohesion and common understanding of shared values and operational guidelines, and experience hands-on how to use the LEGO Serious Play cycle of build-share-reflect to have a participatory discussion to identify shared values and build a set of simple guiding principles.

     

  • Liked Jason Little
    keyboard_arrow_down

    Jason Little - Creating Alignment for Agile Change

    60 mins
    Talk
    Intermediate

    Sometimes people in organizations feel as though Agile has been pushed on them. They end up going through the motions, without any real sense of ownership of what they are doing. Instead of actually implementing meaningful changes, organizations end up doing "Agile in name only" by slapping Agile labels on existing processes. Then Agile is blamed for "not working". This isn't an Agile problem. It's an alignment and ownership problem. In this session, through theory and multiple real-world case studies, you'll learn how to co-create change by involving the people affected by the change in the design of the change.

     

  • Liked Andrew Annett
    keyboard_arrow_down

    Andrew Annett - Changing the Language of Change

    Andrew Annett
    Andrew Annett
    Agile Catalyst
    Leanintuit
    schedule 2 years ago
    Sold Out!
    45 mins
    Workshop
    Intermediate

    We swim in a sea of language but seem to be drowning in misunderstanding. Nowhere is this more apparent than in the efforts we make to change ways of organizing work in organizations.

    Making common meaning of the language we use when working together takes conscious effort but we typically go about it unconsciously. In this session we'll examine common patterns of unintended consequences that stem simply from the language we use to describe changes to the way we work.

    You'll leave with a new model for thinking about language and using it to better effect. We'll discuss and practice the use of metaphor, mindset and specific practices to create shared understand in and between teams. 

  • Liked Caroline Sauve
    keyboard_arrow_down

    Caroline Sauve - Agile Project Inception - Getting Aligned and Making Commitments

    90 mins
    Workshop
    Intermediate

    Sponsors of development projects generally want to know what they are going to get, when they are going to get it, and how much it will cost *before* they make the commitment to "purchase". In many businesses, while the software development process may be Agile, the reality is that other functions in the business - Documentation, Training, Marketing, Sales, Finance, Business Planning - need to know what's coming well in advance. When starting an Agile project these stakeholder needs must be met if the team is to get off on the right track, and be allowed to proceed without undue outside interference.

    Centred on the use of the "Inception Deck", participants will learn techniques to kick off an Agile project that will help them to:

    1. Create a shared understanding around the project’s goals.

    2. Identify and understand risk on the project.

    3. Build a high level plan for the project and setting the ground rules for change on the project.

    4. Get agreement on a set of “project bounds” for scope/content, schedule/delivery, and resources/cost, to allow the project team to proceed independently and make their own decisions as the project progresses.

    This session co-presented and pair-facilitated by Bill Bourne and Caroline Sauve

  • Liked Paul Carvalho
    keyboard_arrow_down

    Paul Carvalho - Software Testing and QA Cheat Sheet for Agile Coaches

    90 mins
    Workshop
    Beginner

    Ever find yourself coaching a team to be more agile and catch yourself ignoring the testers? Why do you do that? Because you don't know the lingo? Unsure of what advice to offer? Don't know any good Testing or QA models or approaches that specifically speak to that development role?

    You're in luck! Paul is here to give you a crash course in models, methods, jargon and techniques specific to Software Testing and QA to help you enrich your Agile Coaching practice. Come prepared to interact and learn as you build a cheat sheet that will help guide you when working with Testers who don't know where to start with the transition to Agile.

     

  • Liked Mark Levison
    keyboard_arrow_down

    Mark Levison - High Performance Teams Game

    90 mins
    Workshop
    Intermediate

    As a Coach and a Team Member, I sometimes come across teams that don't seem to be able to achieve high performance, and the reasons why aren't apparent. This can be frustrating for everyone when this happens, so I wanted to explore this deeper and understand the science of what happens inside Agile/Scrum Teams.


    Some of the leading research[1] suggests that a key requirement for high performance teams is Cohesion. Cohesion is a measure of the strengths of the relationships between individual team members.


    In this session we will use this research to discover:

    • Simple communication patterns we can monitor to spot the health of the team.
    • Simple tools we can use to measure and track those patterns.
    • What effect the location of the Watercooler has? What effect Lunch Tables play?
    • Can Cohesive Teams get you into trouble? .....
    • The importance of Dissent and Diversity within teams.
    • Bonuses - The negative effects of individual bonuses are well understood by the Agile Community. However we’re left with the question - are there good bonuses?

    [1] Sandy Pentland - The New Science of Building Great Teams - http://hbr.org/2012/04/the-new-science-of-building-great-teams Ben Waber - People Analytics: http://www.amazon.ca/People-Analytics-Technology-Transform-Business/dp/0133158314

    The core of the session will a be a game that we play successive round of. After each round I will reveal the factors that affected play in that round. Perhaps making easier to decide what to do in the next round.

    In addition to the game the details of the research will be part of the session handout so attendees can focus on the play and not the details.

  • Liked Dave Rooney
    keyboard_arrow_down

    Dave Rooney - Effective Software Delivery - Agility Without the Dogma

    60 mins
    Workshop
    Beginner
    This session will explore what "effective" means when it comes to delivering software, regardless of the development method used. The audience will participate by sharing their own experiences and insights in order to examine the similarities and differences between business domains.
     
    The goal is to help you to identify what, in your particular context, will smooth out the rough road to a shipped product that meets the needs of the people who consume it, in an indefinitely sustainable manner.
     
  • Liked Annette Lee
    keyboard_arrow_down

    Annette Lee - A Case Study: From Waterfall to Scaled Agile

    60 mins
    Talk
    Beginner

    At the end of 2012 engineering at Wind River began its agile journey. We started with a consultant and 2 pilot projects. By March 2013, we began to move all of our projects to Agile. That's 100s of people and many sites around the world all trying to implement agile and scrum simultaneously! Mayhem ensued. This is a story of how engineering at Wind River survived the chaos and where we are today. Drawing from this experience, there are lessons learned and learning to share.

  • Liked Angel Diaz-Maroto Alvarez
    keyboard_arrow_down

    Angel Diaz-Maroto Alvarez - Expanding an Agile Culture in organisations with Design thinking

    Angel Diaz-Maroto Alvarez
    Angel Diaz-Maroto Alvarez
    Agile coach
    Agilar
    schedule 2 years ago
    Sold Out!
    60 mins
    Workshop
    Intermediate

    Abstract:
    Design Thinking refers to the methods and processes to investigate complex problems in highly uncertain systems. This workshop is about how to use this iterative process of observation, ideation and implementation to better understand organisation's culture and create reasons for people in the organisation to embrace Agile.

    Summary:
    This workshop is about how to use a design thinking process an techniques to better understand organisation's culture and minimize resistance to change in the creation of an Agile culture. The strategy is to combine empathy for the context, creativity in the generation of insights and solutions, and rationality to analyze and fit solutions to the context. This solutions are aimed to create reasons for people in the organisation to embrace Agile. 
    You'll also learn some useful design thinking techniques that you can use in your retrospectives!! 

    Description:
    Design Thinking refers to the methods and processes to investigate complex problems in highly uncertain systems, acquiring information, analysing knowledge, and positing solutions. This workshop is about the usage of this process to better understand organisation's culture and minimise resistance to change in the creation of an Agile culture. The strategy is to combine empathy for the context, creativity in the generation of insights and solutions, and rationality to analyse and fit solutions to the context. This solutions are aimed to create reasons for people in the organisation to embrace Agile.
    This iterative process of observation, ideation and implementation can be integrated within your retrospectives and also applied outside IT to create a continuous improvement engine for organisational culture in organisations.     




  • Liked Andrew Annett
    keyboard_arrow_down

    Andrew Annett - Are We There Yet? Painting Signposts for an Agile Journey.

    Andrew Annett
    Andrew Annett
    Agile Catalyst
    Leanintuit
    schedule 2 years ago
    Sold Out!
    60 mins
    Workshop
    Intermediate

    Adopting agile practices is complex - often we only understand where we are by looking back. Yet many involved in and observing the process want to know how teams and organizations are progressing.This session will explore techniques for mapping the journey, exposing directional options and customising the route according to where we find ourselves.

    The goal of this session is to enable us to understand and clearly explain where we are with respect to team development, how we got there and where we'll head to next.

    The tools we'll discuss will move towards building a GPS for our practice adoption travels.

  • Liked Mike Edwards
    keyboard_arrow_down

    Mike Edwards - Shifting value into high gear

    Mike Edwards
    Mike Edwards
    Agile Coach
    Leanintuit
    schedule 2 years ago
    Sold Out!
    60 mins
    Talk
    Intermediate

    How do you define “value”? What does it take for a business to shift “Value” into high gear and create experiences leaving your customer saying "Wow"? Why does the software industry struggle to even meet expectations?  If you’re struggling to create valuable experiences for your customer then this session is for you.

    Every team I work with talks about delivering valuable features, and yet many of their customers are dissatisfied. When I question how they define value I might get text book answers about ROI, sales, efficiencies or other quantifiable measures. Although these are important measures, I don’t believe “value” can be defined by anything you can quantify. If that’s true then how do we get from "Valuable" to "Wow" without going broke?

    We will start by examining two similar customer experiences. Both experiences are valuable, one met expectations but the other left the customer going “Wow!”. Regardless of what business your in, with some awareness it’s possible to start creating more “Wow!” moments for your customers. 

  • Liked Omar Bermudez
    keyboard_arrow_down

    Omar Bermudez - Teams & Responsibility. How can we help them grow?

    60 mins
    Workshop
    Beginner

    Using The Responsibility Process™ from Dr. C. Avery to build stronger and responsible teams. This process, derived from field studies, shows how all people mentally process thoughts about avoiding or taking responsibility. More of one year ago I started to study this model and I am part of the program The leadership Gift™ (Dr. C. Avery's program). This program allows me to grow as a person and as professional every single day. It also gave me the opportunity to help my teams to shine in a natural way. In this presentation, I will do a presentation of the model and share my experience using it with teams. To help people to understand it and use it, the session will have games and pitfails based in my experience with it

  • Liked Dave Rooney
    keyboard_arrow_down

    Dave Rooney - Digging to the Roots

    60 mins
    Workshop
    Beginner

    Whether it's a minor typo on a page, a major failure causing a severe outage of a system or anything in between, the software industry is fertile ground for examining problems and their causes. From the problems that plagued HealthCare.gov to defects that allowed some lucky people to purchase airline tickets for almost nothing from United airlines, we hear a constant stream of issues with software systems.

    With our society becoming increasingly dependent on software, we need to "up our game" with respect to tracking down problems with they happen, ensuring that defects are caught before entering the wild, and are prevented from occurring in the first place.

    Root Cause Analysis is a process that enables this form of continuous improvement and uses techniques borrowed from other engineering disciplines. The aviation industry, for example, constantly seeks to improve due to the dire consequences of any failures in that domain.

    This interactive workshop will explain when and how to use Root Cause Analysis (RCA) to investigate problems and determine actions that will ensure that those problems can never happen again. Using real world examples the attendees will explore simple, lightweight RCA practices as well as a more involved example using fault tree analysis.

  • Liked Dave Dame
    keyboard_arrow_down

    Dave Dame - Implementing Agile Development in an Enterprise Environment

    45 mins
    Talk
    Intermediate

    Implementing agile in a large enterprise organization requires flexibility to implement a strategy that embraces the benefits of agile while providing the enterprise reporting needed to co-ordinate multiple development team’s working toward a single common release.  If this is not complex enough you still have to accommodate an enterprise legacy product.  I will be giving a case study on legacy products, integrating shared specialized resources (performance, UX), and balancing resourcing between new feature development and maintenance/escalation work. Over the years we implemented a Disciplined Agile Delivery (DAD) process that incorporates a hybrid of Scrum & Kanban frameworks contained in a serial governed ‘phased’ process.