It’s very common and you must have heard it multiple times that “Socialism plays an indispensable role in the success of an organisation”. Even big names of the market like Google, Facebook etc. say that they prefer social person compared to super productive chicken. But what exactly this socialism stands for?
In a team it is usually evaluated with less number of conflicts in teams, how much time team members spend together, how they party together etc. But is socialism limited to this only? Well… It is just the tip of the iceberg and these factors can be seen as an indicator that you have a socialised team.
Recently I conducted an activity in my team. The activity was devised to make team assess how well we understand each other while working together. The observations I made were really interesting. But before jumping onto the observations I would like to share a little background why I thought to conduct such an activity.
On thing which always remains on the top of my mind is how can my team learn and apply new things to be more efficient in their work. On the course of doing so my team conducts weekly presentations on various topics. But bringing that knowledge to actual practice is still a big challenge to overcome. In order to figure out solution to this problem, I took an analogy, and compared these presentations with the theoretical classes of the firefighters or soldiers. And decided to conduct a mock drill through an activity to assess how that knowledge is used in action.
The activity was pretty simple, it was what we assume we do everyday. We decided to build a computer game. We chose game because that is much close to the real world and things can be visualised easily with real world examples. But this time nothing was expected to be coded, instead the idea was to create design on paper using flowcharts, UML diagrams or whatever team will prefer. The whole project was divided into modules and each module was given to a pair of developers and then activity started. After two sessions below were my observations.
- It is really hard for the people to figure out scope of their modules.
- People are not able to conclude how their module will communicate with other modules to exchange data or events.
- People don’t use same terminology to exchange their thoughts.
These problems are actually not related to the technical competencies, instead more related to socialism in work.
Another buzzword in the market related to software development is “Agile Development Methodology “. And agile works on the foundation of a team which understand each other really well. And this is the only reason why less documentation is done in agile.
Now…you must be thinking what’s the solution then? Well the solution which comes to my mind and I am trying to follow seems simple just like this problem. Considering and practising this as the part of daily work. Continuing the analogy I took, army does mock drills for making solders understand each other at work and parties to make them emotionally connected…..after all we are humans and driven by emotions.