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!

Hire Fast, Fire Fast? Not so Fast.

Silicon Valley is full of advice and it frequently comes from people who have little experience on the subject matter.  A popular topic surrounds hiring and terminations with the king catch phrase being: “Hire Fast, Fire Fast.”  To me, what that usually means is lack of diligence, thought, communication and courage.

When hiring people love going with their gut feel, often with disastrous results.  There is an obvious subject of diversity of thought, appearance and background.  When thinking “fast” you are probably hiring people like yourself because humans quickly react to people who they believe are in their tribe.

A startup that lacks the resources of a big company often becomes so desperate to get technical staff that when a decent candidate comes along, excitement ensues and the employer doesn't slow down to put them through a more rigorous hiring process.

I highly encourage technical founders and engineering executives to write out their precise hiring process.  Of course, y…

Pull Requests and Code Reviews

Software development involves a great deal of collaboration.  One of the most basic blocks of collaboration on a software development team is a code review.  There have been many different ways of doing code reviews over time, some of this has been dictated by the tools available.  Git and online source collaboration tools created a set of best practices that are worthwhile of adopting on any team.

About a month ago I have looked at various articles about how to best create a Pull Request (PR) and do a code review and the attached presentation is the result of this research.  The presentation can help you guide your team and develop a set of collaboration practices that works for your particular situation.

It’s good to start out with why to seek a code review.  Having clarity about your intentions helps you guide the person helping you with code reviews and also to manage your expectations about you can get out of the code review.  The reasons for seeking a code review are generally …