Agile
Agile techniques for software requirements: user stories, product backlog, design thinking, MVP minimum viable product, etc.
Non-Functional Requirements: Do User Stories Really Help?
This interesting article by Rachel Davies discusses if user stories can be used to express non functional requirements in agile software development projects.
Read More
The Product Owner on One Page
Roman Pichler crafted a nice diagram that summarizes on one page the product owner’s responsibility together with the role’s key activities and artefacts.
Read More
My Product Owner Will Kick Ass
This blog post is about what a great Product Owner should be like.
Read More
User Stories are a Reminder to Collaborate
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.org
Read More
Agile, Multidisciplinary Teamwork
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
Business Analysis in Extreme Programming
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