2 week sprints.
Weekly PAR review. Small group reviews new defects.
BACKLOG GROOMING (every 2 weeks):
- Stories: discuss story and using pointingPoker.com to point. Goal is to create a score to help estimate relative complexity. Stories are items that add value for customer (e.g., product feature, performance improvements, etc.)
- Tasks do not get pointed. Tasks are items good things to do, but does not correlate directly to a benefit for a customer.
- Review defects (high level)
- Move priority items to top of backlog
SPRINT PLANNING (every 2 weeks):
- Occurs at the start of a sprint. 4 hrs allocated and then we officially start the sprint.
- Assess total team hours available
- Add items to sprint and check team hours remaining
- For stories, create sub-tasks
- For defects, set hours
START SPRINT
- Tickets are prioritized
- Tickets are not assigned so anyone can take
- If a bug is found during a story, create a BUG subtask and take hours from the story's time bank.
SPRINT RETROSPECTIVE (when sprint ends):
- Discuss good and bad points
- Action items (past and future)
No comments:
Post a Comment