...
The alternative would be the traditional approach of writing a requirements specification, hand this over to the IT Development team(s) at the start and then see the product at the end, with perhaps some interim meetings, updates, and demos. However, as part of the new SEKO Roadmap strategy, the desire has been expressed to adopt a more agile approach to software development with continuous stakeholder engagement throughout the build phase.
Capture System Features into a
...
/wiki/spaces/TD/pages/2478309493
The high-level requirements of the desired system delivery should be captured in a bullet pointed list to a degree of detail which gives a clear overall description of the ultimate functionality, with each item in the list a separate required ‘feature’ of the system (it is helpful to think of each feature as a bullet point about the system that could be listed in a detailed sales brochure or presentation).
...
The set of high-level features from the / Requirements Catalogue must be put into a prioritised order and allocated to main delivery phases, to create a high delivery roadmap, with particular focus on the next main delivery phase.
...