It’s OK to Skip some Scrum Events, Right? Wrong!
While Scrum is a flexible framework, it isn’t Scrum unless you have all the components, so NO, it’s not okay to skip some Scrum events!
The Product Backlog source of requirements for a Scrum Team to select from; it’s owned, managed, maintained, and ordered by the Product Owner.
While Scrum is a flexible framework, it isn’t Scrum unless you have all the components, so NO, it’s not okay to skip some Scrum events!
So, you have a Scrum Team. But does your team have all the necessary cross-functional skills to get to a “done” increment each Sprint?
I have long advocated that Scrum Teams have a “Definition of Ready”; if you don’t have one, there are many potential negative consequences.
I can’t tell you how many organizations I have worked with that had employees who confused the Sprint Review with the Sprint Retrospective.
A “Definition of Done” is a commitment to deliver a working increment meeting defined quality criteria to ensure the increment is complete.
What’s the purpose of a Sprint Review? I’ve seen tons of confusion about the reason for this critical agile event. Let me help clear this up.
For agile transformations to succeed, they must have top-down support from executives who really understand what it means to be agile.
No User Story is complete with Acceptance Criteria; they provide the conditions that must be met, and are critical to agile project success.
The concept of a Product Goal is not new, but it wasn’t an official artifact until the 2020 update to the Scrum Guide. Learn more about it!
A Definition of Done can vary widely between organizations, departments, and even teams, but it’s crucial that you have one. Find out why.