Commitments
-
Product Goal
- What is the Product Goal in Scrum?
- Why is the Product Goal considered a long-term objective for the Scrum Team?
- What role does the Increment play in achieving the Product Goal?
- Who is responsible for creating the Product Goal?
- Where can the Product Goal be found within the Scrum framework?
- How does a product deliver value?
- What are the key characteristics of a product?
- What forms can a product take?
- Why is it important to have a clear boundary for a product?
- How do well-defined users or customers influence product development?
- What is a Product Goal according to Scrum?
- How does a Product Goal differ from a Sprint Goal?
- What role does the Product Goal play in the Product Backlog?
- Why is it essential to have only one Product Goal at a time?
- How do Product Goals and Sprint Goals improve Scrum’s empirical approach?
- How do product vision and product strategy relate to Product Goals?
- Why can Product Goals address multiple objectives?
- What happens when leaders do not set clear priorities?
-
Sprint Goal
- What is the Sprint Goal, and why is it important to the Sprint Backlog?
- How is the Sprint Goal created, and who is involved in its creation?
- What benefits does a good Sprint Goal provide to the Scrum Team?
- How does a Sprint Goal help with prioritisation within the Scrum Team?
- In what ways does a Sprint Goal enhance communication with stakeholders?
- What are some tips for creating effective Sprint Goals?
- Can there be multiple aspects to a Sprint Goal, and how should they be managed?
- What might indicate a struggle in setting a Sprint Goal, and how can it be addressed?
- How can the maturity of a product affect the creation and usefulness of Sprint Goals?
- Why is it important for not all work in the Sprint to relate directly to the Sprint Goal?
- How does a Sprint Goal relate to the Sprint Backlog?
- How do Product Goals and Sprint Goals improve Scrum’s empirical approach?
-
Definition of Done
- What is the significance of transparency in Scrum artifacts?
- What is the Definition of Done in Scrum?
- Why is the Definition of Done considered crucial in Scrum?
- How does the Definition of Done impact the Sprint Review?
- What happens if the Definition of Done is part of the organisation’s standards?
- How should multiple Scrum Teams working on the same product handle the Definition of Done?
- Why is it important for the Definition of Done to be binary?
- What practices can Scrum Teams use to create a Definition of Done?
- What challenges might new Scrum Teams face regarding the Definition of Done?
- What should Scrum Teams do if they cannot achieve a Done Increment?
- How should Scrum Teams approach the concept of Done in practice?