Sprint Wrap Up
Attendees
General
- Indicates who took minutes -
- Google-hangout at:
Agenda
- Meta analysis of sprint process
- Summarize final state
- Walk through in-process and unstarted tickets
- Teeing up for next sprint
Minutes
See also 2013-10-02 FF Tech Mtg for Wrap Up from MPDL
Esme
- Slightly hung-up in the code
- Productive on the documentation side
- Generally, it was a productive sprint
- Stand-ups were effective and timely
- Keeping stand-ups to 15min, then have detailed discussions afterwards
- Will be available for helping with 'acceptance testing' of triplestore
Mike
- Getting better at breaking tasks down
- Getting better at writing tests
- Better communication about how fcrepo-commons/test.jar works could help
- Creating mock objects can be tedious
- Unit tests are effective at revealing implications
- There were internal institutional distractions
- Would like to work from home during sprints
Greg
- Was pulled in many directions
- Local priorities
- Scrum master
- F4 coding
- Slightly less productive than usual
- Would like to work from home during sprints
General
- Pivotal: remove use of checker-flag (releases)
- Pivotal: use epics
- Pivotal: order tickets by priority
- Scrum master needs to know intentions of tickets before sprint
- Easy to facilitate meetings
- More difficult to deeply engage in specifics of tickets
- Esme to be scrum-master sprint #7
- Great that Eric submitted PR to modeshape
- Max Planck will be working under individual accounts, instead of as an institution
- Useful to get another developer involved with triplestore work