Crash Course: Good to Great User stories with Story Cubes

**Registration required on Leanpitch portal: https://bit.ly/33erbhO **

One way to capture requirements is through user Story. In Organizations, where they use Scrum, user stories can be used to represent Product Backlog Items. 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 the 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 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.