Discover and read the best of Twitter Threads about #TeamTopologies
Most recents (4)
If you're excited to leverage #WardleyMapping, #DDD, #ValueStreamManagement, and #TeamTopologies, order of execution can help smooth the journey.
One should launch you into the other well prepared to create value. Here's a flow that sets you up for success: 🧵
One should launch you into the other well prepared to create value. Here's a flow that sets you up for success: 🧵
First, clarify needs, objectives, obstacles, and a vision for your future state. You can use Outcome Mapping or a press release formula for this (ideally both).
Working backwards always helps you avoid wandering or drift from working forwards, and brings a team into alignment.
Working backwards always helps you avoid wandering or drift from working forwards, and brings a team into alignment.
Wardley Mapping helps understand your current ecosystem and what the future could look like if you change things. This is a great place to start to discover current work streams and focus your efforts.
1/ Side Project C started 🚀
It came after understanding the paradigm shift from Organizing teams, where we see a tendency toward @TeamTopologies, #DDD, and #DynamicReteaming as new emerging practices vs the old paradigm.
It came after understanding the paradigm shift from Organizing teams, where we see a tendency toward @TeamTopologies, #DDD, and #DynamicReteaming as new emerging practices vs the old paradigm.
2/ With a higher #TeamTopologies adoption, it creates new sorts of needs for managers.
Needs that I'm currently facing and I'm currently solving with Excel files to gather team's feedback and improve my organization sensing
Needs that I'm currently facing and I'm currently solving with Excel files to gather team's feedback and improve my organization sensing
3/ I will make the side project publicly as soon as I feel confident about it. Yet, I do a Tweet about it because it boosts my commitment to the side project 😄✌️
1/ We have been debating with some colleagues about the importance of learning about our decisions within the organization, and how the fast rotation of talent that's happening lately is affecting the decision-making outcomes quality.
2/ Here we had the supposition that the feedback cycle between a decision is made and understanding the consequences are long enough. We always thrive for fast feedback loops, yet we acknowledge that that's not always possible.
3/ It's not the same doing TDD within a unit test - feedback cycle of seconds-minutes vs a business decision and go-to-market strategy that can take months.
We are talking about the latter. Where those business learnings are most valuable for the organization
We are talking about the latter. Where those business learnings are most valuable for the organization
Reading the conclusion of
#TeamTopologies again, I like to share a couple of tweet-sized quotes that stood out to me:
#TeamTopologies again, I like to share a couple of tweet-sized quotes that stood out to me:
"To avoid software becoming even larger and eventually overwhelming a team, the size of subsystems (or components) are limited to that manageable by a single team." #CognitiveLoad
"Team structures must match the required #SoftwareArchitecture or risk producing unintended designs" #ConwaysLaw
