Agile Sprint Challenge
Across
- 4. Prioritized list of all tasks and features
- 7. High-level plan showing future product direction
- 9. A short, time-boxed period to complete work
- 11. Short description of a feature from the user’s perspective
- 13. A small unit of work representing user value
- 15. Meeting to inspect the outcome of the sprint
- 17. Practice of frequently merging and testing code
Down
- 1. Person responsible for maximizing product value
- 2. Large feature broken down into smaller stories
- 3. Criteria that define when work is complete
- 5. Visual workflow system with columns like “To Do” and “Done”
- 6. Facilitator who ensures Scrum practices are followed
- 8. A flexible approach to software development
- 9. A popular Agile framework with defined roles and events
- 10. A fixed limit for completing an activity or event
- 12. Daily meeting for team synchronization
- 14. Measure of how much work a team can complete per sprint
- 16. Meeting to reflect and improve after a sprint
- 18. A usable piece of software delivered after each sprint