Please enable JavaScript.
Coggle requires JavaScript to display documents.
Value in Software - Coggle Diagram
Value in Software
Bloat
80% of value from 20% of features
Complexity problem
Maintenance Problems
UX problems
Matrix
Most wanted, low cost
Desired, risky
Harmful (no value, costly)
Bloating features
Types
Financial
Business Perspective
Customer
Product perspective
Internal business proc.
Project Perspective
Innovation and Learning
for whom?
User?
Project?
Value-Based Req Engineering
All Stakeholders Included :world_map:
Value-based Feature Selection
Rodriguez, Urquhart 2020
Dimensions
Company Strategy
Strategy of company
Portfolio Impact
Architecture/Tech
Complexity
Product Architecture
Development Capability
Cost/Efficiency
Development
3rd party
Economic
ROI
Market Share
Is this diff. from competitive edge
Market Competition
Competitiveness
Time to market
Quality
UX
simplicity vs blingy
Customer
Satistfaciton
Customer
End-user
Market
OK TO ADJUST WEIGHTS ASYMETRICALLY
Type of feature
Mandatory
Basic customer
Business Case
Non-Mandatory
Nice ot have
Internal for tech improvement
e.g. cleaner code
Success-critical?? Stakeholder
Business
Developer
Product Owner
Feature Def’n
Req
Functional
Non-Functional
Distinguishing char
Characteristic of interest to
End-Users
Other Stakeholders
Previous Development
(waterfall)
Requirements Into Code
Value separate from Efficiency/Cost