(This will be the first in a series of posts about XP. I’m publishing them here because the overlap with Tidy First? readers seems substantial & the subscriber list is long. Please lmk if you’d rather I had channel/topic.) I have written before about Professor Zaninotto’s framework for understanding why complex systems are impossible to control. The tl;dr is that systems become unpredictable when you combine:
I don’t know if there is a really good description, but I found this article that talks about how LEGO uses it and why. https://velocityagile.substack.com/p/lego-using-big-room-planning-to-calm
When I did it, it was less regimented: we got everyone in a room for a whole day, making out teams’ right plans and dependencies on a physical wall, using pieces of string to show dependencies. It was not only fun to do but helped everyone get a better understanding of what was going on and avoided some dependencies that would have bitten us in the butt without this. I’d post a picture if I could :)
Have you ever tried Big Room Planning? I first observed it at LEGO, and then tried it with all of the Tech teams at King. Definitely interesting, but also hard to do.
I always thought that applying network analisys on codebases data would help orgs to understand software dependency complexity.
In more details:
1. Create a 2-mode network (committer.team_id x git_repo),
2. Project it into 2 single-mode networks (commiter.team_id x committer.team_id and git_repo x git_repo)
3. Generate centrality metrics on the 2 single-mode networks to find out important nodes and sub-graphs.
Do you think it could be a proxy for the Awareness item?