Software Problems - When You Get Stuck

This post discusses the case study Software Is Not Like Making Shoes

Actually it is like making shoes. At least it should be. It is called software engineering, isn't it? And it is definitely not Research and Development. Managing R&D is an entirely different ball game.

If your design team is unable to progress, than 9/10 they are doing it wrong. In engineering, you use elimination method to detect what the problem is. Eliminate the issues that do not pertain to a problem and you have what requires to be addressed.

But more importantly, what is your role as a Project Manager in this situation?

1) It is necessary to set priority. Get involved in the team's effort. You may or may not be a technical person. But ensure that the team understands that you are as much into it as they are.

2) If you are involved in the team's effort, you will notice that their effort, at times, goes off in an tangent. Stop your team to go on their own voyage of discovery when there is a problem to be resolved.

3) Get the team to list the probable cause of errors - as they understand at that point in time. I like to have a white board on which the points are clearly written down. Once the points are listed, periodically - ideally early morning - sit with the team and address progress on those points. You may have to add points.

4) Ensure all members of the team do not address the same point. Use the white board to list responsibilities against each point.

5) Sometimes it is a good idea to stay with the team late into the night, if they are doing so. Apart from bonding, you will also notice how effectively they are working to solve the problem.

6) Realize that monotony and frustration can set in if a problem prolongs. Step in to give breaks as and when you see it happen.

7) Always, always, involve the customer. Hold regular teleconferences and send regular - daily, if agreed to - status reports.