Skip to main content

First Public Beta of DS Pro is *DONE*

The last signature has gone on the sign off document.  The team is gathering early feedback on the product and everyone is starting to get a warm fuzzy feeling of accomplishment.  Releasing software is fun.

To a certain degree it is always a gamble.  You are gambling that people will find your software useful.  You are gambling that you can achieve the quality customers expect.  You are gambling that you can provide the solutions for the problems scheduled by the sprint.

At the time of shipping a lot of the stars need to align.  If I was to compare shipping software to something I would compare it to the game of football - absolutely everyone needs to play their position and know what other people are doing or the entire process doesn't work.

Project Management needs to clear up the obstacles and take the paper work load off the technical staff.  Development needs to produce features and minimize bugs.  Quality Assurance needs to define the right test passes and run them to show the quality of the product.  If any one of those disciplines doesn't play their role correctly the product doesn't ship.

While all these people are involved in any part of the software process it is only during shipping that you see the hard decisions being made and the trade offs play out.  When I was at Microsoft it was a pleasure working with people who have gone through this process many times.  Everyone knew what to expect and what tradeoffs meant.

DS Pro team uses Agile, iterative approach.  It works out great because people get to practice making tradeoffs every single month.  Every month you have to deliver something useful and every month people understand how to cut features, what resources are needed, who needs to do what and by when.

Some people think that you can teach this through a book.  I don't believe so.  You need to experience this first hand before you start getting a feeling of what's important and why. 

Asides from technical issues every new group of individuals poses it's own challenges.  We started out with people taking really hard positions on certain issues and over time they realized that the most important thing is how we play together in order to deliver innovation to the market place.

We are currently in a position where we can make a lot of people's lives easier.  While there is a potential for a profit it is also important to realize that if we can't get our act together we miss an opportunity to improve someone's quality of life.

Post a Comment

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!

There are Only Two Ways to Treat Your Team

There are only two ways to treat your team: take care of them or let them go.  Early in my management career there have been times when someone has been underperforming on the team.  Before I knew better I let my emotions get the best of me: I’d give them the cold shoulder, avoid including them in conversations and look like I was upset with them. Thankfully with some good mentorship I came up with a simple rule: we are helping each other or you are off the team.

One of the biggest mistakes that folks make a lot of times is letting people linger on for too long.  Hiring good engineers is hard and getting new folks up to speed is hard.  You feel like you are going to miss your product delivery plan if you let someone go.

Letting folks linger when you are unhappy with each other creates a toxic environment.  This toxic environment is generally contagious and brings the entire organization down.  Of course you can’t have a constant state of euphoria on your team, but if a productive and…

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 …