In my previous post (#6) I described how there were speed bumps in the team’s process that resulted from them working as individual developers often do. However, this created a few issues now that they were working on a team project. I was able to use that as a teaching opportunity to not only explain why they hit the bumps, but how to use the GitHub project Issues list to rapidly detect the speed bumps, address the issue as a team and smooth the road while improving their process. That lesson was on a Monday during their weekly scrum (team meeting). They understood the usage of labels and new issues and agreed that it would help.
As they worked that week, on their Friday, while I was happily sleeping 7 hours away, Efatha hit a speed bump and immediately raised a red flag and described his problem in the appropriate issue. Doing that alerted the other two guys. When alerted, they went to the issue and sized up the situation. Philemon identified the problem, and posted a link to a specific piece of code he had pushed. He followed with a detailed step by step that would allow Efatha to access the right code. Ash quickly replied that he had just tested the instructions and verified that it was indeed working for him. Efatha made an additional comment and went on with working. Problem solved!
All the while, I was still asleep. When I woke up and looked at my email I saw a flurry of 6 emails to read. When I looked at them I saw that they were a nice thread of 6 comments from a single issue in GitHub. I quickly read through them and realized that they had identified a problem, fixed it, tested it, and were done. All while I was sleeping. All I had to do was sit and be amazed at how they had implemented the process improvements and were now working very effectively as a professional team.
WAY TO GO TEAM!!
Thank you for sharing this wonderful story and we’re delighted to have put your recommendations into practice.
I encourage the collaboration effort between us and the timely communication in maintaining productivity. Because each member played a crucial role-identifying the problem, providing a solution, and verifying the fix. This division of responsibilities and quick feedback loop underscores the strength of collaborative problem-solving in a team setting
Thanks to Michael Kent Burns for the project owner for providing in this project these work-tools, experience and qualities as professional web developer. I, Philemon and Ash have learned a couple of things in this field.
For the best practice in software development, the team use GitHub for issue tracking and communication. We are happy for this progress.