signalen-discuss October 2020

signalen-discuss@lists.publiccode.net

2 participants
3 discussions

Product steering meeting notes 29/10/2020
by Felix Faassen 29 Oct '20

29 Oct '20

Hi everyone, Here are notes of our product steering meeting held today 29/10/2020. If there are things I missed or you think I misrepresented please reply to this email Kind regards, Felix Signalen Product Steering Meeting 29 October, 2020, 14:00 to 15:00 Comment 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… (Check spam) Chair: Felix Board: https://miro.com/app/board/o9J_kkwkuBE=/ <https://hackmd.io/kWQdMpBgS6CdFxjxKHFmZg?view#Agenda>Agenda: - Announcements - Discussion about where to store and communicate backlog, features - Discuss Feature Request template & process - Agenda next meeting <https://hackmd.io/kWQdMpBgS6CdFxjxKHFmZg?view#Announcements>Announcements 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 <https://hackmd.io/kWQdMpBgS6CdFxjxKHFmZg?view#Discussion-about-where-to-sto…>Discussion about where to store and communicate backlog, features Felix presented a proposal on how to make sure we perform shared product management for Signalen in open. Demo briefly covered: - Information on the signalen.org website about product steering and shared backlog (see draft pull request: ) - Presented our shared product backlog where to put feature requests and prioritize according to the process we are developing together. (see: https://github.com/orgs/Signalen/projects/2) - Feedback will be provided on the mailinglist. We decided to continue with this approach. Jacco made a remark that it would be nice in the future to have a webform for feature requests and would be published on the backlog. <https://hackmd.io/kWQdMpBgS6CdFxjxKHFmZg?view#Discuss-Feature-Request-templ…>Discuss Feature Request template & process 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: <https://hackmd.io/kWQdMpBgS6CdFxjxKHFmZg?view#Refinement-process-from-a-fea…>Refinement process from a feature request to something you can build 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) <https://hackmd.io/kWQdMpBgS6CdFxjxKHFmZg?view#Release-planning-amp-roadmap>Release planning & roadmap 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: - A shared open feature request backlog which is a reflection of functional descriptions which will be refined and designed together with developers and will translate to individual/multiple github issues - The roadmap on signalen.org will provide a high level descriptive overview on a quarterly basis to show where the development is heading in the upcoming quarters. We will practice this process and refine step by step. <https://hackmd.io/kWQdMpBgS6CdFxjxKHFmZg?view#Agenda-next-meeting>Agenda next meeting - Short from feature to product process walkthrough used in Amsterdam by Arvid - High level overview on shared feature request backlog <https://hackmd.io/kWQdMpBgS6CdFxjxKHFmZg?view#Action-points>Action points Next chair: Bram ActionResponsibleDue 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 -- Felix Faassen, Codebase steward Foundation for Public Code | https://publiccode.net github.com/publiccodenet | github.com/felixfaassen felix(a)publiccode.net | +31 624633278

1 0

Revised feature request template
by Erik Veerman 19 Oct '20

19 Oct '20

Hi all, Enclosed the revised feature request template. Groet, Erik 0624530961 ________________________________ Dit bericht is alleen voor de geadresseerde. Hebt u dit bericht onterecht ontvangen? Laat u dit dan weten aan de afzender. Verwijdert u het bericht dan ook uit uw postbus. De gemeente 's-Hertogenbosch is zo zorgvuldig mogelijk bij het voorkomen van virussen. U dient zelf te controleren of er geen virussen in de bijlage(n) zitten. Gemeente 's-Hertogenbosch https://www.s-hertogenbosch.nl ________________________________

1 0

Please add to mailinglist
by Erik Veerman 16 Oct '20

16 Oct '20

Hi, Could you please add me to the mailinglist? Groet, Erik 0624530961 ________________________________ Dit bericht is alleen voor de geadresseerde. Hebt u dit bericht onterecht ontvangen? Laat u dit dan weten aan de afzender. Verwijdert u het bericht dan ook uit uw postbus. De gemeente 's-Hertogenbosch is zo zorgvuldig mogelijk bij het voorkomen van virussen. U dient zelf te controleren of er geen virussen in de bijlage(n) zitten. Gemeente 's-Hertogenbosch https://www.s-hertogenbosch.nl ________________________________

1 0

2024

2023

2022

2021

2020

signalen-discuss October 2020