The roles product people play
This post explores the product people roles of product management, product ownership and business analysis and identifies which titles fill those roles.
What is a delivery lead?
An exploration of the delivery lead role, its key responsibilities, its relevance to product people and different perspectives on the role.
Discovery Sessions: Start a project off right
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.
A product person’s guide to working with SMEs
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.
What is an agile business analyst
An excerpt from How To Be An Agile Business Analyst, a book that explores how to apply your business analysis skills in an agile manner so that your team solves the right problems with the right solutions.
How do you improve business processes as part of a digital transformation?
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.
The benefits and pitfalls of outcomes over outputs
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.
13 Examples of Internal Products
13 episodes from the This is Product Management podcast and the 100 PM podcast where the interviewee works in what I’d consider an internal product context.
Why context matters to product people
Your context drives and influences the practices you use. Here's why you need to understand context to pick the appropriate product practices.
Decisions in three horizons
A discussion of the decisions that occur in the strategy, initiative, and delivery horizons and how business analysts are involved with each decision.
How agile business analysts assess value
9th in a series about the agile business analyst. This post looks at how agile business analysts assess value and use that to determine subsequent action.
How agile business analysts help users implement a solution
8th post in a series about agile business analysts. This one explores how agile business analysts help users and stakeholders implement a solution.
How agile business analysts support delivery
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.
How agile business analysts build detailed understanding
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.
What does an agile business analysis plan look like?
An agile business analysis plan is an agreement within your team about what information is needed to build a shared understanding of your solution.
How agile business analysts define scope
Agile business analysts define scope by make commitments based on outcomes, and creating a backlog that represents a view of scope at a point in time.
How agile business analysts discover outcomes
A look at how agile business analysts discover outcomes in a measurable way to help guide them in determining the scope of their effort.
How agile business analysts get oriented on new projects
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.
What are the characteristics of an agile business analyst?
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.
How To Improve Your Business Analysis Skills
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.
What product owners need to know about business analysis
Business analysis skills help effective product owners focus on outcomes, build shared understanding, and make sure decisions get made.
Analysis with an Agile Mindset
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.
What is the difference between customers, users, and stakeholders?
When you develop products, you have to interact with customers, users, and stakeholders. To be effective, you need to understand the different perspectives.
Internal Product Management
Use Internal product management for products that you don't sell directly, but use to support business activities and sell your true product and service.