A look at how discovery sessions help you to get you project off to a good start by making sure your product solves the right problem.
Some experience backed advice on how product people interact with subject matter experts (SME) including who should your SMEs be and how to work with them.
When your organization is in the midst of a digital transformation, one thing you do is try to improve business processes. Here's one way to do just that.
I often suggest that you focus on outcomes over output, but never explained why. Here's a look at the benefits and pitfalls of a focus on outcomes.
8th post in a series about agile business analysts. This one explores how agile business analysts help users and stakeholders implement a solution.
No matter how good they are at describing backlog items, agile business analysts need to work with their rest of their team as they deliver the solution.
Sixth in a series of posts on the agile business analyst. This one explores how to build a shared understanding about the details of your solution.
An agile business analysis plan is an agreement within your team about what information is needed to build a shared understanding of your solution.
A look at how agile business analysts discover outcomes in a measurable way to help guide them in determining the scope of their effort.
As an agile business analysts starting a new effort, take some time to get oriented to the context in which you’re working and people you’re working with.
You're an agile business analyst when you focus on outcomes, use short feedback cycles and adjust when and to what extent you use analysis techniques.
Business analysis skills are helpful for any product person, even if you aren’t a business analyst. Here are some sources from our partner Bridging the Gap.
Business analysis skills help effective product owners focus on outcomes, build shared understanding, and make sure decisions get made.
This lightly edited excerpt from Beyond Requirements:Analysis with an Agile Mindset describes a typical approach to analysis in software product development where teams exhibit an agile mindset. It places into context most of the techniques described in the technique briefs on the site. This approach to analysis happens in four steps.
When you develop products, you have to interact with customers, users, and stakeholders. To be effective, you need to understand the different perspectives.