Overview | |
|---|---|
Applicability | Scrum and Kanban projects |
Definition (Hover Text) | Highlights the number of fixVersions planned or released in a month |
Source Tools | Jira, Azure Board |
Graph type | Line chart |
Filters | - |
Hover Format on KPI | Month: <<Count>> |
Fields on Explore Overlay |
|
Business Logic | |
Calculation Formula | It is calculated as the number of fix versions in Jira that have a Release End Date within a given month. |
Trend | A stable or upward trend is desirable |
Maturity Levels | Not defined |
Configurations | |
Processor Fields | NA |
Mandatory fields | NA |
How to Validate KPI | |
Suggested ways of working | |
Sample JQLs | NA |
Best Practices | |
Automate Deployment | Use Continuous Integration and Continuous Deployment (CI/CD) pipelines to automate the build, test, and deployment processes, ensuring smooth and frequent releases. |
Incremental Development | Encourage small, incremental changes rather than large, monolithic updates to facilitate more frequent releases. |
Define Clear Release Criteria | Establish clear criteria for what constitutes a releasable increment, including testing, documentation, and stakeholder approval. |
Use Branching Strategies | Implement effective branching strategies, such as GitFlow or trunk-based development, to manage code changes and releases efficiently. |
Utilize Feature Flags | Implement feature flags to enable or disable features without deploying new code, allowing for safer releases and easier rollback. |
Benefits of KPI | |
Feedback Loop | Regular releases allow for quicker feedback from users, which can be used to improve the product iteratively. |
Customer Satisfaction | Frequent releases enable continuous delivery of value to customers, keeping them engaged and satisfied. |
Reduced Risk | Smaller, incremental releases reduce the risk associated with large, infrequent releases and make it easier to identify and fix issues. |
Automate Deployment | |
General
Content
Integrations