Chair: Felix
Video Chat using Jitsi: https://meet.publiccode.net/SignalenProductSteering
This note: https://hackmd.io/1JdTA5uBTvy1QOVt-bpWng
Shared Product backlog: https://github.com/orgs/Signals/projects/2 (draft)
Product steering and feature requests documentation: https://github.com/Signalen/product-steering
Create feature request:https://github.com/Signalen/product-steering/issues/new?assignees=&labels=enhancement&template=feature_request.md&title=[FEATURE-REQUEST]
Slack Channel: https://join.slack.com/share/zt-heae6d92-sqH1xvJvJQ_RMpAAMnHLKQ
Mailing list: https://lists.publiccode.net/mailman/postorius/lists/signalen-discuss.lists.publiccode.net/ (Check spam)
Board: https://miro.com/app/board/o9J_kkwkuBE=/
Started a discussion about everyone’s expectations about the Signalen in their municipality, the challenges and what you want to get out of the product steering meeting. Last but not least I would like to make a short action list on steps we need to take to get a draft roadmap 2021 ready by the end of January beginning of February.
Round question:
Astrid is searching. She is interested in a common vision for the product and wants to know where we are going to work together. Jacco mentions that this is something we need together. Arjo and Astrid acknowledge it but it is also hard as everyone is in a different adoption stage and has different needs.
Felix mentions that it is important we meet and work on things we all commonly need. Felix and Jacco mentioned the idea of creating an Implementation Guide. A living collaborative document where we put our learnings from a process and organizational perspective. Not only will help such a document with the further adoption of Signalen but also as a vehicle for knowledge sharing in the product steering group. In doing the work we will also learn what is commonly needed, what is missing ultimately informing the roadmap and our future work as product steering group.
We will start to create an implementation guide where we will re-use as much information and documentation currently available about Signalen used by Amsterdam and created by Arvid and his co-workers. We will make it more generic applicable to other municipalities and will enrich the guide with our own experience and learnings.
Jacco, Felix and Arvid will have a meeting about this. Felix will set up a new repository for the implementation guide. Jacco, Felix and Arvid will make an initial table of contents including references to existing documentation. Next meeting we will discuss as a group what will need to be changed and added and we will distribute workload and jointly develop this document further.
We also briefly discussed working on a joint mission and vision. Here is a work-in-progress example the mission and vision for OpenZaak
https://github.com/open-zaak/open-zaak/blob/17d32ea48bd69238776410f8a7375681745c612f/OpenZaak_Mission_Vision_Scope.md
Reason why describing this is important is outlined in the standard for public code: https://standard.publiccode.net/criteria/document-objectives.html
Astrid mentions her project where Utrecht will be conducting user experience research. She asked if anyone is interested in certain research questions to be included that she is most welcome to receive them.
There was also interest from the group to have the UX team researching this to give a small presentation in a separate meeting. She will organize something in the coming weeks.
Next chair: ???
| Action | Responsible | Due date |
|---|---|---|
| Make table of contents and repo for Signalen Implementation Guide | Jacco, Felix with input from Arvid | 10-12-2020 |
| Write down short vision/mission Signalen |