Written by

Many times we (as Agile coaches) quickly discover that the Agile frameworks used in our client organizations are deeply incompatible with…

  • The nature of their work 
  • The flow of their work
  • Their overall organizational context
  • And the list goes on!

This is especially challenging when the organization has chosen to quickly scale a single framework with brute force while using a one-size-fits-all approach without considering systemic root causes to their performance issues. In my experience, this often happens when management aims to address symptoms that manifest at their flight level for immediate pain relief and inadvertently neglect to probe more deeply into systemic causes. 

As a result, the teams doing the work struggle through these mandated ways of working that ultimately lead to more problems than they solve! 

This blog post is about my experience when Kanban was a better fit than Scrum, the SAFe caused more problems than it solved, and the organization was afraid to let go and let teams explore what Agile Ways-of-Working works best for them. 

I’ll be sharing pieces of the journey that led to a 300% improvement in Lead Time along with three key questions that can help keep you on track if you find yourself in a similar spot, which are as follows:

  • #1: What problem were you brought in to solve? And what Agile good practices could help?
  • #2: Is the problem actually the problem? Or is it a symptom of something else?
  • #3: If it is a problem, are the current Ways-of-Working helping or hindering? What does the nature and flow of work tell you? What about the organizational context?

This blog post is structured according to those questions where I share the success story that came from carefully answering each one. Hopefully the article will be helpful resources if you find yourself navigating through the same murky waters!

#1: What problem were you brought in to solve? And what Agile good practices could help?

Like most Agile Coaches, I started by seeking to understand the measurable problem I was brought in to solve. And because the client wanted quick results, I also looked for what Agile good practices might help to secure some early wins.

In the specific experience I’m drawing upon for this blog post, this was, “We need to improve this department’s predictability to at least 80%”. 

The landscape

The teams were using Scrum in a SAFe set-up based on a decision 5 years ago to centralize everything Agile under one big SAFe roof. Managers and stakeholders seemed to like using PI planning as a really large batch transfer that happened every 3 months. The outcome amounted to quarterly Gantt charts from each team detailing at a User-Story level how they intended to work on the massive influx of work items the business pushed onto them to complete. Although stakeholders actively invited the Product Managers and Product Owners “to say no” to taking on more work then they could handle, during my interviews I learned that the unspoken cultural norms made it very unsafe to do so. 

What the data showed

Team interviews and high-level value stream maps indicated that, like most organizations, the teams were flooded with work due to a push-based system, features were bundled into projects creating very large batches, and there was a lack of prioritization due to minimal program or even backlog management. The result was a push-based system that was “going through the motions” of Lean Agile but not experiencing the benefits.

Although Scrum is a pull-based system, it wasn’t being used in that way. To get the system heading back into the right “pull-based” direction, I recommended we start with some known good practices for balancing capacity with demand and optimizing flow, such as unbundling features from projects to work in smaller batches, practicing regular backlog refinement, implementing clear definitions of ready and done, and implementing some good program management practices that include prioritization. 

I also recommended that we work on creating T-Shaped team members so work wouldn’t grind to a halt if people were sick, on holiday, or chose to leave the team.

T-shape that describes how to form teams consisting of members with expert knowledge together with members with good enough knowledge of the issue.
T-shape that describes how to form teams consisting of members with expert knowledge together with members with good enough knowledge of the issue.

What I did not expect

Although the Agile Coach and Product leadership team agreed with my assessment and recommendations, which I expected, the team-of-teams did not! They were firm on their stance that adopting such practices would not address the root cause to their pain points. Moreover, they disagreed with management’s assessment that they have a predictability problem. 

As a coach, this was interesting territory. I was brought into drive change in a team that believes no change is needed and doesn’t agree with the measures used to gauge their performance. 

After a few honest discussions with the team, I found myself asking the following question:

#2: Is the stated problem actually the problem? Or is it a symptom of something else?

(more…)
Written by

Av Jenny Jernberg & Sofia Hedlund

