A basic idea of DevOps is that developers (Devs) and operations staff (Ops) form a joint team and can thus address the problems of the respective work area directly from the start. For example, operations places high demands on the monitoring and logging of an application. In close coordination, these can be taken into account directly by the developers. Operations specialists also know the typical scaling problems that should have an impact on the application architecture.
For technical decisions, the customer or product owner (Biz), bring their expertise to the team. Often forgotten, but equally important, are testers and security experts.
This team now works completely autonomously on a thematic area. For example, it develops a decoupled microservice and is able to roll out a new version at any time, ensure testing and operation, and drive forward development based on customer requirements.
Each member of the team still has their core competency. It's not about developers taking over operations in the future. Even if the team structure automatically leads to a better understanding of the previously unfamiliar areas of responsibility. Rather, BizDevOps ensures that interdisciplinary collaboration and communication is improved.
This is also accompanied by a new freedom: The team can organize itself and choose the best way for implementation and operation.
At the same time, responsibility increases: The team is responsible for its service end-2-end. Everyone is called upon, for example, if there are problems on the production environment. There is also a suitable DevOps principle for this: You build it, you run it.