Scrum is an agile framework for managing product development projects. It utilizes short "sprints" where self-organizing cross-functional teams work to complete user stories from a prioritized backlog. Daily stand-up meetings help coordinate work. At the end of each sprint, teams demonstrate completed work to stakeholders for feedback to improve subsequent sprints. Periodic retrospectives help teams improve their processes. Compared to traditional "waterfall" models, Scrum aims to handle changing requirements better through rapid iteration and continuous customer input.
19. • Get hands on quickly
• cross-functional team empowered to make
decision
• rapid iteration / incremental
• continuous customer input
• Just do it ? ...not exactly
Agile
31. Product Backlog
• Value / Feature of product (High level)
• describe as User Story
• Owned by Product Owner
• Estimated by Team
• not perfect (expected to change)
38. Sprint Planning pt.1
• PO + Team + (SM)
• High priority items on Product Backlog
• Context + Def. of done
• What PO wants
39. Sprint Planning pt.2
• Team + (PO + SM)
• focus on the How
• How much effort we have?
• How many items we could do?
• Sprint Backlog
• Volunteer for one task at a time
40. Definition of Done
• Introduce earlier
• To avoid 90% syndrome
• Usually physical / tangible
• Works great with ex. TDD
49. Product Backlog Refinement
• lesser known but valuable
• 5% of sprint time (Team + PO)
• Req. analysis / Splitting items / (re)Estimation
• Workshop near end of sprint
• if not? Sprint Planning = confusion, discovery..