| | 1 | = Sprint 26 = |
| | 2 | |
| | 3 | Thanks all for the great sprint. |
| | 4 | |
| | 5 | Keep |
| | 6 | * code review using the pull request method |
| | 7 | * consistent code styling |
| | 8 | * pair programming! |
| | 9 | * beers at end of sprint |
| | 10 | * cobertura, unit tests, findbugs to more rapidly check if changes don't break code |
| | 11 | * very regular email conversations on issues and progress |
| | 12 | |
| | 13 | Try |
| | 14 | * shorter end-of-sprint |
| | 15 | * 'how to demo' should be more precice |
| | 16 | * document requirements in seperate doc (in code base) |
| | 17 | * code quality (tests!) and maintainability (i.e. refactor for understandability; add docs, etc) |
| | 18 | * learn to say 'no', and invest in training |
| | 19 | * be explicit to each other: if you don't agree/understand say so (e.g in pull requests) |
| | 20 | * switch workplaces if this benefits the sprint |
| | 21 | * be more consise during standup: 2 mins per person: done, todo, blockers |
| | 22 | * interupt people if scrums take to long; schedule meetings afterwards if needed |
| | 23 | * during pull request check if javadoc (explaining why/how big functions) and understandeable |
| | 24 | * reply to questions via entry on wiki |
| | 25 | * firefighting budget??? |
| | 26 | * if person is not in office; should report to scrum master before time |
| | 27 | * scrum should start on time!!! |
| | 28 | * pair programming meetings should start on time!!! |
| | 29 | * allocate a story to fix bugs reported in git |
| | 30 | * allocate a story to increase test coverage |
| | 31 | * all new code should have tests attached |
| | 32 | * developers mailing list |
| | 33 | |
| | 34 | Stop |
| | 35 | * put more points than needed! |
| | 36 | * removing people from sprints; people should always be part of sprint |
| | 37 | |
| | 38 | Other |
| | 39 | * data migration between data model versions |
| | 40 | * SOP how to go from test -> production |
| | 41 | * How to deal with uncertainty |
