×

Debug your process for speed

The process is an unavoidable necessity that lies between the engineers and a business impact. 

The process not a goal in itself, the only thing that matters is how long it takes to deliver engineers' effort to market πŸš€

Our job here is to make sure there are no bottlenecks that slow us down.

So what is so difficult about this?

1. Choosing what works for your team. Blindly implementing one of the methodologies might not give a boost you were hoping for. 

People have unique experiences and patterns, products run on custom architecture. Each process has to be fine-tuned tuned to suit a specific team. How can you tell if works? You measure it πŸ‘‡

2. If you can't measure it, you can't improve it. Agile story point is an abstraction that wraps complexity, scope, and risks into a single number. It turns a simple time parameter into a subjective time parameter

While it might be useful for some cases, one can't use it to debug a release cycle. 

Example: In the last sprint we did 60 Story points, this sprint we did 50 Story points. Did we lose speed or our approach to estimates has changed? πŸ€”

To improve your process, you need to understand how long it takes to prepare a feature for a release. Factual, tracked hours are not subjective, so they are a good starting point to understanding your team.


3To diagnose you need to localize the issue. Length of your release cycle is a good top-level indicator to monitor the health of your process. If you want to increase speed, we need to dive deeper to understand where your chokepoints are:

  • Development;

  • Review;

  • Testing;

  • Merge;

  • Deployment;

By measuring the timing of each step, you can identify process issues and introduce improvements.


4. Validate and repeat. You need to continuously monitor these parameters to make sure your changes are effective.

Even if your team is doing well now - nothing is permanent. As the team members change and your product scales up, processes will need to be tweaked on the go.

How it works in Codigy

Codigy doesn't have enough data yet to suggest which process would be best for you. But you can build a fast process with the right measurement and validation tools:

1. Set release cycle, cultural and work-load benchmarks for each of your teams. This gives you the exact measurement of the release cycle with a breakdown by stage. Plus, Codigy catches known process-breakers such as multi-tasking, idle tasks, and a bunch more.

Benefit:

Do you get actionable data? Yes. Did you have to create Excel sheets? No. Profit!

2. Everything that exceeds your benchmarks is an issue😨 Worry not, issues are your best tool for improvement. Once you review the issues in the dashboard or reports, you can pin down the cause and think of solutions.

Benefit: 

Issues help leaders find and weed out the bottleneck in the process. Codigy will also notify team members if they trigger a process-breaker alert, like multitasking. 

3. Reached your goals? Now you can either keep monitoring or set more ambitious goals.

Benefit:

Faster business impact, lower costs 🐱‍🏍

This page was last revised on March 23, 2021

Return to main

Company


Codigy, UAB

A.Jaksto g.9 Vilnius, Lithuania

Suite 346

+370 608 96 491 hello@codi.gy

2021 Code analytics software | Codigy. All Rights Reserved, Codigy UAB Β©