Deep Dive Models in Agile (Part 1): Process Flows

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  

We have resources available on how visual models are great in an agile environment and which visual models have the most impact on requirements for an agile team. However, we often get requests for additional details on how to utilize visual modeling on an agile project.

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.

The first in this series is the process flow. Other editions in this series will include: business data diagrams, state tables/state diagrams, decision trees/decision tables, business objectives models and feature trees.

What is a process flow?
A process flow is an RML (requirements modeling language) people model that describes the steps that a user takes to accomplish a goal or finish a task. This model is great for understanding the project’s current and future state processes of the business—and for understanding those processes from the end user’s point of view.

RML process flows are created in levels in order to both be able to see the big picture of a process within a system as well as drill down into the details of a single, more detailed process.

This is in …

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