The Lego Game Sprint 3
Sprint 3 | Customers should hand out the stories for Sprint three. | |
Sprint 3: Estimation | 05 | |
Sprint 3-. Sign-up | 05 | |
Sprint 3: Development | 05 | |
Sprint 3: QA Showcase |
05 |
|
Close | 20 |
The start of the final discussion should cover these slightly broader topics 5. Role of the Product Owner: Where did the Product Owner help? When was the Product Owner annoying? 6. Redesign / Simple design: What did you have to redesign? What design choices that you made early on remained consistent throughout the exercise? What were these choices characteristics? Elicit the points from the participants: • Iterative development • Time Boxing • Adaptive Planning • Evolutionary development • Feedback. • Customer Driven vs Risk Driven Discuss the points in any order, but discuss one point at a time. If there is more than one team participating, be sure to compare and contrast each team's experiences on that topic. Once you have covered most/all the points, talk about what new things were learned in this session. Use the white boards to write new terms and concepts. Elicit the points from the participants |
|
|
|
• Estimation |
|
|
|
• Sprint – Time-boxed duration for software development. This is usually 2 to 4 weeks. |
|
|
|
• Relative Complexity |
|
|
|
• Points – Stories are estimated for effort using a scale of 1-5 or a |
|
|
|
• Fibonacci sequence (1, 2, 3, 5, 8....). |
|
|
|
• Velocity – Number of points consistently completed per Sprint. |
|
|
|
• Spiking: Introduce the concept of spikes being stories in Iterations to get insights for estimating for next iterations. |
|
|
|
• Sprint 0 |
|
|
|
• Spiking at different times |
|
|
|
• User Story |
|
|
|
• Retrospective |
|
|
|
• Self organizing team |
|
|
|
• Hangover – The number of signed-up points left incomplete in Sprint. |
|
|
|
These are a hangover to the next Sprint. |
|
|
|
• Acceptance Criteria/Definition of Done – Analysts/Developers should ask the customer when they will consider a story done. |
|
|
|
• Bug – Any piece of functional or non-functional requirements incomplete or not meeting the acceptance criteria for a story is a bug. |
|
|
|
• Showcase – An all team meeting that is primarily aimed at displaying functionality developed during an Sprint to the Product Owner. |