Interview questions

Goal of the interview

Goal of the interview: introduce the project, get to know the interviewee, their role and perspective on the OpenZaak codebase and collaboration, whishes and bottlenecks.

Draft document/model the collaboration (roles, mandates, processes, activities, documents, etc.).

The interview

introduction from the interviewer

Open with some context and sketch the ambition of pilot:

“Wij zijn door G4 gevraagd om bronbeheer, governance en community rondom OpenZaak en mogelijke verbeteringen daarin in kaart te brengen.”

questions for the interviewee

  • can you tell us a bit about yourself and your organization, what is your expertise?
  • what is OpenZaak, how would you describe it? (get a sense of OpenZaak principles/mission/vision and identity - e.g. is OpenZaak loyal implementation, or is it an experimental tester)
  • what is/has been your role in OpenZaak, is it documented, do you have mandate?
  • how did you get involved, how did you enter the ecosystem?
  • how do you work together, what is the process, which other parties do you collaborate with?
  • how does that work for you, what works well, what would you recommend other components reuse (and what not)
  • have there been notable changes in the openzaak ecosystem over time, good or bad?
  • how do you see the future of OpenZaak? Is it mostly development and new features? Or is it scaling implementations and new users?
  • are there any improvements you can think of, what needs to improve (pain points/blockers)?
  • what would be the best future you can think of (ambitions/wishes)?
  • biggest challenge you see for the community (getting there)?
  • any other business

OpenZaak Governance pilot. Distributed by an EUPL.

This site uses Just the Docs, a documentation theme for Jekyll.