wiki:2012-10-26_EOS26

Version 1 (modified by Morris Swertz, 12 years ago) (diff)

--

Sprint 26

Thanks all for the great sprint.

Keep

  • code review using the pull request method
  • consistent code styling
  • pair programming!
  • beers at end of sprint
  • cobertura, unit tests, findbugs to more rapidly check if changes don't break code
  • very regular email conversations on issues and progress

Try

  • shorter end-of-sprint
  • 'how to demo' should be more precice
  • document requirements in seperate doc (in code base)
  • code quality (tests!) and maintainability (i.e. refactor for understandability; add docs, etc)
  • learn to say 'no', and invest in training
  • be explicit to each other: if you don't agree/understand say so (e.g in pull requests)
  • switch workplaces if this benefits the sprint
  • be more consise during standup: 2 mins per person: done, todo, blockers
  • interupt people if scrums take to long; schedule meetings afterwards if needed
  • during pull request check if javadoc (explaining why/how big functions) and understandeable
  • reply to questions via entry on wiki
  • firefighting budget???
  • if person is not in office; should report to scrum master before time
  • scrum should start on time!!!
  • pair programming meetings should start on time!!!
  • allocate a story to fix bugs reported in git
  • allocate a story to increase test coverage
  • all new code should have tests attached
  • developers mailing list

Stop

  • put more points than needed!
  • removing people from sprints; people should always be part of sprint

Other

  • data migration between data model versions
  • SOP how to go from test -> production
  • How to deal with uncertainty