Deep Dive Models in Agile (Part 4): Business Data Diagram

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 Intelligence   Strategy  

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.

This week we are covering one of the key OPSD (Objectives, People, Systems, Data) bounding models, the business data diagram (following our previous entries on Process Flows, Feature Trees and Business Objectives Models). Other editions in this series will cover state models and decision models (you can always contact me if you would like to request additional models for this series).

What is a business data diagram?
Business data diagrams, or BDDs, bound the system from the data perspective. BDDs are also known as entity relationship diagrams or ERDs. BDDs are meant to convey a business view of how the key data objects for a product connect, and should be structured in a way that reflects how users think about the data.

The point of this model is not for designing back-end tables; this model should not represent physical relationships in a database, although it might be used to inform a database. The BDD instead allows the PO or BA to focus on what data is …

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