BROADCASTS.com

Software Engineers require instructions in order to build apps and tools. And most of us don't know what these instructions should look like. One of the ways these instructions can be shared is in the form of user stories, and it's not just about writing a bunch of text, but comprehensive check list of how this should be structured so the right information can be given to the builder. Ofcourse its a two way effort Product and Engineering need to work closely to build up such requirements so they make sense from a functionality perspective, and a technical perspective.

This session is based on the article linked below:

https://martinfowler.com/articles/product-backlog-building-canvas.html