Please enable JavaScript.
Coggle requires JavaScript to display documents.
Overall RETRO (10/03/2017) (MSP process (What we can do in cases when smth…
Overall RETRO (10/03/2017)
MSP process
Components Version Matrix
Mykola
will share info about builds 320 and 300
What we can do in cases when smth which was already added to the list for MSP will be blocked by other one?
we should react immediately and try to solve it as quick as possible (only for cases which MUST be included) otherwise we can start negotiation to remove this case from the list for MSP
we should have plan B - what to do in such situation > start to communicate that probably will not prepare MSP on time (only in case we have items which MUST be included)
Robert
promised share info about RevRec
the deadline can be missed not only because of fixes - we may get blocked by Falcon etc
why MSP takes 3 weeks?
not only CORE items included in MSP - several projects, hard to coordinate
we need to have a common goal - feeling that we work on one project (somehow fix collaboration between CORE guys and outside the CORE)
we need to have clear pictures what we will have in MSP - labels/added cases to the page, before the start of preparation the MSP (CORE + outside the CORE)
PO should be responsible?
content can not be changed, only in some critical situation
in cases we need to change scope of MSP > send additional email or other type of notification to all people who are involved to MSP preparation
MSP testing
Milan
RM request created in Jira by default and published the build with link
48 customers were download
RM process - we should open RM only in case when we fully prepare the MSP
RM team should be aware of what's inside
RM requests - how to use it? share the outcomes to CORE teams
Milan
and
Katya