Home » Archives

Content in the Videos category

[2 Oct 2019 | No Comment | ]

This short videos explains the difference between the 3 main types of user interviews (structured, semi-structured and unstructured), and at what stages of a UX design process it makes the most sense to use each.

[5 Sep 2019 | No Comment | ]

This presentation discusses the various different requirement elicitation methods. These techniques include brainstorming, interview, survey, and many more! This video illustrates the challenges of requirement elicitation and should allow you to choose the right elicitation techniques for your software project.

[7 Mar 2019 | Comments Off on Escaping Features Factory with Outcome-Oriented Roadmaps | ]

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.

[19 Feb 2018 | Comments Off on Decoding Your Customers | ]

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.

[14 Dec 2017 | Comments Off on Presenting Prototypes to Stakeholders | ]

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.

[3 Feb 2017 | Comments Off on Introduction to Agile Requirements Traceability | ]

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.

[14 Jan 2016 | Comments Off on The Perfectly-Formed Requirement | ]

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.

[5 Jan 2015 | Comments Off on Getting Well Written Requirements from Business Analysts | ]

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 Analyst comes to the fore.

[13 Nov 2014 | Comments Off on Definine Customer Value in User Stories | ]

User Stories, designed to keep teams laser-focused on customer needs, serve as THE driving force behind delivering valuable, high quality features, fast. This presentation discusses how to write great agile software user stories by defining customer value and keeping teams laser-focused on needs.

[3 Sep 2014 | Comments Off on Making Product Decisions with a Practical Value Model | ]

Working with stakeholders (customer, business and technology perspectives) to effectively and efficiently deliver high-value products begins and ends with value. “Value” is the beacon, watchword, end game, justification and mantra for Agile. It is the basis of the big “why”.