The Product Owner is involved with the other Team Members throughout the Sprint, but after the Sprint Planning meeting is completed, the Product Owner cannot add to the scope of […]
Scrum Rules: Your Product Owner Knows the Estimated Return on Investment of a Sprint
The Product Owner is responsible for the Return on Investment (ROI) of the Product. In order to manage that responsibility, the Product Owner needs to estimate how much financial benefit […]
Scrum Rules: Your Scrum Master Creates and Maintains the Team’s Sprint Burndown Chart
The Sprint burndown chart tracks the amount of work remaining in the Sprint day-by-day. The burndown chart is updated daily and is visible to the team and stakeholders. This activity […]
Scrum Rules: The Product Backlog Changes Every Sprint
The Product Backlog reflects the current state of the Product Owner’s understanding of the future of the Product. Unless the product is being discontinued, the future state will always include […]
Scrum Rules: The Product Backlog Is Easily Visible to Every Stakeholder
The Product Backlog is a constantly changing artifact, owned by the Product Owner. Stakeholders need real-time visibility into the current state of the Product. Stakeholders should be able to discuss […]
Scrum Rules: The Product Backlog Is Refined for Every Sprint Planning Meeting
A well-refined Product Backlog is one which is: ordered to maximize return on investment for the customer; provides enough clarity that the Scrum team can perform the work of their […]
Scrum Rules: The Scope of Work Is Never Expanded Mid-Sprint
The Scrum Team plans their work in the Sprint Planning meeting and that planned scope (Product Backlog Items) is meant to be respected… it is a commitment by the team. […]
Scrum Rules: Sprints Conclude With a Sprint Retrospective
The last part of the Sprint is the Sprint Retrospective. This meeting is a private meeting for the members of the Scrum Team (including the Scrum Master and Product Owner). […]
Scrum Rules: No Work is Performed Between Sprints
Each Sprint that a Scrum Team does is an opportunity for learning through “inspection and adaptation”. If there is a break or a pause between Sprints, the Scrum Team may […]
Scrum Rules: Sprints are a Consistent Length
The Sprint is the fundamental unit of work when using Scrum. Any product development effort using Scrum is, therefore, divided into Sprints. Sprints are fixed in length so that the […]