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

Lessons from my 9 Year Journey with DocuSign

After over 9 years at DocuSign I am taking on a new challenge.  It’s been phenomenal seeing the
company grow from from 25 to 2000 employees.  DocuSign has changed the way the people do business and I am proud of it.  The next chapter is going to be heading up software development at Tempo Automation - a 25 person startup that is changing the way people produce electronics.  While I am extremely excited about the future, this is a good time to reflect on my journey and share the things that contributed to the success and things that I will do differently next time around.
1: Focus on the Customer One of the key things that contributed to the success of DocuSign and my personal career is relentless focus on the customer success.  From the very beginning our CTO has taken meetings, listened and prioritized requests and feedback coming from customers.  People who could not be bothered by customer requests didn’t last long.  As a result over time our engineering team retained and reward…

Highly Effective Software Teams

A few weeks ago our Board of Directors asked me to present my assessment of the state of software.
 I was hired to organize and grow the software team and the directors wanted to know what kind of a team we needed to build.  I was hoping that I can just reference an article somewhere that would give me the answer, unfortunately I didn’t find anything suitable. During my research I did find some great material that will be helpful if your job is to put together a highly effective software team.
A highly effective software team has the following key characteristics: dependable, committed to shared goals, passionate about technology, respectful and compassionate.  These are not limited to technology industry, it can easily apply to finance, medicine, or sports as well.  Below is the summary and references that I found. Dependable If you are creating a software product, you need to deliver your software to your users.  Your users need to know that you are able to solve their problems on …

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!