2019-03-04-reduce-cycle-time.html.md.erb 6.19 KB
Newer Older
Suri Patel's avatar
Suri Patel committed
1
---
2
title: "Want to reduce cycle time? Commit to a new approach."
Suri Patel's avatar
Suri Patel committed
3 4 5
author: Suri Patel
author_gitlab: suripatel
author_twitter: gitlab
Suri Patel's avatar
Suri Patel committed
6
categories: insights
Suri Patel's avatar
Suri Patel committed
7 8
image_title: '/images/blogimages/just-commit-blog-cover.png'
description: We have a new way of looking at cycle time. Let’s talk about it.
Suri Patel's avatar
Suri Patel committed
9
Tags: workflow, DevOps, collaboration
Suri Patel's avatar
Suri Patel committed
10 11
cta_button_text: 'Just commit'
cta_button_link: '/just-commit/reduce-cycle-time/'
Suri Patel's avatar
Suri Patel committed
12
twitter_text: "#JustCommit to reducing cycle time"
Suri Patel's avatar
Suri Patel committed
13 14 15
postType: content marketing
---

16
Traditionally, software leaders use `cycle time` to refer to [the time between
Rebecca Dodd's avatar
Rebecca Dodd committed
17 18 19 20 21
starting and delivering software](https://www.isixsigma.com/tools-templates/software/software-projects-cycle-time-%E2%90%98are-we-there-yet%E2%90%99/).
More specifically, it's the time between an engineer beginning work on an
issue/feature and when that code is finally deployed to production and accessible
to users. Historically, this definition has arisen from a siloed view of software
development. Engineering leaders talk about the cycle time that affects engineering,
Rebecca Dodd's avatar
Rebecca Dodd committed
22
but they don't include the planning cycle time that the PMO contributed before
Suri Patel's avatar
Suri Patel committed
23 24
the project was handed off to the engineering org. Ultimately, this widely accepted
definition of cycle time doesn't fully capture every stage of the software development lifecycle.
Suri Patel's avatar
Suri Patel committed
25

Rebecca Dodd's avatar
Rebecca Dodd committed
26 27 28 29 30
We've seen how powerful it can be when teams collaborate rather than work in silos,
so we recommend including the planning stage when measuring cycle time. By measuring
cycle time in this way, you capture the full efficiency of your end-to-end process,
which can help you focus on finding and fixing inefficiencies across the full
lifecycle of your software – not just one part of it.
Suri Patel's avatar
Suri Patel committed
31

Suri Patel's avatar
Suri Patel committed
32
## A new perspective on cycle time
Suri Patel's avatar
Suri Patel committed
33

Rebecca Dodd's avatar
Rebecca Dodd committed
34 35
{::options parse_block_html="true" /}

Suri Patel's avatar
Suri Patel committed
36
<div class="panel panel-success">
Suri Patel's avatar
Suri Patel committed
37
**CYCLE TIME**
Suri Patel's avatar
Suri Patel committed
38
{: .panel-heading}
Suri Patel's avatar
fix box  
Suri Patel committed
39 40
<div class="panel-body">

Suri Patel's avatar
Suri Patel committed
41
/ˈsīk(ə)l/ /tīm
Suri Patel's avatar
Suri Patel committed
42

Suri Patel's avatar
Suri Patel committed
43
_noun_
Suri Patel's avatar
Suri Patel committed
44

45
1. The elapsed time between starting to work on an idea and delivering to production.
Suri Patel's avatar
Suri Patel committed
46
1. A determining factor in whether organizations can meet business demands while delivering value to customers.
Suri Patel's avatar
fix box  
Suri Patel committed
47 48 49 50

</div>
</div>

Rebecca Dodd's avatar
Rebecca Dodd committed
51
This new understanding of cycle time covers the entire software development
Rebecca Dodd's avatar
Rebecca Dodd committed
52
lifecycle and accounts for the time invested in planning what actions
Rebecca Dodd's avatar
Rebecca Dodd committed
53 54
to take to ship an idea. The planning stage of the software development lifecycle
is one of the most crucial components, because it builds the foundation for
Suri Patel's avatar
Suri Patel committed
55 56
workflows, project management, and resource allocation.

Rebecca Dodd's avatar
Rebecca Dodd committed
57
>Cycle time is a metric that measures the amount of time in a process between the start,
Suri Patel's avatar
Suri Patel committed
58
which often begins with an idea, and the end when it’s finally in the hands of customers.
Suri Patel's avatar
Suri Patel committed
59

Rebecca Dodd's avatar
Rebecca Dodd committed
60
Reducing cycle time is a competitive advantage, and this new perspective enables
Suri Patel's avatar
Suri Patel committed
61
teams to take an end-to-end approach to rapid delivery.
Suri Patel's avatar
Suri Patel committed
62 63 64

## Why you should reduce cycle time

Rebecca Dodd's avatar
Rebecca Dodd committed
65 66 67 68 69 70 71
Since software touches nearly every aspect of daily life, reducing the time
between thinking of an idea and having the code in production is vital to
providing value to customers. Maintaining velocity is an important step in
listening to customers and meeting business demands. Because the market moves
so quickly, organizations must find ways to simplify processes to empower teams
to focus on delivering value to customers faster. When teams aren’t picking
through tangled processes, they can quickly ship code and innovate to create
Suri Patel's avatar
Suri Patel committed
72 73
features that customers want.

Rebecca Dodd's avatar
Rebecca Dodd committed
74
>“Cycle time compression may be the most underestimated force in determining winners and losers in tech.” — [Marc Andreessen](https://medium.com/digital-customer-experience/the-untapped-creative-potential-of-big-data-39dfe1916d07)
Suri Patel's avatar
Suri Patel committed
75

76 77 78
When organizations experience long cycle time, they risk losing market share.
Since competitors are faster to market and can rapidly respond to customer
needs, organizations with slow cycle time are left behind to perfect the
Rebecca Dodd's avatar
Rebecca Dodd committed
79 80
past needs of users. Organizations face lost revenue and opportunities,
since they’re unable to react quickly to changing market needs. A build-up of
Rebecca Dodd's avatar
Rebecca Dodd committed
81
technical debt and rising costs make problems worse, and organizations are
Rebecca Dodd's avatar
Rebecca Dodd committed
82
forced to play catch-up with their competitors.
Suri Patel's avatar
Suri Patel committed
83

Rebecca Dodd's avatar
Rebecca Dodd committed
84
Organizations that rapidly deliver see an increase in the number of projects and
Rebecca Dodd's avatar
Rebecca Dodd committed
85
budgets that stay on track, with developers spending more time delivering new
Rebecca Dodd's avatar
Rebecca Dodd committed
86
functionality rather than fixing defects, and faster response to constantly
Suri Patel's avatar
Suri Patel committed
87 88
evolving customer needs.

Rebecca Dodd's avatar
Rebecca Dodd committed
89
If organizations want to differentiate their software and gain market share,
Suri Patel's avatar
Suri Patel committed
90 91 92 93
reducing cycle time should be a business imperative.

## How to start

Rebecca Dodd's avatar
Rebecca Dodd committed
94 95
There are several ways to reduce cycle time, but the two most immediate ways to
rapidly see your ideas in the hands of customers is to increase visibility and
Suri Patel's avatar
Suri Patel committed
96 97
adopt a CI/CD approach to development.

Rebecca Dodd's avatar
Rebecca Dodd committed
98 99 100 101
### Visibility

Teams require end-to-end visibility and traceability of issues
throughout the software development lifecycle – from idea to production – in
Rebecca Dodd's avatar
Rebecca Dodd committed
102 103
order to ship features at the speed customers demand. An increase in visibility
reduces silos and facilitates collaboration, ensuring that everyone is aware of
Rebecca Dodd's avatar
Rebecca Dodd committed
104
what’s going on and where they’re needed. To give you an example of the power of
Suri Patel's avatar
Suri Patel committed
105
visibility, let's take a look at GitLab. If we calculated the average time to
106
deliver all the features in [11.8](/blog/2019/02/22/gitlab-11-8-released/), it would
Rebecca Dodd's avatar
Rebecca Dodd committed
107 108 109 110
be 250 days. With an increase in visibility, we're able to see that some features
we shipped took only 30 days, while others were in our backlog for three years.
Since we're on a monthly release cadence, knowing that many of our features were
started and delivered in 30 days helps us determine whether we're quickly
Suri Patel's avatar
Suri Patel committed
111
delivering value to our customers.
Suri Patel's avatar
Suri Patel committed
112

Rebecca Dodd's avatar
Rebecca Dodd committed
113 114 115
### Continuous integration and continuous delivery

Quickly delivering what customers
Rebecca Dodd's avatar
Rebecca Dodd committed
116
want requires a modernized software development lifecycle that saves time,
Shane Rice's avatar
Shane Rice committed
117
effort, and cost. According to a 2017 Forrester Wave report, “CI enables software
Rebecca Dodd's avatar
Rebecca Dodd committed
118 119
development teams to work collaboratively, without stepping on each other’s toes,
by automating builds and source code integration to maintain source code integrity.”
120
A [continuous delivery](/topics/ci-cd/) approach automates testing and deployment capabilities so
Rebecca Dodd's avatar
Rebecca Dodd committed
121
that software can be developed and deployed rapidly and reliably.
Suri Patel's avatar
Suri Patel committed
122 123

Are you ready to reduce cycle time? **[Just commit](/just-commit/reduce-cycle-time/)**.