How to use Cubyts for Stakeholder Review meetings?

Learn how to leverage the platform to streamline your stakeholder review sessions. This article provides the adoption journey for a variety of users, tips for aligning your stakeholder review sessions with your broader platform adoption goals. and a checklist of key questions, practical guidance to using the platform (to get answers).

How can you align your stakeholder sessions with the broader platform adoption goals?

The following questions can be specifically mapped with the Goals and objectives of using the platform and determined daily to keep a check;

Is the team planning their work well?

Team reports, Delivery reports, Overloaded resources flag

Are the resources productive and well utilized?

Code review/PR reports.

How is the quality of the product (designs, requirements, code and test cases)?

Missing test cases, design quality flag, PR code smells flag, deployment flags

Are there release risks with the product?

Feature branch/PR technology flags, PR and code review reports, overloaded developers flag, design quality flag

Have the technical debts reduced?

Feature branch/PR technology flags

Misc. questions and places to find answers on the platform:

The Scrum Master/Engineering Manager can create a template based on regular meeting cadences and review Cubyts before a review session. This will ensure that the sessions are answering all the questions, highlighting anomalies and blockers in an organized format. 

Here are some of the questions that can be used;

• Issues jumping sprints repeatedly causing delays in the feature delivery

• Requirements that can be picked up immediately, can they be prioritized?

• Overloaded team members, resource planning

• Unreleased stories, need prioritization

• Requirements quality needs to improve

• How are resources performing?

• How is my feature progressing?

• Is the product quality improving?

• Are the technical debts reducing?

Using Cubyts to answer the questions above;

The following sources can be used on Cubyts by the Team to determine the answers to the questions asked in the section above:

• Design handoffs below quality levels flag

• Issue extended beyond sprint

• Overloaded resources flag, Team reports

• PR and Code review reports, team reports

• Delivery reports

• Missing test cases flag, design quality flag, Feature branch/PR technology flags, Code review dashboard