Less is MORE

Often I have come across strategies in software industries where in order to make delivery faster, the team is made bigger. Though it may work in some cases, it may not really benefit long term.

Bigger teams can have its own challenges -

• It is a human limitation that one person can manage max 6-7 team members directly. Anything more than that means spending more time in getting to make the team work together. Effectively, we may end up with multiple team members who are spending their time tracking the project status, people management, distributing work and so on.
• Every individual in a team has his/her own different personalities. Gelling together all personalities and making them work together can be challenging.
• Team work requires getting to know and complement each other. Team building can be challenging in bigger teams.
• Being able to divide tasks in such a way so everyone is kept busy as well as there are minimum dependencies among each other.
• It is super difficult for each team member to holistically know what is being delivered. It involves considerable time investment in being up to date.

With smaller teams, we can get rid of all the above challenges. Lesser the team members, more easy it is to work together. Team members do not struggle to get visibility of their work. It is easy to identify the performers vs non performers and ensure work is distributed. It results in every individual have good sense of ownership and is able to contribute effectively. Throwing the ball and blame game is avoided. Inherently team politics stays away and the focus is on performing and delivering.

One of my most recent wins with small teams has been building a product in just 30 person days. This is the fastest I have built a product in my entire tenure that also involved understanding the domain and designing the UI! The product still has a long way to go, but getting it to a point of demo in this span is nothing short of an achievement. This achievement is with just 2 full time team members (including me) and 2 consultants working 8 hours a week. At the end of it I was myself surprised that we did it...

Less is More is definitely the mantra for software development.

Get out of the comfort zone

Time and again, almost on a daily basis, I see people around me cribbing about their jobs. They have been stuck up in an organization since a long time without any real motivation and learning. The thought that keeps crossing my mind is if you dislike your job so much, if you are literally dragging yourself to office everyday, if you are forever thinking that you could do better things, then why don't these you just do it. Why don't you carve a path for yourself that can keep you happy? What does it take to do that?

Over the years I have noted that a very big aspect of not making the move in that direction is the comfort zone. Over a period of time, all of us tend to get into a comfort zone wherein though we may not be happy with our jobs, it serves the purpose. The major worry for most of us is - 'I need to prove myself all over again' or 'I need to work doubly hard' or 'I am all set here'. Well, if you like doing something and you take up exactly that, how difficult will it be to prove yourself? It may take some initial efforts but isn't it worth it than being stuck up somewhere and continuously crib about it.

What you do and what you get is completely in your hands. If you really want to do something, you just go for it. Stop blaming everyone around you for not making it good for you. You are the torch bearer of your career and it's only you who can shape it, no one else. So think about what it is  you want, either be the change you want to see or look for a change.

Most importantly - Just get out of your comfort zone!