Holacracy joy and pain


I want to share my 3-year experience with Holacracy.
The implementation seen in my previous job with a detached point of view, an example of auto-organization at company level whit some joys and pains.
It's not a judgment about Holacracy but only the story of my experience.


Comments

Post a Comment

Popular posts from this blog

"Back to values" agile retrospective format

Image
A week ago i proposed to my team a new format for the weekly retrospective. I called it "Back to values" because the starting focus is on values and then on practices and actions to improve that practices. Step 1: the values I put on the wall seven big post-its with the values, on the pink post-its the eXtreme Programming values plus the team's values on the orange post-its. simplicity (XP) communication (XP) feedback (XP) courage (XP) respect (XP) trust (team) sharing (team) Each teammate has an up arrow and a down arrow and I asked them to vote the best performing value of the week and the worst performing one. At the end of the vote we chose the two most rated values (no matter if with down or up arrow). In our case the chose values was communication and sharing. Step 2: the practices For each of the two chose values (one at a time), I asked the team to write on post-its all practices that support this value, both if they had used them and if...
Read more

Evoluzione del pair programming in un team (quasi) decennale

Image
I spoked ad Mini Agile Day in Trento , here you can find the slide of the talk. I present my experience with Team Nimbus at 7Pixel since 2009. From the "by the book" implementation to the "superpower" adaptation maked by the team. What is pair programming? How does it works?  How we have changed it? Errors and improvements of 9 years of pair programming. Evoluzione del pair programming in un team (quasi) decennale from Marco Fracassi
Read more

Java relative paths: trick or treat?

Image
We all had problems with relative paths in Java! Do not deny it! Every time I have to understand where the path is relative to is a puddle of blood, so how can we unveil this mystery? Will it be relative to the classpath? Will it be related to the project root? And in the tests? I usually use a little trick : in the point of the code where I want to use the relative path I write/log Java: new File(".").getAbsolutePath() Kotlin: File(".").AbsolutePath Simple and fast, at this point we know exactly where is the starting point for our relative path!
Read more