 |
|
User stories are a technique taken from the agile development playbook that can easily be applied in traditional systems development and maintenance. User stories help you document needs in a structured way, from the users’ perspective. They’re a good basis for test cases, so as to support integrated requirements management and testing. In this article, you’ll find concrete advice based on our own experiences developing the requirements and testing tool ReQtest for how you can make user stories the basis for requirements management and testing.
Read the full story »
Learn how to understand Product Portfolio management using Monte Carlo technique. Given a number of product options available, which one should we start first? How do we know whether one thing is better to do or not. Maybe we should work on all the things simultaneously! Let’s add more people to get everything done faster!
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.
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.
The Acceptance Testing syllabus is joint effort between IQBBA (International Qualification Board for Business Analysis) and the ISTQB (International Software Testing Qualifications Board). This syllabus will facilitate the efficiency of acceptance testing through the joint training of business analysts / product owners and testers.
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.
RSS Feed
Twitter