TL; DR: Evidence-guided Product Discovery Using Itamar Gilad’s Confidence Meter
How much product discovery is enough? Figuring out what is worth building often feels valuable in and of itself. The problem is that becoming stuck in an endless discovery cycle neither solves your customers’ issues nor contributes to your organization’s sustainability. Don’t worry; help is on the way in the form of Itamar Gilad’s Confidence Meter!
TL; DR: Hands-on Agile #46: Engage the Agile Fluency® Model with Diana Larsen
On October 12, 2022, agile innovator Diana Larsen delved into the Agile Fluency® Model. After a short introduction to the model, we shifted to an ask-me-anything-style discussion of the groundbreaking view of agile and teams.
TL; DR: Hands-on Agile #45: FAST Scaling: An Innovative Way to Scale Agile with James Shore
In this energizing 45th Hands-on Agile session, James Shore shared his experiences with scaling “agile:” first with traditional approaches and, more recently, with FAST scaling. Learn in this deep-dive what works, what doesn’t, and how you can try FAST in your organization.
TL; DR: HoA #44: Honey, I Shrunk the Backlog w/ Allan Kelly
In this energizing 44th Hands-on Agile session on product backlog management, Allan Kelly clarified one thing: The backlog was a great idea until it wasn’t. Many successful teams deliver backlog items daily, but their backlogs aren’t getting smaller. The never-ending backlog overshadows delivery success. Product discovery, dual-track agile, OKRs, etc., make it worse by accelerating backlog growth without taking any of the rotting items away.
Learn more about Allan’s remedy for oversized product backlogs in less than an hour.
TL; DR: HoA #43: Outcome-Based Product Planning w/ Jeff Gothelf
In this energizing 43rd Hands-on Agile session on outcome-based product planning, Jeff Gothelf clarified one thing: “Roadmapping is a flawed concept in the age of Agile. Maps, by their definition, are linear, and we don’t build linear products and services anymore. We build continuous systems.” Learn more about what he considers product roadmap flaws and what you can do about them.
There are plenty of failure possibilities with Scrum. Given that Scrum is a framework with a reasonable yet short “manual,” this effect should not surprise anyone. For example, what if there is no Sprint Goal — Sprint after Sprint? What if the Scrum team is always only working on a random assortment of work items that seem to be the most pressing at the moment of the Sprint Planning?
Join me and delve into the importance of the Sprint Goal for meaningful work as a Scrum team in less than two minutes.
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookies
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
