Learn how to leverage Cubyts to streamline your daily stand-ups. This article provides a checklist of key questions, practical guidance for using Cubyts, and tips for aligning your stand-ups with your broader Cubyts goals.
How do you use the platform while the stand-up is on?
- Encourage developers to group by assignee and address flags that are under their name
- Inform them about the order of priority (eg: Deployment Flags for active sprints could be prio 1)
- Ask them to set up one-on-ones in case there are blockers
- Incentivise fixing of flags
Questions checklist for an effective stand-up:
The Scrum Master can review the flags and reports on Cubyts to get answers to the suggested questions and discuss the same with the respective assignees/owners during the stand-up or as a one-on-one post the stand-up
Are draft PRs ready as soon as stories are assigned to developers?
How are the PRs progressing?
Are there any technical issues (code review comments, code smells) to be addressed on an ongoing PR?
How is the review progressing?
Are reviews effective?
Are developers fixing the review comments on time?
How big are the PRs turning out to be?
Are developers testing their work making deployments or creating builds?
Are specifications changing after development has started?
Have test cases arrived for stories?
Can an issue spill over?
Are my developers in active sprint overloaded?
Using Cubyts to answer the questions above.
The following sources can be used on Cubyts by Scrum Master or Developers to determine the answers for the questions asked in the section above:
PR overview and status dashboards
PR code smells flag
Code review overview and status dashboards
Changing specifications flag
Test cases not ready flag
Planned hours exceeded flag
Overloaded resources flag
Development landscape deployment pending flag
PR review pending for a build flag
Alignment with goals and objectives
The following questions can be specifically mapped with the Goals and objectives of using the platform and determined daily to keep a check;
Are the resources productive and well utilized?
PR overview and status dashboards, Code review and status dashboards, PR review pending for a build flag, Overloaded resources flag
How is the quality of the product (designs, requirements, code and test cases)?
PR Code smells flag, test cases not ready flag, Development landscape deployment pending flag, PR review pending flag
Are there release risks with the product?
PR code smell flag, code review dashboards, changing specifications flag, test cases not ready flag, overloaded resources flag, Development landscape deployment pending flag, PR review pending for a build flag
Have the technical debts reduced?
PR code smells flag