För dig som upplever att:

  • din organisation har utmaningar att säkerställa rätt beslut och prioriteringar för alla samlade produkter och team (helhetsbilden)
  • din organisation har svårt att se om affärskrav faktiskt kan realiseras
  • det är svårt att få till en ekonomistyrning där produkten hamnar i fokus
  • ni har svårigheter att få till ett rullande strategiskt planeringsarbete
  • er förflyttning från projektorganisation till produktorganisation har stannat av.

Om du känner igen dig, vill du nog fortsätta läsa hela caset där ATG delar sin resa mot att kunna möta upp omvärldens förändrade krav. Här har en mer effektiv och tydligare produktstyrning med produkter, affärsutveckling och team i fokus skapat förutsättningar för ännu högre konkurrensförmåga att erbjuda världens bästa spelupplevelse på en konkurrensutsatt spelmarknad.

Inledning

Den här resan började egentligen för flera år sedan. Många nuvarande och tidigare medarbetares insatser och engagemang har varit avgörande för att ge ATG rätt möjligheter och förutsättningar att vara där man är idag. Den här populärvetenskapliga fallstudien (i bemärkelsen att på ett lättsamt och förenklat sätt beskriva medarbetares upplevelser av förändringsarbetet) avser att beskriva vilka hinder, strategier, tillvägagångssätt, nya strukturer, lärdomar, framgångsfaktorer och effekter man har önskat samt uppnått.


ATG har vuxit under flera år i både affärsrelaterade produkter och kanaler, vilket skapat större grad av komplexitet internt i beroenden och koordinering. Detta har upplevts som hinder för att göra en större förflyttning. Det fanns tidigt en önskan och strävan att ta nästa steg till en effektivare och tydligare
produktstyrning som skulle bidra till ATG:s vision och mission och man ville göra det med en strategi som grundade sig i agila arbetsmetoder. Produkterna och affärsutvecklingsprocessen utgör kärnan i ATG:s konkurrenskraft som måste fortsätta förbättras för att bibehålla konkurrensförmågan. Omvärlden förändras allt snabbare. Kunder, partners, och myndigheter skapar både nya krav och affärsmöjligheter vilket skyndsamt behöver bemötas.


De nya strukturer som vuxit fram det senaste året har skapat en stabil grund som redan har satts på prov i hur man kan hantera förändringar tvärs hela organisationen på ett mycket mer effektivt sätt. Avsikten är att beskriva hur ATG har byggt en förmåga genom en styrmodell för att kunna hantera och ge stöd till förändringar på ett strukturerat sätt. Förut kunde ett nytt krav eller initiativ som krävde snabb prioritering inte ge oss samma förståelse för hur det slår på helheten, så som vi försöker få kontroll på idag. Vilket också kommer underlätta för oss att fatta rätt grundade beslut på rätt plats.

Strategi, tillvägagångssätt

För att uppnå målen om en effektivare och tydligare produktstyrning användes en strategi och tillvägagångssätt som varit grundad i enkelhet och pragmatik. Fokus har legat långt bort från verktyg och ramverk, snarare i en framväxande strategi med stöd i egenformulerade agila principer som legat
i linje med ATG:s manifest och företagskultur. Syftet har hela tiden varit att förenkla komplexa problem till hanterbara delar som en kärngruppering sedan arbetat med i kortare cykler. Kärngrupperingen, en tvärfunktionell konstellation (som vi här kallar programgruppen) av chefer med tydligt mandat och insikter i olika nödvändiga perspektiv i den kommersiella affären, ekonomiska, IT-utveckling, har gemensamt utforskat och upptäckt behov i ett kontinuerligt lärande med stöd av en Agil Enterprise coach.

En helt avgörande faktor har varit att aktivt sponsorskap i ATG:s ledningsgrupp. Under en intensiv inledande period arbetade programgruppen med små hanterbara delar som på veckobasis förde en dialog tillsammans med CFO, CCO och CIO för att få stöd i ramar och riktning. Parallellt testades de prototyper man arbetade fram genom att involvera nödvändiga kompetenser och perspektiv vilket också gav en mer proaktiv förändringshantering. Det minimerade riskerna att fatta fel beslut, missa nödvändiga perspektiv och byggde löpande ett större förtroende i organisationen.

