Deep Dive Models in Agile (Part 3): Business Objectives Models

Candase is a Senior Product Manager at Seilevel and a PMI-Agile Certified Practitioner who trains and coaches product owners, ScrumMasters and business analysts on agile approaches as well as championing products in those roles for clients.

  Agile   Business Analysis  

This series provides valuable information for the product owner community to use additional good practices in their projects. In each installment in this series, we take one of the most commonly used visual models in agile and explain how to create one—and how to use one to help build, groom or elaborate your agile backlog.

Now for something different in the series: business objectives model. If you missed the first (process flows) or second (feature trees) editions, check them out. Other editions in this series will include: business data diagrams, state tables/state diagrams, and decision trees/decision tables.

What is a business objectives model?
A business objectives model is an RML objectives model that iterates through the business problems and business objectives of a project until arriving at the product concept (the solution the project will build). The business objectives model for a product or project aligns the team on exactly why it is undertaking the project/product and what business benefit will be realized from it.

Each business objectives model has four main components:

1. Business problem: Any issue that is preventing the business from achieving its goals.
2. Business objective: A quantifiable way that the business will know when the business problem has been solved.
3. Product concept: The solution the team has decided to build or do on order…

Please log in or sign up below to read the rest of the article.