Download to read offline
Uploaded byXSolve
How to be agile at Agile Hack?! - agilehack.pl
The document outlines the Agile methodology, detailing the roles within a Scrum team including the product owner and Scrum master, and emphasizes the importance of planning and review processes. It includes specific time allocations for planning sessions, reviews of deliverables, and retrospectives to enhance team performance. The overall focus is on maximizing business value and continuous improvement within Agile practices.
More Related Content
Similar to How to be agile at Agile Hack?! - agilehack.pl
How to be agile at Agile Hack?! - agilehack.pl
- 2. How to beagile at Agile Hack?!
- 3. Mateusz Ryba -Scrum Master mateusz.ryba@xsolve.pl
- 4.
- 6. 0 18 min PlanStartBudowanie
- 7.
- 12.
- 13. Development Team Product OwnerScrum Master
- 14. Development Team Creates IncrementSelf-organised Cross-functional
- 15. Product Owner Maximizes businessvalue Has vision and represents it by Product Backlog
- 16. Scrum Master Creates process andenvironment Remove impediments
- 17.
- 18.
- 19.
- 20.
- 21.
- 22.
- 23.
- 24.
- 25.
- 26.
- 27.
- 28. REVIEW WHAT IS NOTDONE?
- 29. REVIEW WHAT DO WEPLAN NEXT?
- 30. Sprint Product Backlog Sprint Backlog Planning Review What? How? What’s done? What’snot done? How does it influence Product Backlog? 1h 30m
- 31.
- 32.
- 33.
- 34.
- 35. Sprint Product Backlog Sprint Backlog Planning Review Retrospective What? How? How to improve? What’sdone? What’s not done? How does it influence Product Backlog? 1h 30m