SPaMCAST 701 - When The Daily Scrum Doesn’t Make Sense, Agile Requirements, Essays and Conversation - a podcast by Thomas M. Cagley Jr

With SPaMCAST 701 we go back to basics. Whether you call that quick meeting to coordinate the day the Daily Scrum, Stand-up, or a huddle is not material. Daily coordination is phenomenally powerful and useful unless it isn’t.  Just making teams meet without benefit is a really bad idea.  What else can be done?   We also have a visit from Tony Timbol with another installment from his Tell A Story Column. In this installment, Tony discusses agile requirements. Getting work done in agile is not just user stories and a cloud of dust.    Re-read Saturday  News The chapter of this week is titled, Creating An Economy. In the past decade, certain words have become toxic. Words like process, waterfall, and output have become taboo in certain corners of software-related industries. Add the word productivity to the mix and many people would grab torches and pitchforks. The vilification of these words (or any words – it is sort of like burning books in my mind) makes it difficult to talk about systemic improvement. As a Kanban practitioner, I focus on flow. But not just flow, I advise my clients that they should keep their eye on continuously improving the flow. Continuous improvement yields better outcomes. Organizations, teams, and individuals that overextend and exceed their WIP limit are not improving their delivery of outcomes but rather in Jim Benson’s words “disrespecting your ability to create amazing things.” More bluntly they are neither effective nor efficient.    Remember to buy a copy and read along.  Amazon Affiliate LInk:      Previous Entries Week 1: – Week 2: –   Week 3: - Week 4: -   Week 5: -   Week 6: -      Next SPaMCAST  Next week, Matthew Stibbe and I talk about the impact of leadership when building a  technology-driven business.   

Further episodes of Software Process and Measurement Cast

Further podcasts by Thomas M. Cagley Jr

Website of Thomas M. Cagley Jr