-
The best way to add more distance between two teams is to move the collaboration method to Jira Tickets Damn, it's so difficult to empathize with PT-423 You lose all the human connection this way 😓Permalink On twitter.com
❤️ 4 Favorites Mood -1 🙁
-
Yet, I understand why this happens. Without the proper effort by the team members, we inevitable go into that direction. - SLAz - Freeing the people that need to carry with the "request" and be able to manage more "problems" at once.Permalink On twitter.com
-
By allowing Ticket collaboration, you free the upstream teams and moving the workload to downstream teams. You don't remove the bottleneck, you just move it from one side to other.Permalink On twitter.com
-
The problem becomes when the upstream is operations and the downstream is product-engineering teams. In this process, you lose so valuable feedback. Delaying a proper solution because lack of understanding the root problem cause.On twitter.com
-
We need to move from - Ticket 33. Fix this. Into - Discovery 33. What's happening, why happens, how to prevent to happen again. Involve Upstream teams in your discoveries, more if they are Ops facing customer problemsPermalink On twitter.com
-
Their feedback and understanding of the customer needs are so valuable. Be careful introducing Ticket collaboration, you might reduce drastically innovation and proper business domain experimentationPermalink On twitter.com
-
Even better, shouldn't be ops part of a Stream Aligned Team? 🤔 If a team needs to be cross-functional to serve the customer needs, that implies also OpsPermalink On twitter.com