Agile techniques for software requirements: user stories, product backlog, design thinking, MVP minimum viable product, etc.
User stories are not a highly documented series of requirements but rather a reminder to collaborate about the topic of the user story—in other words, in agile development (good agile at least), the documentation is secondary to the collaboration. Source: “New to User Stories?“, William F. Nazzaro and Charles Suscheck, ScrumAlliance.orgRead More
The article “<a href=”http://www.methodsandtools.com/archive/archive.php?id=17″>Agile, Multidisciplinary Teamwork</a>” by Gautam Ghosh presents techniques and tools used to create requirements with a team composed of the different participants of agile projects.Read More
This article “Business Analysis in Extreme Programming” describes the myths associated with having business analyst between the customers and the development staff. This approach is indicative of agile processes, in which the questions is asked how can we avoid confusion and get closer to the source of information?Read More