Innovation Accounting in Scrum

Innovation Accounting in Scrum

Abstract: In Scrum a Product Owner can be described as a “value maximizer”…but how is value calculated? In this presentation we consider how empiricism ought to underpin any assessment, and at how the discipline of “Innovation Accounting” can challenge predictive value assumptions.

Why the Sprint Goal is not an Essential (Mandatory) Artifact

Although, the Sprint Goal is not defined as an artefact within the Scrum Guide it is an integral part of the Scrum framework. It provides an overarching objective for the Scrum Team which helps them to focus “WHY” is the team invested in the Sprint.

Why do we choose to conduct this Sprint? What is the value we seek to create? Why did we select these items from the Product Backlog and not others? How will we know whether the Sprint was successful in the Sprint Review? Those are the questions we seek to answer with the Sprint Goal and if we have no clarity on those aspects of Product Development then we are missing a key element of Empiricism, and missing a key Inspect & Adapt opportunity in Scrum.

Read the complete article here: https://www.scrum.org/resources/blog/why-sprint-goal-not-essential-mandatory-artifact

The difference between the ‘forecast’ and the ‘Sprint Backlog’ in Scrum

There is a difference between the forecast and the Sprint Backlog in Scrum. Exactly what this difference is, has eluded me for some time, and it may very well be unclear to you too. The difference may seem subtle but can have real practical benefits as you will learn below.

Continue reading here: https://www.scrum.org/resources/blog/difference-between-forecast-and-sprint-backlog-scrum

10 powerful strategies for breaking down Product Backlog Items in Scrum

Teams that have mastered Scrum know that the key to success lies in a just-in-time, increasingly refined, breakdown of work on the Product Backlog. They prefer Sprint Backlogs with many small (functional) items instead of just a few large ones. Smaller items improve flow and reduce the risk of failing the sprint. In this article, I will explain why the breakdown of work is important, and why it should be done across functional — instead of technical — boundaries. Christiaan Verwijs offers 10 useful strategies that experienced Scrum Teams use to break down work in this article: https://medium.com/the-liberators/10-powerful-strategies-for-breaking-down-user-stories-in-scrum-with-cheatsheet-2cd9aae7d0eb