Information systems (IS) literature has predominantly studied IS project control with a focus on software development projects. However, by virtue of digital transformation, an increasing number of organizations are implementing cross-functional teams, combining software development with software operations tasks. The goal is to react quickly to the ever-changing market requirements.

The DevOps concept aims to effectively orchestrate development and operations activities and smoothly manage tensions within teams, resulting from the heterogeneous composition of skills, responsibilities, and working styles.

In contrast to the predominant project management view of control of prior research, which focuses on software development, this study investigates a different perspective: focusing on exerting control in DevOps teams and simultaneously navigating tensions between software development and operations. Utilizing an inductive theory-building approach, we first identify the four tensions discussed in prior literature—namely, goal conflict, method discomfort, decision rights, and time rhythm—and then empirically derive corresponding resolutions.

Integrating our findings, we present an empirically derived model that can serve as a DevOps control approach for navigating the tensions between development and operations teams. This model extends our theoretical knowledge about control in DevOps teams and serves to inform IT practitioners, helping them successfully implement and manage DevOps teams.

信息系统 (IS) 文献主要研究 IS 项目控制，重点是软件开发项目。然而，借助数字化转型，越来越多的组织正在实施跨职能团队，将软件开发与软件运营任务结合起来。目标是对不断变化的市场需求做出快速反应。

DevOps 概念旨在有效地协调开发和运营活动，并顺利管理团队内部因技能、职责和工作方式的异构组成而产生的紧张关系。

与先前研究的主要项目管理控制观点（侧重于软件开发）相反，本研究探讨了不同的视角：侧重于在 DevOps 团队中施加控制，同时解决软件开发和运营之间的紧张关系。利用归纳理论构建方法，我们首先确定了先前文献中讨论的四种张力，即目标冲突、方法不适、决策权和时间节奏，然后根据经验得出相应的解决方案。

整合我们的发现，我们提出了一个根据经验得出的模型，可以作为 DevOps 控制方法来解决开发和运营团队之间的紧张关系。该模型扩展了我们关于 DevOps 团队控制的理论知识，并为 IT 从业人员提供信息，帮助他们成功实施和管理 DevOps 团队。