Retrospective to analyze what went wrong and well over the new development team, impressions and findings.

Retrospective notes:

Retrospective 1.7.pdf

Actions

  • Team should be sitting together. Possibly TT.0.A-Wing
  • Skype calls to be arranged for regular - planned absences.
  • P.O. Should give a walk-through to new members of the team for a better immersion.
  • DS Architect should inform of new releases and its consequences.
  • No labels