Recently I've been reading "When Agile Gets Physical" [1] and "Extreme Programming Explained": 1. "Extreme Programming Explained" explains the importance of se

Recently I've been reading "When Agile Gets Physical" [1] and "Extreme Programming Explained": 1. "Extreme Programming Explained" explains the importance of separating values from principles and practices. 2. "When Agile Gets Physical" unpacks why using agile software best practices are horrible for hardware. This is "duh" if you're a hardware person, but the book goes back to agile/lean first principles, and then builds up an approach for agile hardware. It got me thinking that we often conflate values and practices. Blinding adopting Scrum or DevOps without understanding some of the underlying value and principles leads to problems. If you understand the foundational principles, you're in a much better position to adopt/reject certain practices for your given situation. In reality, most organizations just adopt a few agile practices, while rejecting the basic values. [1] https://rapidlearningcycles.com/when-agile-gets-physical/ https://rapidlearningcycles.com/when-agile-gets-physical/ [2] https://www.amazon.com/Extreme-Programming-Explained-Embrace-Change/dp/0321278658 https://www.amazon.com/Extreme-Programming-Explained-Embrace...