...
- Meta analysis of sprint process
- Summarize final state
- Walk through in-process and unstarted tickets
- Teeing up for next sprint
Minutes
Reflection
- Mike
- Sprint goals were reasonable
- Versioning is done
- Rest of the time focused on locking
- Prefers development sequence: functionality, ITs, unit tests
- Unit tests sometimes bring significant overhead
- It is important to have collaborative design time
- Thurs committers call is often a good time for this
- Longshou
- Spent much time getting up to speed on the project
- Kevin
- Selection of tickets were good
- Having more time to "take-in" the bigger picture would be good
- Extended stand-ups were helpful
- Esme
- Was good sprint, even though was pulled into Hydra work
- Mocks can be painful
- This is frustrating
- It may be helpful to capture some lessons-learned in the wiki
- Lesson-learned: not to mash multiple tickets into a single branch
- Learned "git cherry-pick"
- Will document git's ability to checkout PRs
- David
- On holiday during sprint
- Good progress on usecase sign-off
- Andrew
- Accomplished sprint goals
- Great team
Tickets
- Mike: will be breaking locking ticket into more tickets
- will be committing today
- Mike: modeshape locks, put into icebox
- Esme: 4xx ticket
- seeing mixed behavior in running the tests
- Kevin: Tomcat Roles Principal Provider