Project Management

The Most Compelling Reasons for Using the Minimum Business Increment

From the Manifesting Business Agility Blog
by
This blog concerns itself with organizations moving to business agility—the quick realization of value predictably and sustainably, and with high quality. It includes all aspects of this—from the business stakeholders through ops and support. Topics will be far-reaching but will mostly discuss FLEX, Flow, Lean-Thinking, Lean-Management, Theory of Constraints, Systems Thinking, Test-First and Agile.

About this Blog

RSS

Recent Posts

The Most Compelling Reasons for Using the Minimum Business Increment

The FLEX Playbook For SAFe

How Disciplined Agile and FLEX Improve SAFe

The Disciplined Agile/FLEX 2-step Approach. Part IV of VI – When have small to medium size organizations with well-defined teams

Why Disciplined Agile Uses Work in Process and not Work in Progress



I have found the Minimum Business Increment (MBI) to be one of the most useful concepts in 20+ years of doing some form of Agile, An MBI is the smallest increment of value that can be created for which value can be realized by an internal or external customer. MBIs are defined from initiatives for specific market segments or customers. They are a focus on what to build and release the quickest.

Whereas MVPs are about discovering whether a new product is viable and what it should be, MBIs are used to define the smallest increment of value to realize for existing products. MVPs are typically built by small teams that can pivot, whereas MBIs are used to coordinate the multiple teams required to create them. MBIs can also be used to help define dedicated product teams for the initiatives they come from. 

Cost of delay (and therefore WSFJ) can be more effectively done on MBIs than on epics, since not all of an epic will be released at one time and features often are not releasable on their own.

Multiple teams can align around MBIs when making decisions on which item to work on next. While true for features, multiple teams should not be required to build a feature.

Summary in table form:

Posted on: April 28, 2020 10:59 AM | Permalink

Comments (3)

Please login or join to subscribe to this item
Very interesting., thanks for sharing

I got new knowledge from it. Thank you

There is always intense focus on MVP and when you are supposed to see it, it falls short. This is intriguing.

Please Login/Register to leave a comment.

ADVERTISEMENTS

"One morning I shot an elephant in my pajamas. How he got into my pajamas I'll never know."

- Groucho Marx

ADVERTISEMENT

Sponsors