Accountabilities
-
Scrum Team
- What is the fundamental organisational unit in Scrum?
- How does the composition of a Scrum Team support its goals?
- What is the typical size of a Scrum Team and why?
- Why are smaller Scrum Teams preferred?
- How does team stability affect Scrum Teams?
- What is the advantage of team members being dedicated to one Scrum Team?
- Why is it important for Scrum Team members to have input into the team’s design and structure?
- How does self-management contribute to the success of a Scrum Team?
- What are the benefits of cross-functional Scrum Teams?
- Why is there no hierarchy within a Scrum Team?
- What are the primary requirements for a Scrum Team in producing usable Done Increments each Sprint?
- How are teams typically organised in larger, traditional organisations?
- What are some inherent challenges in the traditional team approach?
- Why is it difficult for people in traditional teams to feel connected to the end-user or customer?
- How does Scrum propose to mitigate the issues found in traditional team approaches?
- What are the benefits of developing a product iteratively and incrementally in Scrum?
- How does Scrum increase agility and reduce management overhead?
- How does Scrum handle dependencies and delays compared to traditional approaches?
- Why is it essential for Scrum teams to have regular and increased collaboration?
- What role does the Scrum Master play in transitioning traditional organisations to Scrum?
-
Product Owner
- What is the role of the Product Owner in a Scrum Team?
- How does the Product Owner manage the Product Backlog?
- Can the Product Owner delegate tasks related to the Product Backlog?
- What is the importance of the Product Owner’s decisions in the Product Backlog?
- How can a Product Owner be likened to a ‘mini CEO’?
- What are the responsibilities of the Product Owner in terms of product strategy?
- How do effective Product Owners facilitate decision-making?
- What are some characteristics of effective Product Owners?
- Why is support from the Scrum Team and stakeholders crucial for Product Owners?
- What happens if a Product Owner makes a bad decision?
- Why was the Product Owner accountability added to Scrum?
- How were product-related issues and decisions handled in pre-Agile organisations?
- What issues arise from the hierarchical command structure in traditional management?
- How does the committee structure impact the decision-making process?
- What are the consequences of delayed decision-making in traditional management?
- What is the role of the Product Owner in managing the Product Backlog?
- How do Developers support the Product Owner in Scrum?
- Why is it better to make a decision that might later be reversed rather than waiting for perfect information?
- Why is it helpful to think of the Product Owner as accountable for the ‘what’?
-
Scrum Master
- What is the role of a Scrum Master in a Scrum Team?
- How does the Scrum Master facilitate the development process?
- In what ways do Scrum Masters act as change agents?
- How do Scrum Masters provide leadership within the team?
- What are some of the specific ways Scrum Masters serve the Scrum Team?
- How do Scrum Masters support the Product Owner?
- In what ways do Scrum Masters serve the organisation?
- Why is it important for Scrum Masters to have a diverse background?
- How does the role of a Scrum Master differ from a Project Manager?
- Is being a Scrum Master always a full-time job?
- What are the potential issues with rotating the Scrum Master role?
- What is the fundamental shift that organisations new to Scrum experience?
- What challenges might organisations face when adopting Scrum for the first time?
- How can resistance to Scrum adoption manifest within an organisation?
- What role does the Scrum Master play in facilitating the adoption of Scrum?
- Why is the Scrum Master’s accountability crucial for successful Scrum adoption?
- What ongoing support does the Scrum Master require to be effective?
- How long does it typically take for an organisation to fully adopt Scrum?
- What challenges might a Scrum Master face even after Scrum has been adopted?
- Why is the role of the Scrum Master considered perpetual within a Scrum team?
- What might cause an organisation to regress in its Scrum practices, and how can this be mitigated?
-
Developers
- What is the role of a Developer in a Scrum Team?
- What specific responsibilities do Developers have in a Sprint?
- How do Developers contribute to the Sprint planning process?
- Why is the term ‘Developer’ used inclusively in Scrum?
- How does the concept of ‘work’ relate to the role of Developers?
- What does it mean for Developers to be accountable for the ‘how’ in Scrum?
- How do Developers ensure quality in their work?
- What is the importance of daily adaptation of the plan by Developers?
- How do Developers hold each other accountable?
- What does it mean for Developers to create a usable Increment each Sprint?
-
Stakeholders
- What does the term ‘stakeholders’ refer to in Scrum?
- Who is responsible for ensuring the right stakeholders attend the Sprint Review?
- When may the Scrum Team work with stakeholders during a Sprint?
- How does the Product Owner work with stakeholders during a Sprint?
- In what ways do Developers interact with stakeholders during a Sprint?
- What role does the Scrum Master play in working with stakeholders?
- Why is it important for stakeholders to attend the Sprint Review?
- How can the involvement of stakeholders change over time?
- What are the benefits of the Scrum Team working with stakeholders during a Sprint?
- What challenges might the Scrum Master face when working with stakeholders?