There is no business analyst role in the Scrum Agile project management framework. Based on this fact and some perceptions about Agile, Roland Hesz tries to answer the questions “Do we need a business analyst on an agile project? Are there Agile business analysts?”.

Business is coming under increasing pressure to adopt agile practices to reduce costs and deliver more quickly. Agile Analysis describes your requirements and associated features using stories. Typically for use with agile development but it supports structured methods too giving a common analysis method throughout the organization.

Agile uses mostly user stories to capture requirements. In his blog post, Jean-Jacques Dubray explains that there is a problem with user stories because they tend to focus on the solution and not on the problem definition.

This short video presents the Mike Cohn’s Iceberg Analogy for User stories. It discusses User Stories and the Backlog, how you can perform grooming and rightsizing and how you should establish a grooming cadence for sprint, release and roadmap.

System-building projects which fail (which is many of them) do so more often because they build the wrong thing, not because they do a bad job of building the right thing. The Agile community has developed a range of techniques for making sense of system requirements and capturing them in artifacts that are familiar and understandable by business, useful to developers and informative to managers.

This short video discusses what makes a good Product Owner in a Scrum Agile team, how to engage your Product Owner and some pitfalls that can come with the role.

A user story is a tool to describe the product functionality, but it is less useful suited to describe in detail the user interaction. Agile scenarios and storyboards are tools you need to describe the interaction steps. In his post, Roman Pichler what scenarios and storyboards are, how they can be used effectively in an Agile approach and how they relate to user stories.

Learn how to build outcomes over outputs as a key strategy to building great products using the Target Outcome framework. The talk will cover why the metrics we often use are flawed, how to create useful value metrics, track value incrementally and do guerilla user testing.

A user story map is a technique created by Jeff Patton where you arranges you user stories into a useful model to help understand the functionality of the system. In this blog post, Steve Rogalsky explains how to create a user story map.

We are designers, and we know how important design is to the success of our projects. We’re also agile! We believe in making incremental changes based on user testing. But there are some parts of the process we’re just not very good at yet. It’s usually still hard to achieve dramatic, site-wide style changes in an incremental and agile way, and most of us still run into “redesign” projects eventually.