Software Process And Measurement Cast

SPaMCAST 483 will feature our essay on measuring the value delivered by agile. The essay begins: “Organizations and teams come to agile—for that matter, any concept, framework or technique—for a wide variety of reasons.  Even if we are just the keeping up with the neighbors, we need feedback to know if we have met our goal.  We need feedback because—to quote Paul Gibbons, author of The Science of Successful Organizational Change (Re-read Saturday)—“we confuse what we think ought to work” with what does work (quote from SPaMCAST 480).” Four Agile Value Entries: Does Agile Deliver Measurable Value? Measuring the Value of Agile Does Agile Deliver Value? You Can Prove it! Measuring The Impact of Change: An Example Our second column features Steve Tendon who brings his Tame The Flow: Hyper-Productive Knowledge-Work Performance, The TameFlow Approach and Its Application to Scrum and Kanban  (buy a copy here) to the cast.  Today we complete our discussion of Chapter 21.  We have spent extra time on chapters 20 a