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
"...Organizations should expect teams to collaborate to discover new patterns and execution models, then push these down into the platform and supporting tooling" #SpikeAndStabilize
Garden analogy
"Software can not be expected to grow and thrive, if the environmental conditions are hostile."
Needs structure and well-designed communication plus:
- Healthy org culture
- Good eng practices
- Healthy funding and financial practices
- Clarity of business vision
"Software can not be expected to grow and thrive, if the environmental conditions are hostile."
Needs structure and well-designed communication plus:
- Healthy org culture
- Good eng practices
- Healthy funding and financial practices
- Clarity of business vision
If you are working in a software creating organization, I highly recommend "Team Topologies" by @matthewpskelton @manupaisable.
It is just such a delight to read 👏 teamtopologies.com/book
It is just such a delight to read 👏 teamtopologies.com/book
• • •
Missing some Tweet in this thread? You can try to
force a refresh
