scrum

Scrum 🏉

An iterative process for delivering incremental value

An agile framework

Work is organized and progresses from a higher, more general overview to finer details and shorter time periods.

Vision > Roadmap > Release Planning > Epics > Sprints > User Stories

Product Backlog
- have a DEEP backlog:
  - Detailed appropriately
  - Estimated
  - Emergent
  - Prioritized
Sprint Backlog
Epics - Place holder for stories
Stories
- INVEST in stories:
  - Incremental
  - Negotiable
  - Valuable
  - Estimatable: stories are assigned a number a consensus of story points based on complexity. Fibonocci numbers are often used for scale. Points are assigned to user stories during Sprint Planning.
  - Short
  - Testable
- Includes Acceptance Criteria (AC), or test cases. "As a role, I want to goal, so that justification"
- manage size:
  - separate CRUD stories
  - main flow first. altertnates later.
- Spike stories: research & development, protyping, proof of concept. Throwaway. Not technically a story. Not pointed.
Sprints
- Timeboxed: usually 2 weeks
- Estimated: includes enough points to meet velocity
- Includes a demo and a retro

Planning - 1 - 2 hr. Involves planning poker
Daily Standup - 15 min. "Did/Doing/Blockers"
Sprint Demo - Product owner decides if there is sufficient value to release the product.
Sprint Retro - "Start/Stop/Continue"

Backlogs: Must have/Nice to have/Won't do
- Product - Belongs to Product Owner
- Sprint - stories etc committed to by the team for this sprint
Burndowns
- Release - calculates Release Target Date
- Sprint

DOR - Definition of Ready. what is required for a story to be ready
MVP - Minimal Viable Product. The smallest unit of value that can be released as a product
Velocity - the total number of story points in a sprint
TACOS - Titles And Ceremonies Only Scrum

Trainings

Books