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.

This presentation covers:
* Why is the Business Analyst so important in the agile space?
* Why is it missing from most agile approaches?
* Why is it vital to write good requirements and user stories?
* What can go wrong without a Business Analyst?
* How does the Business Analyst blend in with the rest of the team and other stakeholders?
* What is the difference between a Business Analyst and a Product Owner?

Video producer: http://agilekrc.com/

Videos

Design Thinking Activities

This video explains that the six stages of the design thinking process can be supported by a very wide range of UX methods and activities. Don’t limit yourself to the most commonly mentioned methods.

Read More
Videos

Wardley Maps: Business Analysis, Experimentation & Evolution

This presentation explains how Wardley Maps were used to inform the always evolving strategy for the modernization of Ticketmaster’s core ticketing platform not only in terms of technical capabilities and architecture but also process maturity, organizational design, and more.

Read More
Videos

Analytics vs. Quantitative Usability Testing

Analytics and Quantitative Usability Testing UX research techniques help you gain quantitative insight into user behavior. However, each method provides different types of information and can answer different kinds of research questions.

Read More

Copyright © 2009-2021 Martinig & Associates