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.
The product owner is often considered the most critical accountability in the triad of <product owner, scrum master, developers>. Why? Because garbage in from the product owner gets garbage out of the developers, so it's crucial to give serious consideration to who is best to staff the product owner role. Listen to Construx experts share best practices, things to watch for, and stories from the field as they Inspect & Adapt the staffing of the product owner.
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.
