Common use of Fortnightly checkpoint meetings Clause in Contracts

Fortnightly checkpoint meetings. There will be optional fortnightly checkpoint meetings between EU-OSHA and the Contractor. These sessions will be used to resolve issues relating to the most complex problems and to confirm those issues that require more than 2 man-days for their resolution. That said, if this situation is very frequent or if the number of issues raised increases the fortnightly checkpoint meetings would be changed to weekly meetings. Fortnightly checkpoint meetings Goals Periodicity  To ensure the continuous follow-up of the current deployments  To allocate incidents/change requests to the respective deployments and to take decisions regarding specific issues  Fortnightly Tasks Human Resources  To identify and validate issues to be included in each deployment  To analyse complex issues  To analyse a proposal by the Contractor for discarding a bug  To analyse a proposal by the Contractor for a lower priority  To confirm a change by EU-OSHA considering the effort estimation required  To review the ‘Small developments’  To monitor the budget and to check the consumption  To answer requests for more information  To confirm the planning of deployments both in Staging as well as in Production environments  EU-OSHA: Business Owner, Technical Leader. The Release Manager will be informed about the decisions of the meeting  Contractor: Project Manager Tools  The EU-OSHA issue tracker for the revision of issues.

Fortnightly checkpoint meetings. ‌ There will be optional fortnightly checkpoint meetings between EU-OSHA and the Contractor. These sessions will be used to resolve issues relating to the most complex problems and to confirm those issues that require more than 2 man-days for their resolution. That said, if this situation is very frequent or if the number of issues raised increases owing to the volume of websites, web applications and web tools in the Maintenance Service, the fortnightly checkpoint meetings would be changed to weekly meetings. Fortnightly checkpoint meetings Goals Periodicity  • To ensure the continuous follow-up of the current deployments  Sprint for different websites, web applications and web tools • To allocate incidents/change requests to the respective deployments Sprint and to take decisions regarding specific issues  • Fortnightly Tasks Human Resources  • To identify and validate issues to be included in each deployment  Sprint • To analyse complex issues  • To analyse a proposal by the Contractor for discarding a bug  • To analyse a proposal by the Contractor for a lower priority  • To confirm a change by EU-OSHA considering the effort estimation required  • To review the ‘Small developments’  • To monitor the budget and to check the consumption  • To answer requests for more information  • To confirm the planning of deployments both in Staging as well as in Production environments  • EU-OSHA: Business Owner, Technical Leader. The Release Manager will be informed about the decisions of the meeting  • Contractor: Project Manager Maintenance Coordinator Tools  • The EU-OSHA issue tracker for the revision of issuesissues with the status ‘Request for more information’ and issues that require more than 2 man-days for their resolution.

Fortnightly checkpoint meetings. ‌ There will be optional fortnightly checkpoint meetings between EU-OSHA and the Contractor. These sessions will be used to resolve issues relating to the most complex problems and to confirm those issues that require more than 2 man-days for their resolution. That said, if this situation is very frequent or if the number of issues raised increases owing to the volume of websites, web applications and web tools in the Maintenance Service, the fortnightly checkpoint meetings would be changed to weekly meetings. Fortnightly checkpoint meetings Goals Periodicity  • To ensure the continuous follow-up of the current deployments  Sprint for different websites, web applications and web tools • To allocate incidents/change requests to the respective deployments Sprint and to take decisions regarding specific issues  • Fortnightly Tasks Human Resources  • To identify and validate issues to be included in each deployment  • EU-OSHA: Business Owner, Sprint Technical Leader. • To analyse complex issues  The Release Manager will be • To analyse a proposal by the Contractor for discarding informed about the decisions of the a bug  meeting • To analyse a proposal by the Contractor for a lower • Contractor: Maintenance priority  Coordinator • To confirm a change by EU-OSHA considering the effort estimation required  • To review the ‘Small developments’  • To monitor the budget and to check the consumption  • To answer requests for more information  • To confirm the planning of deployments both in Staging as well as in Production environments  EU-OSHA: Business Owner, Technical Leader. The Release Manager will be informed about the decisions of the meeting  Contractor: Project Manager Tools  • The EU-OSHA issue tracker for the revision of issuesissues with the status ‘Request for more information’ and issues that require more than 2 man-days for their resolution.

Fortnightly checkpoint meetings. ‌ There will be optional fortnightly checkpoint meetings between EU-OSHA and the Contractor. These sessions will be used to resolve issues relating to the most complex problems and to confirm those issues that require more than 2 man-days for their resolution. That said, if this situation is very frequent or if the number of issues raised increases owing to the volume of websites, web applications and web tools in the Maintenance Service, the fortnightly checkpoint meetings would be changed to weekly meetings. Fortnightly checkpoint meetings Goals Periodicity  • To ensure the continuous follow-up of the current deployments  Sprint for different websites, web applications and web tools • To allocate incidents/change requests to the respective deployments Sprint and to take decisions regarding specific issues  • Fortnightly Tasks Human Resources  • To identify and validate issues to be included in each deployment  • EU-OSHA: Business Owner, Sprint • To analyse complex issues  • To analyse a proposal by the Contractor for discarding a bug  • To analyse a proposal by the Contractor for a lower priority  • To confirm a change by EU-OSHA considering the effort estimation required  • To review the ‘Small developments’  • To monitor the budget and to check the consumption  • To answer requests for more information  • To confirm the planning of deployments both in Staging as well as in Production environments  EU-OSHA: Business Owner, Technical Leader. The Release Manager will be informed about the decisions of the meeting  • Contractor: Project Manager Maintenance Coordinator Tools  • The EU-OSHA issue tracker for the revision of issuesissues with the status ‘Request for more information’ and issues that require more than 2 man-days for their resolution.