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

How to manage complexity - don't

Improving Scrum by Attending to Flow, not Merely Using It

The Difference Between Inspect and Adapt and Plan do Study Act (PDSA)

Random thoughts about Scrum Guide Based Scrum

The Iron Triangle Constraints Are Misleading



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 (7)

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.

Insightful, thank you!

Very insightful, thanks Al !

Joshua's note here is important about the MVP. Getting to a release early for feedback and requirement refinement to me is an important step. What do you see in the requirement identification quality when it falls sort?

MVPs and MBIs are both important. MVPs are when you are discovering what a product should be. MBIs are about extending existing products. See the link in the first line for more.

Please Login/Register to leave a comment.

ADVERTISEMENTS

Half this game is ninety percent mental.

- Yogi Berra

ADVERTISEMENT

Sponsors

Vendor Events

See all Vendor Events