Agility is a mindset. It is not a set of practices that can be installed. But how do you get out of the practices trap, especially when you have to mobilize not just software development and IT teams but the entire organization towards business agility where value is created through meaningful work? How do you engage business teams, users and customers? How do you enable higher levels of collaboration, not just within teams but also across teams? In other words, how do you get individuals, teams and even the entire organization into a flow state where everybody is doing the right thing at the right time by having the right conversations? Rational explanations and models of agility will only go so far. To be truly effective, the agile mindset needs to be experienced, which is exactly the purpose of the new and thought provoking Okaloa Flowlab simulation by Patrick Steyaert, one of agile's better scientific mind.

Through simulating a conventional work environment that reflects a mechanistic mindset characterized by a focus on resource efficiency, command and control and specialist workers, participants experience which roadblocks need to be overcome. As the team is taking its first baby steps into agile, they will experiment (in 2 or 3 rounds) with policies and practices (e.g. pull of work, cadences, limiting WIP) that enable collaboration, get the team into flow, and allow an agile mindset to emerge. Weaved into the simulations they will discover the fundamental difference between resource efficiency and flow efficiency.

Participants will step into the simulator after a brief explanation of the rules.

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

Outline/structure of the Session

This engaging simulation will leave everyone breathless!

Agenda - address and compare all islands of agility (KANBAN, LEAN, SAFe, SCRUM, LeSS, DA) with the following steps:

A) Efficiency I - OODA Loop

B) Efficiency II - PDCA loop

C) CADENCES

D) FLOW

Learning Outcome

The goal with Okaloa Flowlab is to let participants discover a new agile way of thinking by integrating experience first and science afterwards. Too many agile practices are based on intuition and we must learn to tackle work issues thru the rational side of our brain as well. The aim is therefore to provide a learning tool that allows participants to learn new techniques to handle change and adaptation to attain agility.

It will be done in two steps:

- At first, the participants will be asked to make observations using the OODA loop in order to find what impedes flow and an optimal perspective on agility.

- Next, after some reflective observations (OODA loop), the participants will immerse themselves in active experimentation with the PDCA loop and formulate and test hypothesis for the remainder of the simulation. Only an expert can facilitate this very rewarding simulation.

Participants will live agility and discover the Agile Manifesto anew. A few popular agile myths will surely be challenged and even destroyed!

Target Audience

CEO-VP-CIO-PM-Portfolio mgr- Program MGR - Director -

Prerequisite

No prerequisites of any sort

