[ ] Improve structure of scrum ceremonies (list below)
[ ] Book a meeting define team meeting norms (I'll book a meeting)
[ ] Agree on updated pipeline process so that general concerns don't come up in meetings. (I'll book a meeting to review the process flow I've documented so far)
Refinement sessions
We review stories that have had a first round refined, which means Colin has drafted it, Sandra, Kevin, Justin, and Liv have provide feedback. Then the entire team reviews it during backlog refinement, where it will be reviewed, updated, and estimated. Estimates completed before a team refinement meeting will be based on t-shirt sizing. Sm=32, Med=64, Lrg=96
Sprint Planning
Process
Review prior velocity
Review team availability (holidays, etc.)
Discuss incomplete stories or defects from the previous sprint. Exclude or prioritized.
PO presents the list of Stories in priority order
Each story is confirmed be "Ready"
Missing tasks are added to each story
Final round of estimation and confirmation
Stand ups
The first 15 minutes - Only the following comments. We can say that I'd like to talk about during the second 15 minutes. But, the request is to have no conversation.
What task I worked on yesterday - Zenhub ID/Summary
What task I planned to work on today - Zenhub ID/Summary
What is blocking me from completing my task described in 2.
During the second 15 minutes
Everyone will have heard the topics raised during the first 15 minutes, and have a choice to stay or not
Sandra may request all of us to stay for an important update when she gives her yesterday/today update. But, it should be explicitly stated if we "need" to stay.
I'll say the first 15 minutes is now down and folks are free to go
Retrospective 60 minutes
10 mins - review previous retro
15 mins - brainstorm
5 mins - dot voting
5 mins - conclude top items
25 mins - planning next steps to resolve top items
Proposed Approach