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 they explore scaling patterns.
All content for Inspect and Adapt is the property of Construx and is served directly from their servers
with no modification, redirects, or rehosting. The podcast is not affiliated with or endorsed by Podjoint in any way.
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 they explore scaling patterns.
Why can't I know—with high precision—the final cost, scope, and time frame of my work effort? One of the biggest reasons you can't know all three at once is illustrated by Steve McConnell's Cone of Uncertainty. In this episode of Inspect & Adapt, Construx's Mark Griffin, Steve Tockey, and Earl Beede talk about what the Cone is, how it impacts your ability to estimate, and how you can use it to increase your estimate predictability.
Inspect and Adapt
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 they explore scaling patterns.
