Great post. Highlights the importance of selecting the right problem to focus on and to limit WIP on other ones. Setting a clear start and end date is crucial when running these experiments in my experience as described in the article.
It's an eye opener for some that see now a more complex set of issues involved.
In practice though the team leader, CPO or similar, has to invest tones of time and energy to make it work through all the resistance and passive-aggressive behavior or people who, naturally, don't want changes and wired to seek for homeostasis.
Thank you for this, it's great! One more thing to help form new habits - publicly praise/recognise people who are doing the new thing properly. Simply saying "great work updating the information radiator" in a team meeting positively incentivises the behaviour, helping the new thing stick and role-modelling to other team members that "this" is a praise-worthy activity.
Great post. Highlights the importance of selecting the right problem to focus on and to limit WIP on other ones. Setting a clear start and end date is crucial when running these experiments in my experience as described in the article.
Reading the book now. Thanks John.
It's an eye opener for some that see now a more complex set of issues involved.
In practice though the team leader, CPO or similar, has to invest tones of time and energy to make it work through all the resistance and passive-aggressive behavior or people who, naturally, don't want changes and wired to seek for homeostasis.
Thank you for this, it's great! One more thing to help form new habits - publicly praise/recognise people who are doing the new thing properly. Simply saying "great work updating the information radiator" in a team meeting positively incentivises the behaviour, helping the new thing stick and role-modelling to other team members that "this" is a praise-worthy activity.
Very interesting ideas. I see clearly now why we're stuck on autopilot and why our retros suck.