Discover this podcast and so much more

Podcasts are free to enjoy without a subscription. We also offer ebooks, audiobooks, and so much more for just $11.99/month.

#18 More Effective Agile, Part 6: Refine the Product Backlog, Create and Use a Definition of Ready, Minimize the Defect Detection Gap

#18 More Effective Agile, Part 6: Refine the Product Backlog, Create and Use a Definition of Ready, Minimize the Defect Detection Gap

FromInspect and Adapt


#18 More Effective Agile, Part 6: Refine the Product Backlog, Create and Use a Definition of Ready, Minimize the Defect Detection Gap

FromInspect and Adapt

ratings:
Length:
42 minutes
Released:
Jun 16, 2020
Format:
Podcast episode

Description

Sixth in our series in which Steve McConnell describes the 28 key principles in his new book, More Effective Agile (Construx Press, 2019). The principles described this time:"Refine the Product Backlog." Backlog refinement ensures the team is working on the highest priority items, is not filling in gaps in requirements on its own, and is not starved for work. (See page 187 in the book.) "Create and Use a Definition of Ready." Part of backlog refinement is ensuring that requirements are truly ready before the team begins implementing them. (See page 188.)"Minimize the Defect Detection Gap." The cost to fix a defect tends to grow the longer it stays in process. A benefit of Agile’s focus on continuous quality work is detecting more defects closer to the source. (See page 155.) 
Released:
Jun 16, 2020
Format:
Podcast episode

Titles in the series (48)

World-class software development requires far more than language/platform expertise and steady sprints. Join us as we describe time-tested, industry-proven software best practices at the team, organization, and leadership levels, sharing examples from recent engagements with software teams of all sizes.Construx is led by industry leader Steve McConnell, author of Code Complete and More Effective Agile. Software experts first and software trainers and consultants second, our team has seen what works and doesn’t work in hundreds of software organizations.Host Mark Griffin spent the first half of his career as an electrical engineer doing silicon hardware design and leading software automation teams. He moved into the sales side of software because he wanted to spread the value of what his company was building. It was supposed to be a one-year assignment that turned into the second half of his career. His balance of deeply technical skills and right-brain artistry also makes him a masterful home brewer!