Software Tales #1

Summary

The Development team is experiencing a bottleneck in resolving an integration test environment issue due to dependencies on external teams and inefficient communication methods.

Abstract

The Development team at a company has encountered a significant problem with their system integration that has led to a series of email exchanges in an attempt to resolve the issue. The problem was initially reported by Bob from the Dev Team, who noticed an issue with the Integration test environment. Jane, the Dev Lead, escalated the problem to John from the Environment Team, who after two hours suggested that Rob from the Infrastructure Team might be able to address the connection issue. However, Rob was outside his working hours, leading to Katy from the Infrastructure Team being asked to look into the problem. Katy indicated that only Rob could handle such issues, resulting in the problem remaining unsolved by the end of the day. The situation highlights two main issues: the team's reliance on external teams to solve problems and the inefficiency of using email as the primary mode of communication, causing delays as team members wait for responses.

Opinions

The team structure appears to be siloed, leading to inefficiencies where one team's productivity is heavily dependent on the availability and responsiveness of another.
The use of email for urgent issues is ineffective; real-time communication tools like Skype could improve response times and issue resolution.
There seems to be a lack of cross-training or redundancy in critical roles, as Katy suggests that only Rob can handle certain infrastructure issues.
The manager, Manny, is aware of Rob's unavailability but does not take proactive steps to empower another team member to resolve the issue, indicating a potential gap in leadership or contingency planning.
The overall process for handling critical issues seems reactive rather than proactive, with a lack of established protocols for escalation and resolution outside of normal working hours.

going in circles

The Development team encountered a problem while working on system integration, a mail thread starts, let’s see what happens:

Bob (Dev Team): “Hey, there is a problem with the Integration test environment”

Jane (Dev Lead): “Hey John (Env Team), please try to figure out the issue, we’re blocked!!!”

… 2 hours later …

John (Env Team): “Please Rob (Infra Team), this is a problem with the connection can you check it?”

… other 2 hours …

Manny (Manager): “Rob is outside his working hours, Katy (Infra Team) can you check it?”

Katy (Infra Team):” For this kind of issues you need to refer to Rob”

The day passed and the problem was not solved, let’s try tomorrow…

What are the problems here?

The team is not self-contained, so it is needed to chase for other teams to get an issue solved.

The communication was mainly through email, so every team member is waiting for an answer offline, some times is better to use Skype.

Do you see any other problem? How would you handle these kind of situations?