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.

This session talks about how to understand your customers – how they’re behaving, how capable they are of learning and changing, how they make decisions, what they care enough about to pay money or attention to fix. It’s not easy.

Sharing low fidelity user-interface prototypes with project stakeholders is a great way to transfer knowledge and get buy-in early from them. A low-fidelity prototype is a prototype that is sketchy and incomplete, that has some characteristics of the target product but is otherwise simple, usually in order to quickly produce the prototype and test broad concepts.

Modern software development approaches like Agile support a strong collaboration between all member of the software development team, software testers and business analysts included. Even if you don’t use a method like Behavior-Driven Development or Specification by Example, checking the fact that you will be able to actually test your requirements is a good thing. In his article, Richard Ellison share some best practices to reviewing requirements for testability from the point of view of a software tester.

The new MetaEdit+ 5.5 brings collaboratively created models to GitHub and other version control systems. Modeling and version control both play key roles in industrial-scale software development. However, most modeling tools and version control systems fail to work well together. Anyone who has tried merging model files knows it is a nightmare. Others curse the modeling tools that lock them out while another user edits a set of diagrams.

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 across our scrum or kanban wall.

This video discusses the perfectly-formed requirement, which should be unambiguous and testable. It presents the Snow Card, focusing on the requirement, rationale, fit criterion, and supporting materials.