Skip to content

Sprint 2 Retrospective

Paul Coen edited this page Apr 12, 2018 · 1 revision

What went well during the sprint cycle?

  • We started earlier
  • We almost achieved our sprint goals
  • We had a lot less dependencies
  • Communication was very good among the team
  • Components that required team work were developed much smoother then last sprint

What went wrong during the sprint cycle?

  • Not enough testing initially
  • We did not plan as well as we could have
    • Not enough planning with regards to accounts
  • Time management remained a recurrent issue

What could we do differently to improve?

  • Write and Use more tests
    • Test before pushing
  • Pair back-end and front-end people together on each page's task
    • Develop small teams among our group
  • Refactor our code to be both easier to read and be more functional
    • Separate all our pages based on purpose (gone will be the days of landing being our home for html)
    • Only use either tabs or spaces (we have a problem with this)
    • Create a short standard for coding our project
    • Stay more consistent with our work
    • More commented code so others know what happens
  • Plan more regular meetings

What was the status of our actions?

  • Split work by page
    • It did not fix the front-end/back-end split
    • It did however allow us to define the tasks better
  • Elaborate tasks more (BE MORE SPECIFIC)
    • This tied in heavily to splitting the work by page
  • More time for planning meeting and planning overall
    • We need to consider time for learning thing we use
      • Issue is kind of fading, we all felt like we knew what we were doing better with regards to back-end and front-end
    • Start sooner
      • We did and it worked well, we almost finished our sprint goals
      • Estimating things went a lot better, we had a lot better time management
    • Our meetings ended up taking less time now and we felt like we got more done
    • With regards to planning overall, we still need to do more