Strategin och tillvägagångssättet har varit att mötas i perspektiven utan att förändra organisationen, vilket också minimerade en mer komplex förändringsledning. Det blev viktigare att tillämpa befintliga forum och redan etablerade hållpunkter i årshjul där agendan skruvades om, nya hypoteser och prototyper ersatte befintliga arbets-/tillvägagångssätt vilket gjorde att förändringarna blev successiva och lättare kunde justeras på vägen.

Vilka upplevda hinder och problem hade ATG?

ATG hade under flera år vuxit i både affärsrelaterade produkter och kanaler för att möta kundernas efterfrågan och hade snabbt utvecklats till ett bolag med större grad av komplexitet internt i beroenden och koordinering. Som en konsekvens uppstod behov av att hantera hinder som stod i vägen för att göra en större förflyttning mot en tydligare och mer effektiv produktstyrning. Produkterna och affärsutvecklingsprocessen är fundamentet i ATG:s konkurrenskraft. Programgruppen kunde identifiera mönster kring hur information, styrning, uppföljning och återkoppling flödade mellan en strategisk och operativ nivå men där avsaknaden av en taktisk nivå som hade helhetsbilden för ATG:s samlade produkter och kapacitet blev tydlig.

Några av de hinder, symptom och upplevda problem beskrivs här i korthet:

  • Tydliga affärsplaner utifrån produktstruktur saknades. Existerande affärsplaner baserades på
    budgetstruktur utifrån organisationsindelning och inte efter produkter och produkt-roadmaps.
  • Förutbestämda initiativ och mindre inflytande nära produkterna
  • Avsaknad av enhetliga roadmaps som användes i det strategiska arbetet.
  • Roadmaps utgick från ett önskeläge som inte var förankrat i en realistisk bild
    av att alla produkter och team inte kan växa samtidigt.
  • Glapp mellan operativ och strategisk nivå och avsaknad av
    samlad bild för produkter och kapacitet (team).
  • Utmaningar i beslutsordningen, behov av detaljerade beslut lyftes direkt från
    team/PO till ATG:s högsta ledningsgrupp utan konsekvens utifrån helhet.
  • Många och otydliga beställare.
  • Begränsad transparens vilket också inkluderar produkternas och teamens hälsostatus.
  • Produktägare ägde inte hela produktens backlogg utan tog ansvar för affärsmässiga fokusområden
    medan IT Manager ansvarade för IT:s fokusområden. Där respektive följdes upp på mål utifrån affär
    och IT-utveckling.
  • Otydliga kommunikationsvägar. Kommunikationen runt den gemensamma leveransplaneringen hade
    inget forum att kommuniceras i. Hinder och problem gällande prioriteringar mellan teamens leveransplaner försökte man lösa mellan produktägare. I de fall man eskalerade konflikt, gick det direkt till
    strategisk nivå som saknade underlag för hur enskilda beslut påverkade helheten.
  • Supporterande team kom sent in i planeringen vilket påverkade flödet ut mot kund.
    Man hade inte haft möjlighet att proaktivt kunna vara del i planering.
  • Gemensamma definitioner saknades vilket gjorde att man pratade om varandra
(more…)
Written by

MAINSTREAM MODELS MAY NOT BE CUTTING IT

Mainstream coaching models don’t fully account for the unique processing styles that are prevalent in the systemic thinkers that organizations rely upon for creativity and innovation. As a result, we’re not tapping into and releasing the remarkable creative and innovative potential of today’s talent in roles involving creative knowledge work. Moreover, research suggests that many of these systemic thinkers often have attributes of ADD, ADHD, Asperger’s, or other atypical ways of thinking. Given that everyone falls somewhere on the ADD, ADHD, and Asperger’s spectrum, we posit that unleashing creativity and innovation in today’s workplace requires a coaching model that accounts for multiple processing styles. We all think differently, and we need a coaching model that fits everyone.

In this blog post, we present a model designed to leverage the processing strengths and mobilize the brainpower of today’s entire (organizational) collective, which we’re currently calling the Grow/Plow Coaching Model.

