The Characteristics of the Artifact to Use at Scale to Guide Manifestation of Value
From the Manifesting Business Agility Blog
by Al Shalloway
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.
Recent Posts
What is a Lean-Agile Coach?
My Approach to Sensemaking in Knowledge Work
Why if you are a PMP who understands the value of Agile your next workshop should be the Disciplined Agile Value Stream Consultant
My views (past posts) on cause and effect in complex systems
Transcend the thinking that scope, time and cost are in opposition to each other with Lean-Thinking
Categories
lean,
value streams
Date
Creating and deploying functionality to existing products in large organizations requires multiple teams to coordinate with each other in order to minimize delays in workflows both within and across these teams. The backlog item used by these teams must be designed to accommodate this. These must:
- be the minimum size that can be deployed while providing value in a manner consistent with the needs of customers and the business
- describe the overall behavior desired
- identify the capabilities needed to build and deploy them
- represent the next increment of an initiative to be deployed (this enables step-wise manifestation of the organization’s strategy)
- be able to be sequenced according to the value delivered and the cost/time of creating it
DA calls this the Minimum Business Increment (MBI).
Whereas the MVP is about discovering what product would be of value, the MBI provides the next chunk of value for an initiative to be deployed. MVPs are discovered and created by a team. They start small and expand. MBIs are focus on the next incremental value to be built while being used to coordinate multiple parts of the organization to get it deployed quickly.
Posted on: March 26, 2020 09:20 AM |
Permalink
Comments (3)
Please login or join to subscribe to this item
Alexandre Costa
Scrum Master| Integer Consulting - Pictet technologies
Loures, Portugal
Hi Al, I agree with you generally.
I can only give has example my company, due to the nature of the products ( self-service finance machines) all teams of the several departments must participate in the creation of the MVP ( the minimum value product that the client accepts) and then after creation and release of the Product we use the terms MBI to release valuable increments to the business again involving all teams in a coordinated effort.
The particularity of the MBI is that must pass in two quality processes , our process of quality and because is a financial product must pass also in a process of quality Certification performed by the customer.
This several times is a challenge and create bottlenecks, because we are more advance in deliverables (MBI) than the customer is prepared to accept.
Alexandre
Al Taylor
I.T. Contractor| Independent
Waterloo, Ontario, Canada
good discussion! I get MVP & MBI. I am an old school developer...pretty much what I want to know when I get up in the morning is 'What do I build today / What value do deliver today' and I like simple answers...:).
Please Login/Register to leave a comment.
|
What a waste it is to lose one's mind. Or not to have a mind is being very wasteful. How true that is.
- Dan Quayle
|
