ABOUT THIS EPISODE
How should you spend your always-limited testing resources? Is one part of the product more important to test than another? Construx's Steve Tockey and Earl Beede join host Mark Griffin in looking at one approach to answering those questions: risk-based testing. Steve and Earl look at how to do risk-based testing along with its pros and cons.
English
United States
TRANSCRIPT 🔗
Are you the producer of this podcast?
Add a podcast transcript
Need Audio-to-Text?
Transcribe with Listen411 in Just 60 Seconds
SEARCH PAST EPISODES
Search past episodes of Inspect and Adapt.
OTHER EPISODES IN THIS PODCAST
All development organizations use software's F word: Feature. But what they actually mean by the word is often unclear, since the software industry has two—somewhat incompatible—definitions of feature. Join host Mark Griffin as he asks Construx's Steve Tockey and Earl Beede to explain th…
We develop software primarily on teams, but how do you develop the teams? Construx's Mark Griffin and Earl Beede Inspect & Adapt the different ways you can organize your development team. They look at the pros and cons of different approaches and even offer some help for when you're s…
Scaling software development is hard. Several patterns have emerged that moderately successful organizations use when scaling. The patterns focus on how to package the work, where and when to make decisions, and how to get teams to collaborate. Join Mark Griffin, Earl Beede, and Steve Tockey as the…
Total Project Quality, Construx's course on how to insert quality throughout a work effort, hasn't always gotten the traction it deserves. Why not? In this podcast, we examine the subject of quality and our (perhaps poorly-named) Total Project Quality seminar. Join Construx's Steve T…
Disclaimer: The podcast and artwork embedded on this page are from Construx, which is the property of its owner and not affiliated with or endorsed by Listen Notes, Inc.
EDIT
Thank you for helping to keep the podcast database up to date.
