HAS THIS HAPPENED BEFORE?

Hopefully, the answer will be a ‘yes’ for the majority.

Mainly, this kind of scenario can happen within a big project team especially when working remotely.

Here I will describe three main reasons that can be happened,

1. Miscommunications.

As I said when working on a big project and with a big team, managing each individual work is not an easy task. Hence all most of all software projects are using some repository and different platforms for CI/CD to manage every individual’s task and do the releases.

So if I take the above example, there the developer has committed his changes into a different branch but DevOps has deployed the build in another branch. But the developer doesn’t know the build has been done in which branch. So the developer thinks the changes are in the new build and he informed QA to test and moved the task into the Ready for QA status. Only after QA testing, the developer will know about the deploying issue.

2. Technical and network issue.

There may be technical and network issues while committing the code, and also there can be miscommunication due to technical and network issues in the mode of communication.

Suppose, the developer has sent a message or email to the DevOps mentioning that he has committed the code into the “feature branch”. But due to network or technical failure of the communication mode, the message didn’t send to the DevOps at the same time, or the message was delayed to receive, or maybe the receiver hasn’t checked his recent messages.

3. Takes no responsibility.

If I take the above example, the developer should have the responsibility to ask from DevOps before committing the code or after committing the code, if the developer is skeptical about this. And DevOps also should be responsible for checking the commits and inform the developers about in which branch the build is going to deploy.

So let’s have a look at the solutions to overcome the above situations.

1. Having feedback right away from the teammates and exchanging questions, concerns, and answers.

It is better to have to keep good communication between team members. And if there is anything that needs to be discussed or in decision making, sorting it out those then and there is a good technique in order to minify the issues. And also by taking feedback right away will keep up the understanding of the tasks as well.

2. Use a reliable mode of communication.

There can be any technical or network failure at any time, we can’t predict those, and we can’t avoid those at 100%. But what we can do is, we can make sure our communication mode is reliable. Since comments, emails, messages could get lost or not seen very easily, we should use proper and reliable communication mode.

When we are working remotely or working from home, maintaining good communication is essential. So we can use Skype/zoom calls to confirm the things.

Using professional ways is also fine but what matters is reliability.

3. Take individual responsibility.

When it comes to responsibility, we all should be responsible for the tasks that we are assigned to.

Instead of telling I have committed the code in to feature branch and thinking that the changes are in new build, the developer should ask from the DevOps that “To which branch we should commit our code” or “I have committed to the feature branch, so can you please deploy from feature branch”.

We can’t blame others, instead, we can take responsibility for our individual tasks, and then as a whole team, we can be successful in our projects as well as in career.

At last, not least COMMUNICATION IS THE KEY to success in our life.

Related posts:

Given that you clicked on this article, I’m sure you already know that. As a leader, it’s great to be in a culture that you and your team want to work in, encourages collaboration and produces…

Manteman kalian tau nggak, kalo selama ini tu ada cara mudah buat ningkatin pemahaman belajar kita loo!!! Aku uda tebak pasti sebagian dari teman teman masih ada yang malas buat baca buku kan? jadi…

There are two conversations happening in our minds at any time of the day. Especially when it feels like the journey you are on never seems to get better and sometimes maybe even darker.