Attendees

• Andrew Woods 
• Osman Din
• Unknown User (escowles@ucsd.edu)
• Nigel Banks

General

• Indicates who took minutes - 
• Call-in: Google-hangout at: 
  
  • https://plus.google.com/hangouts/_/event/ccnv0ba94h3fb2je3gscunqc49g

Agenda

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

Minutes

Reflection

1. It may be useful for all to read other people's tickets
2. Considering lessons from sprint-b1
   
   • Still did this
     
     1. Few tickets are actually complete
     2. We should create specific tasks scoped to the scale of ~task per day
     3. Tickets were too broad
3. How do we get the tickets to the right level?
   
   • Could go back and update size of tickets during development
4. Assumption is that small tickets are valuable
   
   1. Allows for others to chip in on larger work
   2. Reflects clarity of task
   3. Allows entry-point for discussion implementation strategy
   4. Easier to review
5. Process:
   
   1. Start sprint with high-level ticket
   2. Break-down tickets on first day of sprint (Monday)
   3. Further break-down tickets on daily basis
6. Discussion about sprint schedule mon-2nd-thurs
   
   • Consensus that the schedule is constructive
7. Daily meetings, tend to go longer than 15min
   
   • Start by ensuring everyone gets 3-4min as first pass
   • Institute after-meeting for extended discussions
8. Idea of working in feature teams?
   
   • Pair-programming tends to be slow
   • Collaborating can potentially be effective
9. How to scope tasks/features to a sprint?
   
   • Sometimes we get stuck in tasks of uncertainty
   • We need to ask the team questions
   • That includes asking modeshape

Actions