Skip to content

Sprint 2 Retrospective

MartinsLucas edited this page Apr 25, 2017 · 4 revisions

Sprints 2 Retrospective

Introduction

That was the firts sprint without the two members that left the course, so there were three trios. The team started to implement features not related to the Game Engine.

Went Well

  • Team engagement in the code.
  • Game Engine completed and working properly.
  • PEP8 customized.
  • Communication improvement (integrated tools).

Went Bad

  • Technical debts.
  • One member missing. (Traveling)
  • Programming techniques missing in code (due to team inexperienced).
  • Still no tests.
  • ZenHub underused.

Improvements

  • Two weeks long sprints: To compesate technical debts
  • More discipline in applying techniques
  • Refactor code
  • Start testing

Knowlegde Board

Sprint 2

Clone this wiki locally