Draft shared product backlog: https://github.com/orgs/Signals/projects/2
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)
Chair: Felix
Board: https://miro.com/app/board/o9J_kkwkuBE=/
Jacco had a meeting with Amsterdam. VNG does not currently have a UX/UI designer in the team.
Amsterdam agreed the would like to contribute UX/UI designer to Signalen
Jacoo also had a meeting with Wouter Bruining and Bart on how Signalen could connect with a case management system using the ZWG API standard.
Almere and Den Bosch reached consensus on how to operationalize Signalen as a Service
Felix presented a proposal on how to make sure we perform shared product management for Signalen in open. Demo briefly covered:
Last meeting we extensively discussed the feature request template and decided to fill one out and test drive the process we came up with. In stead we had a number of discussions related to:
The step where a feature request needs to be translated from a functional description to something a developer can actually build is largely dependent on the scope of the feature request. There can be large epic’s which will result in a long process of refinement and design before it is ready to be developed.
Some refinements can be short, others long. Developers or other experts should and can always be present as needed in the product steering process but there needs to be a short term and mid-long term cycle in which we can accommodate discussions and prioritizations about features as well as further refining and designing them.
Arvid from Amsterdam already has a process which takes this into account which focuses on the steps on the process on how to come from a feature request to something which is developed and integrated into the Signalen product. Arvid will share and talk us through this process in the next meeting so we can align an use this process in the product steering group (see action points)
In the previous discussion Jacco mentioned it is also important to have a forward look where you decided which “ready-to-be-develloped” features will land in the product. This could be a quarterly roadmap which includes a high level summary of the development and features goals and publish these on the roadmap section of the website of signalen.org.
Arjo mentioned that it is very hard for him to determine what would be included in the roadmap or a quarterly release. Also Astrid said she finds it challenging as there is no single overview yet of all the features but she is more than happy to work on the backlog after the initial one is ready for the next meeting.
Felix amended that the shared product backlog located on github (https://github.com/orgs/Signalen/projects/2) already includes all epics and stories combined from the sources: VNG backlog, joined excel sheet Den Bosch/Almere and powerpoint Amsterdam.
We came to the conclusion that it would be valuable to groom these items, go over them and write them in the form of a feature request so these features can be a starting point for our first joint quarterly roadmap. In the next meeting we could discuss these on a high level with each other and then start working on the joint roadmap together.
Felix will facilitate that process. Before that Bram will team up with Erik, a new product manager from Den Bosch and with Almere first. After that he will ping Felix and we will have a co working session to put all the cards in place.
Important to note that is that we will have the following assets:
We will practice this process and refine step by step.
Next chair: Bram
| Action | Responsible | Due date |
|---|---|---|
| Short from feature to product process walkthrough used in Amsterdam | Arvid | 12-11-2020 |
| High level overview on shared feature request backlog | Bram/Erik/Felix | 12-11-2020 |