New Daily Stand-Up (WIP)
The daily stand-up meeting is a daily morning meeting to help steer the teams daily and weekly goals.
The meeting should last no more than 30 minutes.
Before the meeting
The PM will audit the Support Desk and project boards to identify blockers and prepare specific discussion points, ensuring stand-up remains focused and efficient.During the meeting
We’ll have a quick run down of what everyone is planning on working on that day and go through the key points highlighted in the audit
Do you NEED a Stand-up?
If a business-critical issue is impacting the regular stand-up then consider delaying or even cancelling the stand-up. Also if it genuinely feels like the stand-up can be skipped then cancel it and provide information in Slack to steer any important tasks.
During the Meeting
After a brief window for pleasantries we’ll kick things off:
Freshdesk review:
The PM should have highlighted any tickets that need discussion and have the tabs ready prior to stand-up starting.
Review any tickets highlighted for discussion
Triage to GitHub or Basecamp: During the review, note down the tickets that require triaging to GitHub or Basecamp - this can be completed by the PM after stand-up
Engineers can raise any additional queries they may have that have not been highlighted, if necessary
For support tickets that are ‘stuck’ in Code Review or QA please note that these are the responsibility of the REQUESTOR not the REVIEWER to be complete and that, the REQUESTOR must then chase the REVIEWER to complete the work
Basecamp review:
The PM should have highlighted any required areas of discussion.
Review cards, threads or items highlighted for discussion
Triage any outstanding actions required
GitHub & QA/CR Review
Start with a quick and ‘holistic’ view of the ‘Team Dashboard’ https://github.com/orgs/mkdo/projects/11/views/1
Next, check all items in active 'Code Review' https://github.com/orgs/mkdo/projects/11/views/38
Make close attention to the Code Review, QA and Client Review columns to make sure that these are all properly assigned and can be moved forward
Finally review the In Progress column and clarify that team members are using the board correctly and have their active work in the correct place
Remember: At no point should the board become the sole focus of standup and any distractions issues or problems should be taken care of after the call has ended.
Harvest Review (TBD)
Review the Team View in Harvest to validate time has been tracked for the previous day or week
Note: It is especially important to review Harvest near the end-of-the month as client reports are generated in the first week of the following month and if data is missing at this point hours will be missed.
Roundtable and AOB
If anyone has any concerns that haven’t been touched on they may raise them now.
E.g.
“I have a question about how best to respond to a ticket”
“I’m not sure how best to proceed with this task”
We’ll end the meeting with a brief roundtable covering the following:
What you’re working on
Any blockers to your work
Your capacity and workload
End Meeting and Discuss Blockers or Issues
Blockers can be addressed immediately if the solution is simple (IE ‘I will talk to the client’), however if they need more in-depth discussion an agreement for the parties involved to have a meeting outside of this one can be arranged.
Branching Off Specific Meetings
At no point should a technical solution be discussed in the standup. Any specific project work or other discussions should be taken into a breakout call or scheduled for later that day.