Good to Great user stories with Story cubes

A user story is a foundation in SCRUM, it is simple and can be written in a minute. The non-functional requirements, like security, usability, or regulatory needs are defined as acceptance criteria or in definition of done.
These requirements serve as important constraints for the team – leading it to a solution. Non-functional requirements are not optional, yet many a times these are missed the common reason being “Everybody knows’. Assuming the teams understand non-functional constraints leads to a lack of explicit definition and subsequent failure to define them.
What if we could use leverage games to uncover these non-functional requirements and explicitly define them?
What if we could make this entire activity fun rather than a stressful exercise?
Can this improve collaboration within the team and with customers?
We will find out…
Structure of the session:

1. Ice breaker using story cubes – 5 mins ( table wise assuming we have 4 tables )
2. What is a good user story and how you can make it great ? – 3 mins
3. Primer on non-functional requirements, this will be backed by research and personal stories ( 2) why non-functional requirement elicitation is important – 5 mins
4. Introduction to Story cubes – 2 mins
5. Demo of how story cubes can help in eliciting non-functional requirements – 5 mins
6. Each table will have a user story, they will roll a story cube and come up with non-functional requirements to make the good user story “great” – 10 mins
7. Debrief the non-functional requirements uncovered – 10 mins
8. Retrospect as a team on how this activity can be made more effective– 3 mins
9. Some SME tips on how to – 2 mins
a. Leverage Story cubes for virtual teams
b. What is your learnings ? How can you use this elsewhere ?
c. Scale