GovStack Release | Wes Brown | 30 min | Questions Is having a specific target release date needed? Yes, it is! We seem to be aligned on this based on the feedback in the Governance Committee call earlier this week What core product use cases should we prioritize? What building blocks can be included? When could we realistically create a v1.0 release?
Comments Suggestion for v1.0 improvements by Nico Lueck Reevaluate Required/Optional (dont be too strict), rename must/should or add if not existing Why? To have the same clear wording for the importance of reqs in all specs e.g. "Multiple instances of scheduler BB may be hosted with load balancing in high concurrency demand" In this case, is "may be" meant as "optional" or rather a suggestion?
Give requirements an abbreviations which can be referenced Why1? To more easily state compliance e.g. we can create an list based on these abbreviations to give suppliers for self-assessment Why2? To make it easier to handle the optional requirements e.g. "for use case X, you need the optional requirements Aw1,Eg1 and Fr3"
Check for errors and wrong formalities e.g. Headings with no text underneath, headings wrong numbering, Version history in gitbook needed?...
Take up Architecture and Security BB again
|