jneyra-modo opened a new issue, #8730:
URL: https://github.com/apache/incubator-devlake/issues/8730

   <!--
   Licensed to the Apache Software Foundation (ASF) under one or more
   contributor license agreements.  See the NOTICE file distributed with
   this work for additional information regarding copyright ownership.
   The ASF licenses this file to You under the Apache License, Version 2.0
   (the "License"); you may not use this file except in compliance with
   the License.  You may obtain a copy of the License at
   
       http://www.apache.org/licenses/LICENSE-2.0
   
   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.
   -->
   
   ## Question
   DORA now utilizes five metrics to measure software delivery performance, 
grouped into two distinct factors:
   
   Software Delivery Throughput
   Change lead time: Time from code commit to successful production deployment.
   Deployment frequency: How often application changes are deployed.
   Failed deployment recovery time: Time to recover from a failed deployment.
   Software Delivery Instability
   Change fail rate: Percentage of deployments causing failures in production.
   Deployment rework rate: Percentage of deployments that are unplanned work to 
fix bugs.
   
   is there any plans to implement the fifth metric, Deployment rework rate?
   
   
   ## Screenshots
   If applicable, add screenshots to help explain.
   
   ## Additional context
   more info here: 
https://dora.dev/guides/dora-metrics/history/#from-four-keys-to-five-2024


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to