Hi Claudio. Wow, I did not expect you to actually read my blog post in Danish! Thank you for making that extra effort. You rock!

I am sure both Popcornflow and Toyota Kata can pick up useful aspects from each other and since I have not used these methods in “the real world”, I’m curious to hear from people with experiences. It was very interesting to attend both workshops.

I would love to hear about more software-related real-world experiments but I do see that there was not time in the one day workshop. There should be an extension :). Jesper, who did the Toyota Kata workshop, mentioned that he had just redesigned his workshop to go from more everyday life examples (loose some weight) to use an example from the participants. It takes up a lot more time, but was also very informative. All in all I would conclude that it was nice to have both perspectives – I loved your examples as well – but to cover both perspectives it would probably be a 2 day workshop each :).

Thank you for a great workshop. I’ll let you know what I learned from all the experimenting we’re going to do :).

Hi Jesper!

Thank you so much for your great workshop and for joining the conversation here as well.

As for your last point – I’m sorry that it wasn’t Toyota Kata that made my heart jump the highest. As I mentioned in the blog post it is mostly a matter of style and need – as I’m not currently doing much structured experiment work (more, “lets try this out, guys and evaluate our gut feeling in a bit of time”), then Popcornflow is already an improvement. It certainly doesn’t mean, I’m never going to try Toyota Kata – just that I’m starting out with another step. Experimenting with experiments! :). The entry barrier does seem to be lower with Popcornflow as you mention. I’m very practical in this respect – I want to maximize my chance for success by making it easier for me to do.

I hope you and Claudio will look into this more. Systems thinking or complexity theory – maybe it is a joint session at GOTO CPH next year? 🙂

Jep. Conway’s law. Din arkitektur kommer til at afspejle din organisation – eller omvendt. Endnu en grund til at der er meget at vinde ved at splitte monolitter op i organisationen og i koden.

Den med sand i skoen var nok lidt en smart bemærkning fra min side :). Det er min erfaring at man i de fleste organisationer er nød til at acceptere at gå udenom en kampesten eller to og så gå videre til at fjerne lidt mindre sten.

Hvis jeg kun kunne vælge at beholde et enkelt element fra Scrum så ville det være Retrospectives!