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 πβοΈ
4/ The project addresses the pain of the engineering managers, CTOs, engineering leaders, ... those who manage teams and need to organize teams for a fast flow of change
It addresses the feedback cycle on understanding the team's impact on splitting, merging, and creating a team
It addresses the feedback cycle on understanding the team's impact on splitting, merging, and creating a team
5/ It's not about 4Key Metrics from Accelerate (DAMN! I forgot this one in the Wardlay Map!)
It's not about understanding the bounded contexts
It's not about an org view using the 4 TeamTopologies and their collaboration
Can you guess what's it about? π€π§‘
It's not about understanding the bounded contexts
It's not about an org view using the 4 TeamTopologies and their collaboration
Can you guess what's it about? π€π§‘
β’ β’ β’
Missing some Tweet in this thread? You can try to
force a refresh
γ
