Really interesting (and very practical) article on organization culture. It’s easy to see how practicing TameFlow would fit in with these ideas. https://cloud.google.com/solutions/devops/devops-culture-westrum-organizational-culture
“Common traps were stepped in—like trying a top-down mandate to adopt Agile, thinking it was one size fits all, not focusing on measurement (or the right things to measure), leadership behavior not changing, and treating the transformation like a program instead of creating a learning organization (never done).Throughout the journey, the focus was moving to outcome-based team structures, knowing our cycle time (by understanding our value stream map), limiting the blast radius (starting with one to two teams vs. boiling the ocean), using data to drive actions and decisions, acknowledging that work is work (don’t have a backlog of features and a backlog of technical debt and a backlog of operational work; instead, have a single backlog because NFRs are features and reducing technical debt improves stability of the product). None of this happened overnight, and it took a lot of experimentation and adjusting along the way.”
Forsgren PhD, Nicole; Humble, Jez; Kim, Gene (2018-03-26T23:58:59). Accelerate . IT Revolution Press. Kindle Edition.