This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
I love the way in which all the ITRev books fit together and complement each other. For example, Project to Product is a great book for persuading C-level people and finance people of the value of moving away from projects and towards a product model. This in turn helps fast flow, a key aspect of the Team Topologies book. In the TT book we obviously refer to some of the statistics from the Accelerate book for identifying practices that lead of high performance. It's win-win-win for everyone 🤓 🎉
I love the way in which all the ITRev books fit together and complement each other. For example, Project to Product is a great book for persuading C-level people and finance people of the value of moving away from projects and towards a product model. This in turn helps fast flow, a key aspect of the Team Topologies book. In the TT book we obviously refer to some of the statistics from the Accelerate book for identifying practices that lead of high performance. It's win-win-win for everyone 🤓 🎉
After reading Accelerate, the light bulb went on in our CTOs head since it’s so research- and data-driven—hard to argue with!
I echo @UNK3E4Y1M: >I love the way in which all the ITRev books fit together and complement each other. I believe Project to Product puts the focus on one of, if not THE paradigm shift to the concept of flow. Status and progress is mostly a indicator that will tell you if you sucked, but watching cycle times and understanding the real impact of too much WIP, conflicting priorities, unclear dependencies, etc ("Making Work Visible") is what really makes the difference!