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.
In an earlier webinar, Construx's Earl Beede took on many organizations that create product visions with phrases like, be the world's best ‘x’ or dazzle our customers. Not bad ideas but pretty much worthless in helping you make day-to-day decisions on what work is the most important for your business. This is a follow-up, with Earl and Mark Griffin delving a bit deeper into some of the questions that came up during the webinar. You can find the webinar here: https://youtu.be/yVA-k6aWE0k
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.
