OKALOA FLOW LAB
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 conversation? 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 Okaloa Flowlab.
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.
Outline/structure of the Session
Agenda - address all islands of agility (KANBAN, LEAN, SAFe, SCRUM, LeSS, DA) with te following steps:
A) Efficiency I - OODA Loop
B) Efficiency II - PDCA loop
The goal with Okaloa Flowlab is to let participants discover a new way of thinking integrating science and experience. The aim is to provide a learning tool that allows participants to learn new techniques to handle change and adaptation: reflective observations (OODA) – after the 1st round participants will be asked to make observations in order to analysis what impedes flow active experimentation (PDCA) – based on these observations, participants will then be asked to define experiments and hypotheses
CEO-VP-CIO-PM-Portfolio mgr- Program MGR - Director -
No prerequisites of any sort