How to better collaborate cross stages
Why this issue
As we are looking at user problems more holistically, there will be more opportunities for us to collaborate across stages. As we are growing, it might be discussed earlier than later.
There might not be a perfect rule for the best cross-team/stage collaboration, but I believe we could come up with tips or guidelines to help us improve on this because we are smart, we love to work with each other, we treat Gitlab users impartial regardless of their personas and wish the best experience for them
The game plan
I have to think of answering the following questions will help us come up with some guidelines, and after having the guideline, we might have a checklist in the issue template to help us remember what to do.
Free feel to give suggestions of questions or the game plan!
Question list
- When do I need to collaborate with the other team?
- Does the team who initiates the issue need to lead the issue?
- When to contact the other team(s)?
- What information will be useful for both teams for better communication?
- What needs to be agreed upon for better collaboration?
- Tips for better communication cross team
- How do we structure bigger communication: epics? issues? tasks?
- How can we find the right DRI for certain feature
- [How do you determine if a topic is cross-stage or not?](#2150 (comment 1168137014)
Draft guideline
Expected result
-
Handbook guideline for cross-team/stage collaboration guideline -
Issue template/checklist to help us better cross-team/stage collaborate