Creating effective Product Requirements documents takes a lot of effort, often undermining whether they actually get done. Much of what is written is rarely implemented and the details are not always static as they change when the team learns what it really wants. This session would sort through what is really needed in a Requirements document focusing on what actually gets done.
is there anyone who would like to faciliate / present on this topic? Please email firstname.lastname@example.org