List of Projects OSRA - Support system Team meeting summaries Sprint 1 retrospective, Sept 16 2014

Sprint 1 retrospective, Sept 16 2014

Updated almost 5 years ago by Nikita Avvakumov

Bad:

  • Code reviews too long (progress stops)
  • Notifications from GitHub insufficient
  • PRs (too?) large
  • Stories too big & complex
  • Stories not independent
  • Mis-estimates of time & effort
  • Lack of communication re:availability

Good:

  • Well-written user stories
  • Good feedback on PRs
  • Good discussions outside of code reviews
  • All stories accepted by client

Strategies:

  • PRs: 24hrs without activity - raise priority, notify team
  • PRs: everyone has authority to merge others’ code
  • break up user stories into smaller chunks
  • no fixing existing code as part of new story
  • reduce interdependencies with smaller stories & story prioritization
  • Use Slack!

Actions:

  • Be proactive. Draw others' attention to stagnating PRs
  • Use own judgement in determining whether a PR has been sufficiently reviewed, based on magnitude of changes
Revisions

comments powered by Disqus