Skip to end of banner
Go to start of banner

ERM Sprint 62 Retrospective

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Current »

Agenda

  1. Review Retro Board (10 mins)
  2. Voting (2 mins)
  3. Discussion (15 mins)
  4. Summary Actions (3 mins)


Apologies 

Retrospective

  • Can we encourage participation of testers in the sprint review and retrospective processes - make testers feel more part of the core team and process - testers say they won't hold back from contributing tho if a burning issue crops up
  • John made first PR - thats a good milestone
  • John - Flow improving - familiarity with tech stack improving, groovy & grails improving
  • Problems - it's hard at the start when everything is new, language, environment, team, etc
  • Adi - Solid progress on bigtest
  • Peter - Access to server and config of VMs is still a problem
  • Gill - Good to see progress 
  • Kurt - Flow improving with tech stack, similar issues with transitioning to the new stack etc
  • MD - Encourage people to participate in the public chat on erm-dev for knowledge sharing and comms
  • Steve - Been away most of last sprint

Personal highlights

  • First PR - Solid milestone
  • Good to see new functionality appearing in deployed systems
  • Familiarity with tools and techniques improving
  • Bigtest infrastructure installed - good step forwards
  • General Tooling and onboarding improving

What went well

  • Really great feedback from the stakeholders and project about the quality and efficiency of our work - got some explicit feedback from Kirstin.

What caused problems

  • Onboarding
  • Insufficient communication in public channels on slack
  • Devops problems impact development priorities - as we're a shared resource
  • Not enough cross knowledge sharing going on


Discussion Notes

Actions

  •  
  • No labels