Tame Your Work Flow, Part 2, A Conversation with Daniel Doiron and Steve Tendon Software Process and Measurement Cast

SPaMCAST 564 is part 2 of my conversation with Steve Tendon and Daniel Dioron.  We discussed their new book . Steve and Danie ask the question “Do you need a high-performance enterprise management & governance approach improving planning, execution, and delivery while dealing with multiple projects, events, stakeholders and teams?”, the book and the interview probes potential answers. In order to answer the question, the three of us take a deep dive into applying Goldratt’s Theory of Constraints in the real world. Listen to part 1 before listing to SPaMCAST 564. Steve Tendon’s Bio With a background in software engineering (in his early career he lead the development of software applications in diverse fields, like banking, health care, legal, human resources, and more), Steve is the creator of the TameFlow ® Approach, a systems thinking approach for creating breakthrough performance innovation in knowledge-intensive digital businesses. The TameFlow Approach has been developed and used with great success since 2003, across numerous industries. Steve holds MSc in Software Project Management with the University of Aberdeen, an MIT Fintech Innovation: Future Commerce certificate with the Massachusetts Institute of Technology, and an Oxford Blockchain Strategy Programme certificate with the Oxford Saïd Business School. Daniel Dioron’s Bio Daniel has been involved in IT since 1981 in a wide range of roles and responsibilities, primarily in client-facing consulting projects covering the government, banking, insurance, and telecom industries to name a few. Daniel’s involvement with Agile started with Scrum in 2005 and more recently with Kanban and Management 3.0. Daniel is heavily involved with Steve Tendon’s TameFlow method. He is proficient with working expertise in Finance/Accounting/Managerial control (MBA-CPA-CMA), Agility (CSP), Project Management (PMP), Kanban (CKC and CKP) coupled with 38 years in IT (Bachelor studies & career). He loves systems, enjoys measuring improvement while embracing teamwork that actually works! For Tameflow Training, visit  Re-Read Saturday News A few nights ago severe thunderstorms rolled through northern Ohio.  There were lots of power outages and trees that were blown over. The next morning when I went to the grocery store, the store’s systems could not accept debit cards. I immediately made up a story that connected the storms to system failure. As we have seen before, System 1 thinking takes disparate facts and creates a coherent believable story.  No conclusion is too big a jump for System 1 thinking. My story and my belief that I had predicted the most probable cause is an illusion of validity which unless I can get System 2 involved stands a good chance at being wrong even though I believe I am correct! Remember, if you do not have a favorite, dog-eared copy of , please buy a copy.  Using the links in this blog entry helps support the blog and its alter-ego, The Software Process and Measurement Cast. ,  It’s time to get reading!   The installments: Week 1: – Week 2: – Week 3: – Week 4: – Week 5: – Week 6: – Week 7: – Week 8: -   Week 9: -   Week 10:  -   Week 11: -   Week 12: -   Week 13: -   Week 14: -   Week 15: -   Week 16: -   Week 17: -   Week 18: —    Week 19: -    Week 20: -     Next SPaMCAST SPaMCAST 565 will feature an essay on sprint goals. Everyone says they use sprint goals. While I am not convinced, those that do use them often mess them up. We will spend a few minutes straightening them out! We will also have a visit from Jon M Quigley who will bring his column, The Alpha and Omega of Product Development to the podcast!