You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Improvements can be made on the documentation around the OpenZaak market consultation.
Easy enhancements
Improve how existing assets interlink.
There are currently assets on https, the blog, the podcast, about and the openzaak market consultation repo. These do not all interlink.
market-consultation repo: add links to blog and podcast
podcast: add links to all
about: add links to all(?) (currently only blog)
Possible mid-size enhancements
market consultation repo: review the text from the perspective of a new and uninitiated reader and improve how well it explains what the content, goal and outcome was of this work
Questions to consider when deciding on prioritising and investing in new features
does the market consultation remain a one-off, and investment can go into building a strong case study archive in the openzaak/market-consultation repo?
is it likely vendor ecosystem set-up work will be repeated, and if so, should investing in extracting reusable process and learnings into About be prioritised? (incl how to use the workshops for this)
is there enough interest to warrant follow up work to evaluate what the consultation enabled, potentially leading to a business case?
While this is still interesting to people who haven't considered group public sector FOSS procurement before, we will not be doing this before staff leave on 1 April 2024.
Improvements can be made on the documentation around the OpenZaak market consultation.
Easy enhancements
Improve how existing assets interlink.
There are currently assets on https, the blog, the podcast, about and the openzaak market consultation repo. These do not all interlink.
Possible mid-size enhancements
Questions to consider when deciding on prioritising and investing in new features
Existing unpublished work that can be built on
The text was updated successfully, but these errors were encountered: