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.
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 those two different uses of the word feature on development projects.
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.
