---
tags: OpenZaak
---

# OpenZaak Product Steering Meeting - 22 September 2020, 10:00 to 11:00

Meeting link: https://meet.publiccode.net/OpenZaakProductSteering

Mailinglist: https://lists.publiccode.net/mailman/postorius/lists/openzaak-discuss.lists.publiccode.net/

Slack Channel: https://samenorganiseren.slack.com/archives/CT6UH711Q

## Attending

- Felix Faasen, Foundation for Public Code. [e-mail]
- Jan Ainali, Foundation for Public Code. [e-mail]
- Joeri Bekker, Maykin Media
- Niels Lindeboom, Dimpact
- Hugo ter Doest, Dimpact
- Silvion Moesan, OPEN.satisfaction. [e-mail]
- Olav Allema, Contezza
- Lazo Bozarov, Utrecht
- Tahir Malik, Contezza
- Jolanda
- Peter, Exxcellence

## Agenda
1. Introduction round
2. Decide on the responsibilities / composition of the product steering team. Finalize the [GOVERNANCE file](https://github.com/open-zaak/open-zaak/blob/master/GOVERNANCE.md) (that’s in draft right now),
4. Update of APIs for customers, so that OpenZaak follows the ZGW API standard as closely as possible
5. Content and theme of the website

## Introduction round

After the introduction round the input of Joeri and Silvion was highlighted. A number of these topics will be touched upon in our discussion topic about reponsibilities / composition of the product steering team. The proposed agenda item concerning the mission/vision/goal and strategy around OpenZaak product is being drafted by Hugo and discussed for review in our next meeting.

Additional proposed agenda items by Joeri and Silvion:

### Proposed by Joeri:
* Richtlijnen opstellen voor deelname aan stuurgroepen (zijn er bepaalde eisen voor deelname en/of zitten er verplichtingen aan?)
* Expliciete rollen benoemen (PO, website maintainer, meeting organizers)
* Exposure (zijn er nog -marketing- events waar we Open Zaak willen tonen?)
* Indien toepasselijk: Financiering voor product development (wat is de beste manier om ongoing financiering te regelen voor ontwikkeling, het doen van bugfixes?)

### Proposed by Silvion:
* Mission/vision/doelen/strategie om zo te kunnen focussen waar we willen staan met OpenZaak en waar we dus ook nee (iig nu niet) op kunnen zeggen met een gegronde onderbouwing
* Bespreekmomenten / structuur product steering group overleg
* Hoe gaan we gemeenten (klanten) aanhaken bij de product steering group

## Decide on the responsibilities / composition of the product steering team.

The group discussed numerous of topics concerning the responsibilities, composition and scope of the OpenZaak product steering group.

The group discussion involved questions about; people vs. organizations, type of organizations in the team (vendors vs. municipalities), roles in the team, and selection criteria.

Also the optimal group size was discussed; typically between 3 and 9 people and/or organizations was deemed as a good size.

Should it be organizations or persons that are part of the group? Both cases were made. An important point that was generally agreed upon was that the people coming to meetings should be invested. They are there to do work and take care about OpenZaak, not to make bureaucracy tick.

Everyone in the group agreed the minimal requirement should be that a team member should at least use OpenZaak in some shape or form (use, buy, sell, develop). Other requirements discussed (not decided) included:

- Vendors contribute development time
- Vendors contribute skills
- Vendors use/integrate OpenZaak
- Muncipipality invests in OpenZaak
- Is active in community (tickets) or do work that benefits OpenZaak
- Attend at least X% of the meetings

Lazo mentioned that members are not there to represent their own interest but the health and interest of the OpenZaak ecosystem as whole. There was no opposing views expressed on that.

We did not decide yet on the composition of the team but Peter and Joeri volunteered to capture thoughts of the group discussions and other ideas into the draft GOVERNANCE.MD file in the OpenZaak repository. They will make a pull request for it so we can review this in our next product steering meeting.

## Update of APIs for customers, so that OpenZaak follows the ZGW API standard as closely as possible

Agenda point proposed by Hugo about how to stay up-to-date / in sync with the ZWG-API's which is evolving. A discussion around the scope of the OpenZaak product steering team started, wheighing components vs. ecosystem. What is part of case oriented working and what isn't and what should be in scope?

Part of this discussion will also be touched upon in the drafting of the product mission, vision and goals and need further discussion.

## Todo's

| Action | Responsible | Due date |
| ------- | ----------- | -------- |
| Ask steering group for representatives in Product Group, post in the CommonGround | Niels, Joeri | October 21st, 2020
| Create draft pull request on GOVERNANCE.MD members |Peter & Joeri | October 21st, 2020 |
| Create Mission & Vision Draft on OpenZaak product | Hugo | October 21st, 2020

## Agenda for next meeting

Suggested to have rotating chair, Joeri takes next chair on Oct 21, 2020 15.00

- Review & discuss pull request on draft GOVERNANCE.MD file
- Review & discuss product mission/vision and goals
- PROPOSED: Feedback website?
- PROPOSED: Any other points?

## Notes