POPULAR COACHING MODELS

All the mainstream coaching models we’ve come across are variants of the popular GROW model, which involves establishing a Goal, examining current Reality, exploring Options, and determining what Will happen next: 

The GROW Coaching Model

Such approaches presuppose that the coachee’s processing style prefers to start with concepts, such as goals or the big-picture aspirations often discussed while coaching, before diving into the details. This processing style is known as top-down processing and accounts for how most people think. Top-down thinking is driven by cognition where the brain applies what it knows from experience and what it expects to perceive and “fills in the blanks”. 

SYSTEMIC THINKERS THINK DIFFERENTLY

Systemic thinkers, on the other hand, often have neurobiological and cognitive attributes that result in a bottom-up processing style that prefers details before concepts. A bombardment of sensory information comes in and their brain takes in these details before moving into conceptualization. This processing style is often connected to what’s known as the Weak Central Coherence deficit. In our experience, such thinkers prefer using problem-solving approaches to coaching that welcome the sensory details underpinning the need for change early in the process where the desired future state can be emergent and shaped by data rather than presupposed at the onset. 

THE “PLOW” PROCESS

We took the basic steps involved in problem-solving to create an acronym we call PLOW. The PLOW process involves defining the Problem (i.e., state the problem as clearly as possible and be specific about the situation, behavior, circumstances, and timing that make it a problem); Learning as much as possible about the problem (which includes gathering data like facts, feelings, and opinions); exploring Options; and determining what Will happen next:

The PLOW Process, which can be thought of as a generalized 4-step problem solving model
(more…)
Written by

Earlier this spring we got a fun request: to start an Agile Book Club. Such a privilege to be contacted by a competent and passionate agile frontrunner who wants to use the Dandy People Network!

This spring we started an open Slack work space that we named “Coffee Coaching”, to fill the social gap Corona made. We wanted to create a space where we could meet each other as if we were “by the Coffee machine”, offering a space for a small chat with anyone about anything.

But we wanted to see how this could be used for more. Perhaps for an Agile Book club? And it turned out to be so easy! We simply used this space like in the old times, by putting a piece of paper on the Coffee machine, inviting people to join our new slack channel “Agile Book Club”. And the Agile Book Club was born!

(more…)
Written by

The same rookie mistake I made on my transformation journey into marathoning is one that I see a lot of organizations make on their Agile journey: not taking the time to find the right shoes. Let me explain.

Me with some of the tools that set my foundation to become a marathoner.

“Doing” agile is not enough

I thought I had a solid start on my transformation from couch potato to marathoner by focusing first on the routines and habits of runners. I felt like I was a runner because I was DOING the things runners do, like running 5-days a week, eating healthier, and strength training. Many organizations fall into the same trap. They think they’re agile because they’re going through the same motions and copying best practices. But then my mother saw me running out in the neighborhood and pointed out something that changed everything. She gave me the same perspective that I’ve given clients looking to become agile, and it blew my mind. 

(more…)
Written by

My client is still happy. 

My goal is to coach myself through a transformation from couch potato to marathoner (well, a half-marathon). It’s been life-changing. 

Behavior science is the secret sauce

The barriers and obstacles I experience with “becoming a marathoner” are similar to those experienced by organizations wanting to “become agile”. The secret sauce lies in behavior science. Through this marathoning process, I’ve uncovered my own behavior-based twist of the Deming cycle and Lean Startup and am using them to inspire a Lean Performance Management model for teams and organizations. It’s always fun when personal and professional worlds collide!

The Behavior-Change Cycle

Below is the Behavior-Change Cycle I created for myself inspired by the Deming Cycle and how behavior scientists approach organizational change:

The Behavior Change Cycle I created for my transformation
(more…)
Written by

We asked Paolo Damelio, one of our experienced Agile coaches at Dandy People, to share some of his best tips and tools on how to maintain sustainable and High Performing Teams, now that many of the team members are working from home.

Hi Paolo! What are your thoughts on the situation right now?

