Sprint Cycle

Formal meetings follow this schedule per sprint cycle regarding the Seko team:

Start of cycle

Week 1

Monday

Internal backlog refinement - refine stories, ensure all design/stories are consistent and well enough detailed

Wednesday

1-2-1 catchups - 15 minutes conversation about how things are going; good, bad & ugly

Thursday

Backlog refinement with Dev Team Project Manager (Semyon) for upcoming sprint and following sprints:

• Go through all stories in the backlog every time to ensure consistency and check any notable changes

• Timebox meeting to limit time but not limit on number of stories assessed

• Verify that stories are in good enough state for story points to be allocated

This meeting forms a definitive list for the dev team to task up and allocate story points in time for sprint planning. Five days in advance of the Sprint Planning meeting.

Friday

Internal retrospective - to iron out issues, learn and move forward in the process

Week 2

Monday

Internal backlog refinement - as above

Wednesday

Sprint Demo

Sprint Planning with whole team. Next sprint starts.

1-2-1 catchups

Thursday

Backlog refinement with dev Project Manager for following sprint - as above

Friday

Internal retrospective - as above

…. and repeat