Please enable JavaScript.
Coggle requires JavaScript to display documents.
Overall RETRO (04/11/2017) (:checkered_flag:Establish a (rotating) role of…
Overall RETRO (04/11/2017)
Beta coordinator
- when preparing beta, define a team who is responsible for beta build preparation and contact point for other teams at the start of the sprint. (In a similar was we have for MSP.) – (Management team)
team who is responsible?
common planning - we should agree which team
Confluence page for checklist for Beta?
review and update the page
Bohumil
:checkered_flag:
Establish a (rotating) role of build guardian
(currently occupied by poor Ladik). The build guardian team will: (Management team)
a. Watch Core builds
b. If the build fails, does the initial investigation and find the guilty submit
c. Note: this might involve other teams (architects, Apollo, PerfStack, etc.)
d. Makes sure that fixing the build (including automated tests) takes priority over new feature work in sprint
e. Open question (we didn’t agree): Do we want to track failed builds in Jira or Confluence or not at all?
Nobody can submit in case when build is RED
Team should be responsible (as we have for MD schedule )
:check:Clear description of the new process
who should fix automation
who should be responsible for CLS
create Jira cases for such or reopen old
ask Lada for more details
Robert
Locking the builds on perforce
Revert all the fixes
External components - do not take every builds to CORE
Second step for Personal builds
MSP
– use MSP2 in the next sprint to improve MSP preparation: (Management team)
a. Fix known MSP issues (Core manifest)
b. Update MSP preparation checklist
c. Fix the build script (if there is any work remaining after Yuriy’s fixes)
MSP preparation_Retro outcomes
(Hubble team)
Consider doing an early dry run of MSP with dummy CLs to confirm it is indeed working - automate applicable
JanKmetko
Permissions to promote the packages (Lviv and Brno side)
PetrLokaj
Core foundation
is going in too many directions in parallel. Focus better. (Legend team)
Changes in product are difficult
(e.g. copyright). Let’s make sure that everything we do makes further changes cheaper = do clean design and code (Legend team)
Stabilize continuous delivery pipeline (Legend team)