Problem solving is central to a product team. But how do you know which problems to solve? More importantly, how can you tell which problems you shouldn’t? Lean product management is all about reducing waste and maximizing value. But waste still abounds. Features are built that never ship because they don’t really solve a user problem. Architecture-up-front prepares teams for a future of scale that never happens – or happens differently than they expected, causing re-work. Or, long after the performance problem has been addressed, a performance team is still laser-focused on improving a number that’s been good enough for a year. The easiest way to reduce waste is to find work that doesn’t need to be done, and then simply not do it. In this talk you’ll hear stories of work that didn’t need to be done, and learn five rules that would have saved months of work. Each rule is short, simple, and memorable, ensuring ease of use in planning conversations. You’ll learn how to apply the rules in an agile context and beyond.
Are you seeing teams that continually struggle with finding a sense of flow? Is it difficult to see how work moves through the system? Is it hard for a team to deliver anything within a sprint because there are too many dependencies or hidden work st…
