Sprint Wrap Up

Attendees

General

Agenda

  1. Meta analysis of sprint process
  2. Summarize final state
  3. Walk through in-process and unstarted tickets
  4. Teeing up for next sprint

Minutes

See also 2013-10-02 FF Tech Mtg for Wrap Up from MPDL

Esme

  1. Slightly hung-up in the code
  2. Productive on the documentation side
  3. Generally, it was a productive sprint
  4. Stand-ups were effective and timely
    • Keeping stand-ups to 15min, then have detailed discussions afterwards
  5. Will be available for helping with 'acceptance testing' of triplestore

Mike

  1. Getting better at breaking tasks down
  2. 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
  3. There were internal institutional distractions
  4. Would like to work from home during sprints

Greg

  1. Was pulled in many directions
    • Local priorities
    • Scrum master
    • F4 coding
  2. Slightly less productive than usual
  3. Would like to work from home during sprints

General

  1. Pivotal: remove use of checker-flag (releases)
  2. Pivotal: use epics
  3. Pivotal: order tickets by priority
  4. Scrum master needs to know intentions of tickets before sprint
    • Easy to facilitate meetings
    • More difficult to deeply engage in specifics of tickets
  5. Esme to be scrum-master sprint #7
  6. Great that Eric submitted PR to modeshape
  7. Max Planck will be working under individual accounts, instead of as an institution
  8. Useful to get another developer involved with triplestore work

Actions

  • No labels