Overall RETRO (09/14/2017)
Communication pipeline issues. It is unclear how to communicate between code owners. How to handle Communication lags? (Ihor Obrizan)
Additional communication need (Core tech leads email group etc)
Contact point for each area - confluence page, etc (Core component ownership page on confluence)
Some Chanel for communication - Skype, Lync, etc
Orion Core chat is the right place to ask questions
Devops work done during sprint consumes around 20% of team's capacity and only one team is able to work on devops stuff (Petr Lokaj)
Build pipeline/installers - do we need separate supportability component? NOT for now
We need to have several teams who can work with build pipeline - in a different locations - Lviv, Brno
We need Duty as we have for CIs? NO, we should do it during build guardians (update the page if needed)
Paring fix the issue - skype/webex/etc
PO/EM technical requests within sprint consumes team's capacity. I would like to agree on a way how to cover it (Petr Lokaj, Hubble team)
On planning sprint we should have some free capacity for such activities as - code review for example we can have some external request
Request come > team should think about the impact and risk do not finish cases which you already have in a sprint and share their feeling to PO and after they can pick up such requests
During implementation topology - new stories is coming and we need to have clear picture and think about risks/influence/etc
we should be aware of all things as much as possible before the implementation
We should have the same and clear priorities for each sprint from all sides (PO, EM, team)
External sprint review VS internal sprint review - what's the difference, except participants (Hubble team)
Find info about external/internal reviews
Clarify the rules which content can be added for external review
Meeting in Brno (techleads) when Lviv guys will be at office Milan
Organize separate meeting before next EXTERNAL review if needed