E-book content

Every Product Owner, Product Manager, Project Manager and Business Analyst must know how to describe software requirements (items that will form the Product Backlog), as well as every Developer or Engineer must know how to read these PBIs.

Knowing which template is more appropriate for each requirement or each type of PBI is essential for developing and delivering a software product, avoiding waste and ambiguity.

This E-book  ‘5 Ways to Describe Software Requirements‘ has been created with the aim of sharing my experience with these professionals and it presents a collection of templates that are most used to describe software requirements.



My name is Leandro Bodo, I've been working in digital transformation for about ten years, delivering software solutions for a variety of organisations such as Beyond Petroleum (BP), Coca-Cola, Unilever, GSK, Smithers e Forest England. Currently, I work as a Senior Technical Product Owner for a Digital Agency in the UK.