Category: Metrics
-
Types of TDD
Test-Driven Development (TDD) is a software development practice that involves writing tests before writing the actual code. It helps ensure that the code meets the specified requirements and functions correctly. There are several types of TDD, and the implementation requires a specific mindset: Mindset Needed to Implement TDD: TDD is not just a technical practice;… Read more
-
On-Site Customer
An On-Site Customer is a practice in agile software development where a customer representative works closely with the development team on-site, providing real-time feedback, clarifying requirements, and making decisions. This practice is often associated with extreme programming (XP) and other agile methodologies. Explanation: An on-site customer is physically present at the development location, allowing for… Read more
-
Collective Code Ownership
Collective Code Ownership is a software development practice that promotes shared responsibility for code among all team members. It emphasizes that every developer is responsible for the quality and maintainability of the codebase, not just the original author of a particular piece of code. Here are techniques to implement collective code ownership, its benefits, and… Read more
-
Small Releases
Small Releases involve delivering software increments that are relatively small in scope but add value to the product. When used in collaboration with Scrum, small releases can enhance development practices and ensure that valuable functionality is delivered consistently throughout the project. Here’s how to use small releases in collaboration with Scrum, its benefits, and considerations:… Read more
-
Continuous Integration
Continuous Integration (CI) is a software development practice where code changes are automatically built, tested, and integrated into a shared repository frequently. When used in collaboration with Scrum, CI enhances development practices and streamlines the integration of new features and bug fixes. Here’s how to use CI in collaboration with Scrum, its benefits, and considerations:… Read more
-
DORA – Mean Time to Recover (MTTR)
Mean Time to Recover (MTTR) is a DevOps metric that measures the average time it takes for a system or service to recover after an incident or failure has occurred. It reflects the organization’s efficiency in resolving issues and restoring normal operations. Tracking this metric is valuable for several reasons: Uses: Insights from MTTR: Actions… Read more
-
DORA – Change Failure Rate
Change Failure Rate is a DevOps metric that measures the percentage of code changes, updates, or deployments that result in failures or incidents in a production environment. It assesses the reliability and robustness of an organization’s software delivery process. Tracking this metric is useful for several reasons: Uses: Insights from Change Failure Rate: Actions to… Read more
-
DORA – Deployment frequency
Deployment Frequency is a key DevOps metric that measures how often new code changes or features are deployed to a production environment. It reflects the organisation’s ability to release software rapidly and frequently. Tracking this metric is valuable for several reasons: Uses: Insights from Deployment Frequency: Actions to Improve Deployment Frequency: Tracking Deployment Frequency is… Read more
-
DORA – Lead time for changes
Lead Time for Changes is the time it takes for a code change, feature, or user story to move from the initial request or idea to being fully deployed and operational in a production environment. Tracking this metric is valuable for several reasons: Uses: Insights from Lead Time for Changes: Actions to Improve Lead Time:… Read more
-
Sprint burndown charts – what do they measure
Sprint Burndown Charts are visual tools used in Agile and Scrum to track the progress of work in a sprint (a time-boxed iteration). They plot the amount of work remaining to be completed on the vertical axis and the time on the horizontal axis. As the sprint progresses, the chart is updated automatically to reflect… Read more