zx
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.
???? Watch the video now: James Shore: FAST: An Innovative Way to Scale — Hands-on Agile #45.
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.
???? Watch the video now: Jeff Gothelf: Outcome-Based Product Planning — Hands-on Agile 43.
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.
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 your Scrum team repeatedly faces unengaged stakeholders at the Sprint Review? How can the Scrum team stay on track in accomplishing the Product Goal when a vital feedback loop is missing?
Join me and delve into how to support your stakeholders in living up to their part of the collaboration with the Scrum team in less than two minutes.
In this energizing 42nd Hands-on Agile Lean Roadmapping session, Janna Bastow, the go-to-authority on product roadmaps, talked about being lean while creating and maintaining your roadmap and how objectives and key results (OKR) may help meet that challenge.
???? Watch the video now: Janna Bastow: Lean Roadmapping and OKRs — Hands-on-Agile #42.
In this energizing 38th Hands-on Agile session, Roman Pichler delved into your questions on the role of the Product Owner. The topics range from product manager vs. Product Owner vs. business analyst to the right size of a Product Backlog to linking product vision to Product Goal and Sprint Goal.
???? Watch the video now: Roman Pichler: The Product Owner — Hands-on-Agile #38.
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. One failure symptom of a botched agile transformation is the frustrated Scrum Master.
???? Join me and explore the consequences of a Scrum Master who has thrown in the towel in 92 seconds.
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. To make things worse, a crucial success factor of every Scrum team is not even mentioned in the Scrum Guide: Any organization that wants to employ Scrum to learn faster than its competitors needs to have a solid failure culture.
???? Join me and explore the consequences of not living a failure culture in less than three minutes.
There are plenty of Scrum stakeholder failures. Given that Scrum is a framework with a precise and concise yet short “manual,” this effect should not surprise anyone. While the Scrum Guide makes numerous references to stakeholders in Scrum, stakeholders themselves are no official role (accountability), no matter their crucial contribution to a Scrum team’s overall success.
Explore with me three widespread examples of how stakeholders fail their Scrum teams in three short video clips, totaling 6 minutes and 5 seconds.
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. However, creating Product Increments that “over-deliver” in scope or quality — also known as gold-plating — with regard to the previous refinement agreement demonstrates that the Developers need to acquire a more entrepreneurial mindset and embrace their responsibility.
Join me and explore the reasons and the consequences of this Sprint anti-pattern in 109 seconds.
