Deep Dive Models in Agile (Part 6): Decision 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  

This series provides valuable information for the product owner community to use additional good practices in their projects. In each installment, 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.

This is the last paper in this series and covers decision models, which include both decision trees and decision tables. Other editions in this series have been process flows, feature trees, business objectives models, business data diagrams and state models.

What is a Decision Model?
Decision models include two RML system models (decision trees and decision tables) that detail the system logic that either controls user functions or decides what actions a system will take in various circumstances.

Like state models, these two models are covered together here because they show the same information in different formats. Oftentimes, a PO or BA will use only one or the other of the two decision models based on circumstances:

• Decision tables are used when the PO or BA wants to ensure that every permutation of applicable decision choices has been explored.
• Decision trees are more consumable for business stakeholders and are typically used to show a collapsed view of a decision tree by only modeling the decision choices that lead to an outcome.

…

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