schedule Submitted 4 months ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • Liked thomasjeffrey
    keyboard_arrow_down

    thomasjeffrey - Scaling Agile without the scaling framework

    thomasjeffrey
    thomasjeffrey
    President
    Agile By Design
    schedule 3 months ago
    Sold Out!
    60 Mins
    Talk
    Advanced

    Increasingly Agile adoption has focused on how to operate larger enterprises with agility, and run larger and larger initiatives, at scale.

    In many cases, organizations have turned to explicit agile scaling frameworks to address their needs to coordinate increasingly larger efforts to deliver value in a way of that does not sacrifice feedback and self organization . Often these frameworks attempt to address the complexity that comes with large scale by adding extra process and procedure. Prescriptive advice is prescribed in the form of additional roles, stages, gates, and methods. This approach to scaling bears more than a little similarity to the heavy weight methods of the past, but in this case merging agile terminology with much of the same framework bloat and bureaucracy we have seen in the past.

    As a a result adoptees struggle to understand how to fit these frameworks to their context, and seasoned coaches struggle to wrestle out the good bits.

    During this session I will discuss a different approach to scaling agile, one that places an emphasis on both mindset and practice. I'll pay particular attention to the topic of leadership, organizational design, and the role management has to play in designing a system of work that allows larger efforts to work with an agile mindset without being forced into a one size fits all process framework.

    A key part of the discussion will be to showcase how core agile methods and techniques can be extended and expanded to successfully manage coordinated agile deployments that range from hundreds to thousands of FTEs. I'll present these techniques by using real examples of agile deployments I have been a part of during my work with ScotiaBank's agile journey.

    Key Scaling Practices covered will include:
    - The design components required to structure your organization based on demand
    - How to continuously de-scale your organization
    - "Get Out Of the Boardroom" style governance and leadership
    - Operational cadences and Impediment Escalation Flow
    - Managing the flow of value at the Business Technology Asset level
    - Moving the conversation from stories to domains
    - Streamlining finance and budgeting to align to the agile mindset

    I hope to illustrate ways that both management and knowledge workers can select techniques that allow them to scale agile as needed to support ever larger initiatives without succumbing to a one size fits all framework that does not adapt constant change.

  • Liked Taimur Mohammad
    keyboard_arrow_down

    Taimur Mohammad - Delighting the Customer at the First Point of Interaction

    Taimur Mohammad
    Taimur Mohammad
    Coach
    Agile By Design
    schedule 3 months ago
    Sold Out!
    40 Mins
    Experience Report
    Intermediate

    The first interaction with a prospective customer often makes or breaks the sale. In today’s age of instantly obtaining products and application at the touch of a button (e.g. mobile apps), the last thing that customers expect is a long, complicated process. Truly delighting the customer requires moving towards instant gratification. How do you re-organize traditionally separate business and technology groups so that the focus is on delighting the customer?

    A group within a leading financial institution identified this as a goal and looked at lean-agile principles and practices to rapidly iterate on delighting the customer and bringing business & technology processes seamlessly together. While delivery was set up using what we’ve come to as good lean-agile principles and practices, how the product backlog was managed provided the rapid feedback, innovation and pivot/pursuits required to truly delight the customers.

    In building the product backlog a number of practices were introduced to make it dynamic and ever evolving.

    • Kanban connected the customer to the product backlog which connected to the delivery engine
    • Product metrics and cost of delay were used to create hypotheses to prioritize MVPs
    • Rapid feedback through various customer and proxy customer interactions were leveraged to feed the customer backlog
    • Monthly releases ensured a constant flow of new features to enhance the customer’s experience
    • Story decomposition ensured the customers feedback was being directly communicated with the delivery team

    The result? While the client is still on its journey the results have been overwhelmingly positive. Key metrics indicate greater customer satisfactions, increased speed to completion and simplified internal processes.

    In this talk we’ll discuss how we’ve taken various product management related practices and stitched them together to connect the customer to the delivery engine. We’ll provide practical examples that we’ve seen work in our experience and engage in a discussion with the group to connect their questions to our examples.

  • Liked Paul J. Heidema
    keyboard_arrow_down

    Paul J. Heidema / Iaroslav Torbin - 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 / Sean Deschamps - 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

  • Liked Sam Tabbara
    keyboard_arrow_down

    Sam Tabbara - How to transform culture in large enterprises

    Sam Tabbara
    Sam Tabbara
    Senior Consultant
    Agile By Design
    schedule 3 months ago
    Sold Out!
    40 Mins
    Experience Report
    Intermediate

    Most important factors in any Agile transformation are the ability to react and change quickly, which are most often associated with startups than large enterprises. To really win and transform an organization there are core elements that need to be mastered and executed at the culture level. We will cover these elements and provide you real use cases where transformations both succeeded and failed to meet their potential to prove the relationship.

  • Liked Paul J. Heidema
    keyboard_arrow_down

    Paul J. Heidema / Iaroslav Torbin - 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 Sam Tabbara
    keyboard_arrow_down

    Sam Tabbara - How to truly transform large enterprises

    Sam Tabbara
    Sam Tabbara
    Agile Practitioner
    Bell
    schedule 4 months ago
    Sold Out!
    40 Mins
    Talk
    Intermediate

    Most important factors in any Agile transformation is the ability to react and change quickly, which are most often associated with startups than large enterprises. To really win and transform an organization there are core elements that need to be mastered and executed at the culture level. We will cover these elements and provide you real use cases where transformations both succeeded and failed to meet their potential to prove the relationship

  • Liked Abeer Rahman
    keyboard_arrow_down

    Abeer Rahman / Fawzy Manaa - A Techie's Guide to Improving Operations: Inspirations from Public Transit

    60 Mins
    Experience Report
    Beginner

    A Techie's Guide to Improving Operations: Inspirations from Public Transit

    There are lots of common challenges between technical operations and public transit operations. Public transit is a staple system in any city's infrastructure that helps to flourish the economy of the city. They have tried-and-tested runbook-type systems in place to deal with standard operations, and how to deal in times of incidents. Sounds pretty much like what technical operations teams have to deal with on a regular basis, right?

    In this talk, we present some parallels between operating & running a public transit system that can be implemented at operations teams at software organizations. We will look at technical as well as simple organizational-behvaviour aspects that can be rolled out to increase operational efficiency at organizations, ultimately benefiting for global optimizations - such as minimize downtime, improve systems architecture & infrastructure.

    Why is improving Ops important and often left out of agile enablement?

    The world of infrastructure & operations is usually not looked at when enabling agile teams from a product management perspective. Most agile enablement process don't look at Ops early. All too often, we see the "throw over the wall, run it & figure it out" behaviour in organizations. The good news is... this behaviour is changing, slowly, but steadily, thanks to the DevOps movement.

    There are lots of good literature out there on increasing operational excellence in technical organizations, however, in such a fast world, are leaders getting time to actually learn & reflect on tactics to enable themselves? Can there be easy takeaways that teams can implement starting tomorrow?

    Yes they can!

    By carefully seeing how a public transit system, such as the TTC, operates, there are lots of areas we can incrementally improve in Ops at our organizations.

  • Liked Tyler Motherwell
    keyboard_arrow_down

    Tyler Motherwell - Art of Flow: Managing and Linking Teams in a Creative Environment

    40 Mins
    Experience Report
    Intermediate

    Co-ordinating and managing dependencies is a challenge that impacts every team at some point. Most struggle when encountering this situation, especially in scenarios when making the dependent skillsets part of the team is impractical, such as large variability in demand. Additionally, such skillsets are frequently scarce and difficult to teach others.

    In this session, you will learn how we were able to successfully link together 5+ teams (with direct upstream-downstream relationships) in a marketing/creative context, including both behavioural and visual management components. Additionally, we will review several other potential linking mechanisms and how you might apply them in your organization

  • Liked Adeeb Dhanani
    keyboard_arrow_down

    Adeeb Dhanani - Maps, Models, & Specs... how they connect

    Adeeb Dhanani
    Adeeb Dhanani
    Agile Coach
    Agile By Design
    schedule 3 months ago
    Sold Out!
    60 Mins
    Experience Report
    Advanced

    Connecting Story Mapping, Domain Modelling, & Spec by Example using a scenario based approach.

    The Story Map was used to illustrate the system sequence of events. The Domain Model was used as a common glossary of interrelated concepts normalizing language. Spec by Example illustrated the Scenario across the Story Map events, using common language of the domains, with the variables of the scenario

  • Liked Junbin Huang
    keyboard_arrow_down

    Junbin Huang / Glen Farrell - Agility in Support Organizations

    40 Mins
    Experience Report
    Beginner

    A co-facilitated session from the perspective of coaches working with a multi-tier support organization. A closer look at the adoption of agile within a chaotic environment from deciding the methodology, the customization to fit the organization and tools selection.