Previous
¶ Solution Options
¶ What it is
Solution options are to be defined based on the change strategies and verified requirements to identify the solution approaches that achieve the desired future state.
¶ Why it is useful
Solution options must be assessed to help decision-making on which one to adopt and move on into the production phase smoothly.
¶ When to use it
When change strategies and requirements are defined, the team should consider possible solutions. See the figure - solution options are to be defined after the requirements are verified and signed off by the stakeholders and before moving on to PoC.
¶ How is it done
- Review the change strategies and the verified requirements to decide the possible solution components. The scope may be the complete list or just part of the requirements.
- Allocate the requirements to each component based on relevance.
- Form solution options with different combinations of components
- Assess each option mainly from the perspectives of:
- Performance - predict how much the option may contribute to the business value
- Limitation - analyse the risks and cons of an option
- Recommend the best option, or recommend the actions to increase the value of options
Solution options analysis is not performed only by business designers or analysts but also supported by the professional teams of marketing, technical, operational, and so on.
¶ Do's & Don't
Do's
- Be flexible when setting up solution components, so you will have fewer limitations later when building solutions.
- Be always ready for trade-offs.
- Be an end-user while assembling a reasonable solution, not a software builder.
Don't
- Don’t always try to put all the requirements into the product; always think about values and costs.
- Please don’t give up a solution option easily but consider how to increase its value.
¶ Tools needed
¶ Example
