Learn how to leverage the platform to streamline your daily stand-ups. This article provides the adoption journey for a variety of users, tips for aligning your stand-ups with the platform adoption goals, and a checklist of key stand-up questions, practical guidance for using the platform (to get answers).
Guidelines for Engineering managers/leads/Project managers/Program managers (Admins/Editors in the platform)
1. Prepare yourself for the stand-up by checking out Trace to analyze the flags associated with artifacts executed in the current sprint
2. If you have enabled auto-resolution for evidence generation (for technology flags), review the progress of evidence generated by the platform in the recent past
3. Checkout the flags associated with an artifact (issue, PR, Feature branch, etc.), plan/review the resolution with the owner of the artifact
4. Flags that are not being auto-resolved, create evidence for flags in Jira (for technology flags) for resolution in current or planning sprint
Guidelines for Engineers (Viewers in the platform)
1. Work on the flags from the Jira evidence tickets, resolve issues based on assigned timeframe and based on recommended suggestions (by the platform)
How can you align your stand-up with the broader platform adoption goals?
The following questions can be specifically mapped with the Goals and objectives of using the platform daily to keep a check on daily progress:
Are the resources productive and well utilized?
PR summary and status reports, Code review summary and status reports, PR review pending for a build flag, Overloaded resources flag
How is the quality of the product (designs, requirements, code and test cases)?
Feature branch/PR Technology flags, test cases not ready flag, Development landscape deployment pending flag, PR process flag
Are there release risks with the product?
PR/Branch technology flags, code review summary report, 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/Branch technology flags
Misc. questions and places to find answers on the platform
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?
How can you get answers for these questions using Cubyts?
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:
Feature branch/PR summary and status reports
PR/Branch technology flags
Code review summary and status reports
Changing specifications flag
Test cases not ready flag
Planned hours exceeded flag
Overloaded resources flag
Development landscape deployment pending flag
PR process flag
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article