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

Collaborating With Stakeholders

To make UX research and requirements gathering more efficient and effective, you have to get everyone in the software development team and the user representatives involved. When the teams understand user concerns and usability issues, they become better at preventing problems.

Read More
Videos

Product Managers Best Practices to Build Highly Effective Teams

This talk shares product management best practices and experiences with you in hopes they will help you in your product development journey to build highly effective teams. It covers key topics including (a) working together, (b) managing and prioritizing the work, (c) customer discovery and readying stories, (d) measuring what and how we work, and […]

Read More
Videos

Mapping Customer Experiences: From Insight to Action

Visualizations are a key tool that help organizations change their perspective. Though no silver bullet, mapping experiences diagrams seek to align customers’ experiences with how businesses operate. You are surely familiarly with things like customer journey maps, service blueprint, experience maps, and more.

Read More

Copyright © 2009-2021 Martinig & Associates