Skip to main content

Routines & Responsibilities

Incomplete article

More content to come as soon as possible. Want to contribute? Contact us on Slack (requires a Bouvet user account) or see the following issue on GitHub

To avoid situations where the responsibility for specific components of a system is unclear, it is a big advantage for the project to clarify the scope and responsibilities of the project. The list below is not a complete catch-all checklist, but can be used as a starting point and adapted to specific situations as needed. The primary goal is to raise awarenes related to which responsibilities a team has, so that everyone is aligned.

The other articles on covers all the phases in a traditional DevSecOps process, and be used as a starting point for defining roles and responsibilities for the project team.


The customer is responsible for all infrastructure the project depends on, including virtual machines, networking, storage and database servers. We are responsible for implementing the project, migrating existing data into the databases, deployment, logging and monitoring as well as maintenance of the project deliverables.

  • What is Bouvet responsible for?

  • What is the customer responsible for?

  • Does the customer have any uptime requirements?

  • Are there any requirements regulating data loss?

  • What are the current process for maintenance (patching)?

    • OS
    • Installed components
    • Dependencies

When the overall list of responsibilities is established, consider storing it in the source code repository along with any other project deliverables. This will increase its visilibity within the team, and can result in a higher degree of team ownership.