Good Practices
-
User Stories
- What are user stories and their purpose in product development?
- How do user stories facilitate collaboration among team members?
- Can you provide an example of a user story and explain its components?
- How do user stories help developers understand the context and purpose behind features?
- Why are user stories important for creating a user-centric product?
-
Automation
- Why is automation considered vital for Scrum Teams?
- How can automation benefit areas outside of testing within Scrum Teams?
- Can you give an example of how automation improved efficiency in a specific project?
- How did automation help in a complex billing process you worked on early in your career?
- What is the long-term importance of integrating automation into Scrum practices?
- Velocity
-
Poker Planning
- What is Poker Planning, and how is it used in estimating Product Backlog items?
- Why are Fibonacci series values commonly used in Poker Planning?
- How does the process of revealing cards work in Poker Planning?
- What are the advantages of using Poker Planning for estimation?
- How does Poker Planning enhance understanding and identify potential issues in projects?
-
Story Points
- How does collaboration influence the accuracy of estimates in Scrum Teams?
- What are story points and how do they differ from time-based estimates?
- Why are story points preferred over time-based estimates by Developers?
- How do Developers assign story points, and what scale is typically used?
- How do story points and velocity help in planning and forecasting within a Scrum Team?
-
Flow Metrics
- What techniques are replacing story points, velocity, and Poker Planning in Scrum?
- What are the four basic flow metrics tracked by Scrum Teams using Kanban?
- How does limiting Work in Progress (WIP) benefit Scrum Teams?
- What role does Cycle Time play in predicting delivery times for future work?
- How can Throughput help a Scrum Team manage their capacity and meet customer needs?