Skip to main content

Interruption “Fund” In Scrum


About a year ago I started building a new team at DocuSign.  I hired a few engineers, teamed up with a product manager and started building a portfolio of products that were all designed to plug DocuSign into leading business ecosystems.

I am a big fan of agile project management.  As I evangelize DocuSign technology in addition to managing a dev team I always need a clear answer to where the team stands and what we need to do to get the product shipped.  Overall the personnel and the method worked out really well we shipped on average 1-2 new products or new versions of products every month.

 Now the success is catching up to us.  Several thousand customers have deployed our products and they are starting to use it for business critical needs.  What this means is that now folks are encountering new configurations and new use cases and the issues get escalated to my engineering team through support and sales staff.

Every purist who is saying: “you should have had better documentation / you should have tested all of the possible environments” can sit down and just admit that they have never shipped products in emerging markets with emerging platforms.  The reality is that escalations will happen.

Our solution to this has been to give developers an interruption fund (we call it a “slush fund” internally).  Basically a couple of developers and one QA engineer get 2 days every two weeks to account for interruptions.   If not interruptions come in those folks use the time to improve unit tests, fix build issues and do other things to “pay down the technical debt”.  For your reference the total team size is 6 developers and 2 testers.

My question is: how do you deal with interruptions while running a scrum team?  Thoughts or suggestions?  Hit me up over twitter @mikebz .

2 comments

Popular posts from this blog

SDET / QA Engineer Interview Checklist

After interviewing and hiring hundreds of engineers over the past 12+  years I have come up with a few checklists.  I wanted to share one of those with you so you could conduct comprehensive interviews of QA Engineers for your team.

I use this checklist when I review incoming resumes and during the interview.  It keeps me from missing areas that ensure a good team and technology fit.  I hope you make good use of them.  If you think there are good questions or topics that I have missed - get in touch with me!


SDE/T or QA Engineer interview checklist from Mike Borozdin
If you like this checklist you might want to check out these posts:
Emotional Intelligence in Software Teams  and Good-bye manual tester, hello crowdsourcing!

Two Critical Questions for Your Next Interview

I’ve interviewed probably over 500 engineering and management candidates over the last several years.  There have been a lot of really smart people who have applied at DocuSign, Microsoft and Tempo Automation. A surprising number of them didn’t have a clear answer to these two essential questions:

Why are you interested in joining our team?Why should we be interested in you? 
If you are an applicant, having a prepared answer for these questions is critical.  If you are a hiring manager, you should ask them and have a clear answer to these questions at the end of the first interaction with your future team mate.

In a field where work is somewhat predictable and static, those questions are less critical, but in software development perseverance, ingenuity and focus make all the difference. These are the two main questions that will separate a subpar and a superb hire.

When I discuss those two questions with an applicant I try to go below the surface.  Generic answers like “it says you ar…

Chief Collaboration Officer

When you search for the word “collaboration” on the Internet, the top hits are mostly software packages you can buy.  Software can facilitate collaboration, but it doesn’t make people collaborate on its own.

One of the key functions of a technical leader is to bring a team together, help people share ideas, and facilitate team members helping each other.  When a software leader overlooks this key function, you end up with a group of individual contributing engineers instead of a cohesive team.
Before we get into tactics, we should ask “Why is collaboration important for an engineering team?” 
It’s critical to examine your assumptions, so here are my reasons for why a group of engineers working on their own are worse than a team working together: Smart people learn from each other.Getting your plans and designs reviewed by other people allows you to leverage their experience and check your assumptions.Collaboration produces artifacts that stay after collaboration has taken place (such…