Solution #3 – don't strive for throughput, instead restructure teams based on outcome-driven timelines
Releasing often helps us to learn and respond swiftly to feedback, but how often is often? A combination of timeline, effort, and desired outcomes (business and customer impact) may determine how often we release. Some functionality can be built in a few hours. Some can take a few days or weeks. Also, based on the stage of product maturity, we may need less or more focus on technical stability. Technical success criteria are likely to vary based on desired outcomes. Customer context and market needs also have a bearing on how soon or frequently we can update our product.
If something can be released in a few hours and can speed up our feedback ...
Get Lean Product Management now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
