Skip to main content

Going for Lead-Time

Note: This topic of this post was heavily inspired by The Phoenix Project and the succeeding tome of reference, The DevOps Handbook.

There are many metrics out there that can guide you to improve your business, but in the upside-down world of Internet business, many of these can be plain wrong, or at least they do not serve well as guides for what you should be doing. If you measure success by measuring profit, for instance, you'll run out of good will with your users or partners very quickly.

Then there are a load of more noble but fuzzy numbers that you can measure by surveying employees or users. Think employee-happiness, etc. While these are definitely useful, they are easy to get wrong, and it's easy to over-do it, causing survey fatigue. They're also hard to trace from cause to effect. It's hard to say which particular company decision lead to some satisfaction rating going down.

Take the SWOT analysis as a particular one of these surveys. It will give you a great map of what the employees of the company are feeling about a variety of things, and while this will certainly be helpful, it does not even attempt any root-cause connection, so it ends up being a collection of subjective opinions, which may or may not be pointing at the underlying issues.

When it comes to getting real deep understanding of the issues of an organization, I'm personally a fan of the good old retrospective. Getting in a room or call with a smaller group of people who can genuinely build a common understanding of what is going wrong and right is golden, especially if done so on a repeated basis (as long as the resulting commitments and impediments are actually tended to). They don't scale so well, although I'm sure there are clever ways like open-space, or "scaling agile" techniques to help with that.

But neither SWOTs nor retrospectives give you proper metrics. They're not fast. They're not objective. They're not automatic.

So what number can we measure in an automatic way that actually gives us valuable input on how the organization is working? What number can we aim to change when changing the organization? What number can we ask about in every retrospective? The answer is lead-time.




An example of "lead" from idea to change in the world. I left out waiting times, execution times, rework/failure rates, etc.
Armed with lead-time, the Theory of Constraints, Little's Law and value stream mapping, you can go into any organization and start improving the system (yes, this is in a simplified sense what Lean is about). You'll still need retrospectives and the like to explore how to improve the system, but lead-time trend over time will tell you how bad/good it is. Shorter lead-times is a near no-brainer for improving company performance. While shorter lead-time does directly equal higher velocity or more performance, it does mean you have much more opportunity to navigate tactically and strategically, and improve velocity and performance more often.

After I joined eyeo and saw the dangers of increasing silofication, I started working for turning the ephemeral cross-functional teams into sustained, first-class organizational units. A lot of people who had been at the company for longer didn't see why this was necessary, so they asked me why.

At first, I'd be stumped, thinking this was an obvious thing to do. Then I'd think more about the happy ways of working in a team like that, and how it's just good. Also, being able to point out all the explicit teams in some map would be really handy for new-hires to navigate with. However, arguing like that didn't get me very far. People had more important things to take care of, naturally.

So I changed my line of argument: I looked at the current issues: projects seem to take a long time. Requests spend a lot of time hanging in free air before landing at the right desk. I then started building a case for optimizing our structure for lead-time:

  • If any task that needs doing can bounce between the necessary experts within the border of a team that works tightly together, lead-time will go down.
  • If a domain of related tasks will always go to the same team, their ability to deal with these types of tasks will improve and lead-time will go down.
  • Related, if the inventory of related work-in-process is oriented around a fixed team, they can increase their focus and reduce the amount of concurrent tasks, making lead-time go down.
  • If an incoming project can be take on by an existing team of people who already are able to work and deliver together, yup, you got it, lead-time will go down.
Once people started seeing that my ideas were actually about fixing their biggest issues, seeing that their biggest issues could usually be expressed as length of lead-time, the tone changed quite a bit, and soon after that we got busy organizing the introduction of these new kinds of teams.

How to turn lead-time into an actual metric then? That's for another blog-post.

Comments

Popular posts from this blog

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant

Encrypting and Decrypting with Spring

I was recently working with protecting some sensitive data in a typical Java application with a database underneath. We convert the data on its way out of the application using Spring Security Crypto Utilities . It "was decided" that we'd be doing AES with a key-length of 256 , and this just happens to be the kind of encryption Spring crypto does out of the box. Sweet! The big aber is that whatever JRE is running the application has to be patched with Oracle's JCE  in order to do 256 bits. It's a fascinating story , the short version being that U.S. companies are restricted from exporting various encryption algorithms to certain countries, and some countries are restricted from importing them. Once I had patched my JRE with the JCE, I found it fascinating how straight forward it was to encrypt and decrypt using the Spring Encryptors. So just for fun at the weekend, I threw together a little desktop app that will encrypt and decrypt stuff for the given password

What I've Learned After a Month of Podcasting

So, it's been about a month since I launched   GitMinutes , and wow, it's been a fun ride. I have gotten a lot of feedback, and a lot more downloads/listeners than I had expected! Judging the numbers is hard, but a generous estimate is that somewhere around 2000-3000 have listened to the podcast, and about 500-1000 regularly download. Considering that only a percentage of my target audience actively listen to podcasts, these are some pretty good numbers. I've heard that 10% of the general population in the western world regularly listen to podcasts (probably a bit higher percentage among Git users), so I like to think I've reached a big chunk of the Git pros out there. GitMinutes has gathered 110 followers on Twitter, and 63, erm.. circlers on Google+, and it has received 117 +'es! And it's been flattr'ed twice :) Here are some of the things I learned during this last month: Conceptually.. Starting my own sandbox podcast for trying out everythin

The academical approach

Oops, seems I to published this post prematurely by hitting some Blogger keyboard shortcut. I've been sitting for some minutes trying to figure out how to approach the JavaZone talk mentioned in my previous blog-post. Note that I have already submitted an abstract to the comittee, and that I won't publish the abstract here in the blog. Now of course the abstract is pretty detailed on what the talk is going to be about, but I've still got some elbow room on how to "implement" the talk. I will use this blog as a tool to get my aim right on how to present the talk, what examples to include, what the slides should look like, and how to make it most straightforward and understandable for the audience. Now in lack of having done any presentations at a larger conference before, I'm gonna dig into what I learned at the University, which wasn't very much, but they did teach me how to write a research paper, a skill which I will adapt into creating my talk: The one

Git Stash Blooper (Could not restore untracked files from stash)

The other day I accidentally did a git stash -a , which means it stashes *everything*, including ignored output files (target, build, classes, etc). Ooooops.. What I meant to do was git stash -u , meaning stash modifications plus untracked new files. Anyhows, I ended up with a big fat stash I couldn't get back out. Each time I tried, I got something like this: .../target/temp/dozer.jar already exists, no checkout .../target/temp/core.jar already exists, no checkout .../target/temp/joda-time.jar already exists, no checkout .../target/foo.war already exists, no checkout Could not restore untracked files from stash No matter how I tried checking out different revisions (like the one where I actually made the stash), or using --force, I got the same error. Now these were one of those "keep cool for a second, there's a git way to fix this"situation. I figured: A stash is basically a commit. If we look at my recent commits using   git log --graph --