@@ -11,8 +11,10 @@ <h1><a id="epilogue">Executive Summary</a></h1>
1111< p >
1212 Meanwhile, DevOps has grown to encompass much more than simply building and running technical solutions. DevOps
1313 teams are responsible for meeting performance metrics defined by research organizations like DevOps Research and
14- Assessment (DORA) and also implementing high performing team structures such as those defined by Westrum's organization
15- culture. The concept of DevOps has proven so popular and grown to encompass such a wide range of disciplines, tools, and
14+ Assessment (DORA) and also implementing high performing team structures such as those defined by Westrum's
15+ organization
16+ culture. The concept of DevOps has proven so popular and grown to encompass such a wide range of disciplines, tools,
17+ and
1618 processes that it is no longer possible to define where DevOps ends.
1719</ p >
1820
@@ -160,5 +162,13 @@ <h1><a id="epilogue">Executive Summary</a></h1>
160162</ ul >
161163
162164< p >
163- DEaaS is
165+ DEaaS allows you to scale your DevOps teams by providing them with high quality and supported architectural
166+ decisions
167+ on which to build valuable solutions to unique problems. The responsibility models used by DEaaS clearly identify
168+ what DevOps teams and individuals are and are not responsible for. Structuring DEaaS as an internal business service
169+ ensures common business requirements such as documentation, training, support, and metrics are provisioned from the
170+ outset. DEaaS can measure its impact on its customers through the improvement of DevEx, the impact on customer
171+ specific outcomes such
172+ as the DORA metrics, how widespread the use of IDP artifacts are, or other north-star metrics. DEaaS also measures
173+ its business impact on revenue, risk, or cost.
164174</ p >
0 commit comments