This is a challenging time for everyone. For us as individuals, for organizations and for the collaboration inside teams as well as cross-team and cross-organization. And it is a challenge that, I believe, will take us to a place we only could have dreamed of just a few months ago. There is no going back to where we were before.

(more…)
Written by

The need for adaptability and innovation have probably never been bigger, and we need to use the force from our employees. We need to connect the people in our organization using new formats, perhaps being forced into some of them. Also, the distancing has affected all of us, some are suffering more than others. The need for us as human beings to maintain and build trustworthy relationships is being put to test now that we have replaced the small talk by the coffee machine with Zoom meetings. 

We are perhaps seeing the world through new eyes, and maybe even reevaluate our business as well? Can we continue as we did before and still survive? Or, are there ways to move us forward and actually help us be better? And, can the use of a Buddy System be the help we need to help us do this?

Adapt and Excel – it´s All About the People 

To be able to survive in today’s business climate our focus needs to be on our ability to adapt – and to act fast. But that is not enough. Our organizations have to continue to grow and excel to stay alive, and not standstill.

A prerequisite for us to adapt and move fast is to secure that people are responsible for workflows, decisions, actions, and have the authority to make the rapid changes needed.  The type of organization that meets these demands best is a learning organization where it is possible to create endurance and the speed needed in a complex (VUCA) world.

Learning Organization. For many, the traditional top-down management organization has reached its maximum capacity and is unable to obtain, plan, develop, implement and follow up its operations at the pace needed in a world of volatility, uncertainty, complexity, and ambiguity.

(more…)
Written by

In the same way as Aesop’s Fables from Ancient Greece talked about serious matters but transferred them into the world of animals, this game lets all participants play in a friendly environment where nobody is in their ordinary job role. Instead the whole team is challenged to draw randomly selected wild animals well enough so the “customer” can guess what animal is is. The challenge can only be overcome through learning about- and improving how the team is organized and how it works. Two to three hours of laughter, serious learning and quite silly-looking animals can be expected.

The game has been used in one of the largest companies in Sweden to give hundreds of employees a “hands-on” feel for the difference between resource optimization and flow optimization. Especially counter-intuitive ideas need to be experienced to really win acceptance and nothing beats having done it yourself. It also clearly illustrates the value of small rapid improvements in a complex situation (like when working with flow) where you can’t analyze your way to the perfect solution. Sometimes groups of more senior participants try to discuss for a long time before playing another 5-min round. This results in fewer rounds being played, less reality feedback being generated, a slower learning cycle and a lower final score. The team that has the global high-score in the game is a group of junior engineers who could decide rapidly what to try next, play more rounds and thus learn quicker what ACTUALLY worked best. A healthy atmosphere of wanting to change many things compared to the original (and really bad) delivery process was certainly to their advantage too. (more…)

Written by

Vi träffades en kväll i Crisps lokaler på Sveavägen ett gäng intresserade agila UXare, coacher och utvecklare för att prata om något som vi alla tycker är spännande, vill dela med oss av och lära av varandra – hur man kan arbeta med att upptäcka och utforska produkter och tjänster i ett agilt team – Product Discovery. Ett Product Discovery-team innehåller oftast tre roller, där ingår en person med fokus och stenkoll på de affärsmässiga förutsättningarna och målen (PO), en person med användbarhets och upplevelse-kompetens (UX) och en person som kan avgöra hur enkelt eller svårt det är att implementera (Utvecklare/Arkitekt).

Vi pratade om vilka metoder man kan använda för att utforska och lära sig mer om målgrupper och behov och hur detta kan kopplas mot effektmål och visualiseras. Men också om hur man skulle kunna gifta i hop Discovery och Delivery-processen till en helhet utan överlämningar och vi och dom känsla. Vilket vi kallade “Continuos Discovery” – kanske myntade vi ett nytt begrepp? (more…)

Shopping basket
Related Trainings
Our Trainings
The Agile Leadership Team in a Nutshell Training & Toolbox – Online
Target Group: Executives, Managers, Employees, Associates in all functions across the organization, everyone who belongs to a team, and you who also support teams, in an Agile organization.
Start at any time!