Should-have requirement
A should-have requirement matters but is not essential to the delivery scope under consideration. An accepted workaround can initially allow use.
A should-have requirement is used here for an important requirement whose absence does not make the delivery scope unusable. In MoSCoW this is Should Have. An accepted, potentially cumbersome workaround may exist.
A hypothetical portal should allow convenient repeat orders. For the launch under consideration, the team temporarily accepts manually rebuilding the cart. Repeat ordering remains important but does not block this launch. The extra work needs to stay visible in the decision.
Should-have therefore does not mean insignificant or definitely removed. Nor does the label alone guarantee delivery. Agree on scope, timeframe and how deferrals are handled. Something initially classified as should-have may become essential for a later increment.
Sources
Related terms
- Must-have requirementA must-have requirement is essential to the agreed delivery scope. Without it, the intended outcome is not acceptable within that scope.
- Requirements catalogueA requirements catalogue organises requirements with identifiers and verifiable details. It helps track scope, unresolved questions and changes.
- Minimum viable product (MVP)An MVP is a limited product or offer used to test a concrete assumption about customer behaviour.
- Exit strategyA prepared route to switch, take over or retire an IT service in an orderly way.
- Migration costsEffort and expenditure for the planned move of data or functions to another environment.
- Investment costsCosts of building a new or expanded IT capability, as considered in project planning.
Articles on this topic
IT Consulting & Strategy with ASES
Strategy, architecture and technology choice