Business Value Vs Complexity
Here s a simple path.
Business value vs complexity. Business value complexity is an effective methodology that lets the product team evaluate all the initiatives according to how much value each will bring or how complex it would be to implement them. Do business strategy user research make a list of features create features code features somewhere in that list of features step is a big transition from mushy research to getting down to work. For more information on complexity analysis and for the strategic corporate wide approach refer to conquering complexity in your business mcgraw hill 2004 overview of complexity tools.
Download the business value complexity ppt template to provide a deep insight into the concept to your team. Defining the business value measures. The business value can include anything from revenue generation more visibility traffic more savings etc.
Initiatives are then plotted on a quadrant and prioritized accordingly. The value versus complexity model enables product teams to recognize which features have the potential to bring the most positive results and the complexity involved in implementing them. Business value could be anything ranging from revenue generation more traffic more visibility more savings.
This approach is rather common many product managers daily go through this assessment instinctively. It considers research and business strategy along with initial technology estimates. Business value is key to it success achieve more success and boost the reputation of your it organization when you deliver quantifiable and tangible business value for your company.
Figure 1 candidate features scored against value and complexity. The purpose of these tools is to help you diagnose and quantify complexity opportunities in your business unit or value stream. The value complexity matrix i like to think of projects as a journey from the abstract to the concrete.
The value vs complexity model lets you evaluate every opportunity based on its business value and relative complexity to implement. Product managers can use this information to allocate developers resources and time to the highest priority features.