Agile techniques for software requirements: user stories, product backlog, design thinking, MVP minimum viable product, etc.
Agile development teams that struggle to keep track of UX work in the product backlog can utilize a separate backlog for UX. This method can help siloed teams where UX and development aren’t in direct communication. Separate UX backlogs do have pros and cons, which are discussed here.Read More
Specification by Example is a set of process patterns that facilitate change in software products to ensure the right product is delivered effectively. This book written by Gojko Adzic is based on the research of 30 teams that implemented 50 projects. The first part of the book introduces the Specification by Example concept… with examples, […]Read More
This video about requirements management in Scrum discusses how acceptance criteria can be added to Product Backlog Items individually in additional to an overall Definition of Done and why it may be a good idea.Read More
Why is it so hard to reconcile Agile approaches and long-term product planning? What causes the friction between product teams and stakeholders that prevents delivering desired outcomes as fast as possible? This presentation shares some research on the issue and gives a sneak-peak into ongoing experiments to solve this painful requirements problem.Read More
This video provides an example of agile requirements traceability. We discuss an example user story and show how detailed requirements captured as test tables can be used to build executable specifications and aid the design process. Finally we wrap up by a brief example of how we would track the progress of multiple user stories […]Read More
A lot has been said and written about user stories and their role in an agile context. But what are people actually writing as user stories? It doesn’t matter if you are agile or traditional in your approach, poorly written requirements are one of the major causes of project failure. This is where the Business […]Read More