Collaborating as a Team
This article is written as opinion. The opinions expressed within are solely those of the author, and do not represent the views of Red Hat.
One of the major issues facing Software Development Team is Collaboration. As such, a lot of software has been created to help improve collaboration between programmers. However, as some solutions are created, it seems to open doors to other issues. So, with a lot of software at our disposal, programmers begin to get distracted with too many applications for collaboration. The use of email has been efficient but recently a lot of organizations are beginning to avoid it as it has begun creating a new set of issues.
Collaboration is key. Collaboration is important. However, to collaborate in a more efficient way, better methods of collaboration have to be devised or we will continue in the same loop of lack of collaboration. In my organization, we have chosen a particular step of collaboration, which we think we can test over time, and see how it works. Nevertheless, the goal of Lean Organizations is to pivot or persevere on whatever concept they try.
So, the basic mode of collaboration is by daily updates. We use the application Slack to keep everyone up to date with the current activities we all are working on and if anyone has any major issue, they can use that opportunity to point out their issue if there is anyone who can help.
The daily update method was chosen after the daily stand-up meeting seemed to not be producing the much-needed result. The daily stand-up was somewhat restrictive in that all programmers must be available at the same time of the day. However, the daily update provides a window for giving an update within a certain time range and programmers are supposed to give an update anywhere they are within that time.
The daily update method is not without its own flaws as some people forget to report their daily issues for lack of Internet or simply have one issue or the other. However, with the constant reminder about daily updates, people seem to keep up to speed.
In addition, meetings are needed but should definitely be minimized. Impromptu meetings should be discouraged and if any meeting is to be held, time should be given to enable people to prepare for such meetings. Programmers really do not like meetings and an impromptu meeting is more annoying than a normal meeting.
We schedule meetings at a particular time of the week so that programmers can adjust their calendars for that particular period so that everyone is aware of the meeting. Well, we are still experimenting with these collaboration methods but more can still be done to improve.
Concerned with how tasks are assigned and resolved, we generally use JIRA. JIRA has helped solve many issues on designing Kanban Boards, scrum boards, and others. Support ticket issues are also assigned using JIRA. However, we continue to experience issues with Internet and familiarity with using JIRA, with good Internet service, the issue with JIRA would be resolved.
As more collaborative methods are developed, the collaboration between team members will be updated, improving productivity.
For a framework for building enterprise Java microservices visit WildFly Swarm and download the cheat sheet.