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.

#13 More Effective Agile, Part 5: Manage Technical Debt, Support Large Agile Projects Through Architecture, Automate Repetitive Activities

#13 More Effective Agile, Part 5: Manage Technical Debt, Support Large Agile Projects Through Architecture, Automate Repetitive Activities

FromInspect and Adapt


#13 More Effective Agile, Part 5: Manage Technical Debt, Support Large Agile Projects Through Architecture, Automate Repetitive Activities

FromInspect and Adapt

ratings:
Length:
38 minutes
Released:
Apr 23, 2020
Format:
Podcast episode

Description

Fifth in our series in which Steve McConnell describes the 28 key principles in his new book, More Effective Agile (Construx Press, 2019). The principles discussed this time:"Manage Technical Debt." A consistent focus on quality is part of an effective Agile implementation. Managing technical debt supports higher team morale, faster progress, and higher quality products. (See page 131 in the book.)"Support Large Agile Projects Through Architecture." Good architecture can support portioned work on a project and minimize large-project overhead. Great architecture can make a large project feel like a smaller one. (See page 144.)"Automate Repetitive Activities." No one likes repetitive activities, and many of the activities that can be automated in software development provide more benefit when they’re automated than when they aren’t. (See page 208.) 
Released:
Apr 23, 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!