Feature Fit Risk
Risk that the needs of the client don't coincide with services provided by the supplier.
Part Of
Reduced By Practices
- Analysis: Analysis can help ensure technical solutions fit the problems they're designed for.
- Demo: Showcases the product to ensure it meets client expectations and needs.
- Prototyping: Allows early validation of features and design with stakeholders.
- Release: Putting new features in the hands of users can make your product fit their needs better.
- Requirements Capture: Ensures that features align with client needs and expectations.
- Standardisation: Ensures that the features conform to predefined standards, reducing variability.
- User Acceptance Testing: Ensures that the software meets the client's requirements and expectations.
Attendant To Practices
- Automation: The automated process might not capture the variability of requirements of the original approach
- Design: Too much design up-front can create problems meeting feature requirements.
This is the risk that the feature that clients want to use in the software isn't there.
- This might manifest itself as complete absence of something you need, e.g "Why is there no word count in this editor?"
- It could be that the implementation isn't complete enough, e.g "why can't I add really long numbers in this calculator?"
Feature Fit Risks are mitigated by talking to clients, product development and delivery (as shown in the above diagram). But that leads on to...