Vxnaid™ Governance Board

This page describes the Vxnaid™ Governance Board, its members and processes.

1 Vxnaid™ Governance Board members

The governance board will consists out of the following members:

Sponsor Sponsor of the project and end responsible for the budget. The sponsor will at a minimum be informed.

Vxnaid™ Product Owner* Owner of the Vxnaid™ solution. Determines priorities for the Vxnaid™ related changes and is the ultimate decision maker.

Connect for Life™ Product Owner* Owner of the Connect for Life™ back-end. Will contribute to the decision making process and any potential dependencies on the Connect for Life™ roadmap and priorities.

IT Project Owner** Overall owner of the IT solution. Will contribute to the decision making process related to the Vxnaid™ and Connect for Life™ product and will be responsible for leading the Governance meetings.

Technical Lead** Responsible for providing technical input on effort, complexities and feasibilities of the requested changes.

Project Manager/Business Analyst** Responsible for determining the impact on the planning and scheduling of the requested changes. This role will also be responsible for ensuring the requirements are documented. Responsible for documenting the outcomes of the Governance Board meeting.

Ad-hoc member Members that will be included in the Governance meeting on an ad-hoc basis if request(s) have an impact on their implementation.

(*) These members are at minimum required at the governance meeting. (**) In addition to the members marked by ( * ), at least on of these members is required at the governance meeting.

2 Intake Process

New requests, reporting of bugs, etc. from external implementers/users will be done via the Vxnaid™ project on Github under the "Issues" reporting tab. Requests, bug reportings, etc. will be processed on a weekly basis and aknowledged to the reporter.

3 Prioritization

During the Governance meetings the board classifies the requests as follows:

• Urgent: Only applicable to bugs. Tickets with this designation will be addressed immediately and will be part of an emergency release of the solution outside of the regular release schedule.
• High: Tickets with this designation will be released as part of the current release.
• Medium: Tickets with this designation will be released as part of the current, or unless team capacity does not allow, the next release.
• Low: Tickets with this designation will be released as part of the next release.
• Nice to Have: Tickets with this designation will be picked up by the team as soon as capacity allows.
• Deferred: Tickets with this designation will be put on hold and re-prioritized at the next Governance meeting.
• Rejected: Tickets with this designation will not be addressed.

4 Governance Process

/uploads/Governance process.png

5 Governance Meetings

The Governance Board will convene every last week of the month, unless:

• Critical team members (see section 1) are not available: the meeting will be rescheduled at another time before the next planned governance meeting or the request(s) will be addressed via e-mail.
• Urgent bug(s) are reported: an ad-hoc meeting may be scheduled or addressed via e-mail.
• Low amount of requests: the Governance Board can decide to address these via e-mail.
• No new requests: no need for any meeting.