Iteration 6 Retrospective Notes

Owned by Darius Jazayeri
Sep 04, 2013
2 min read

Action Items from last iteration:

  • Get back on the same schedule for iterations and community dev lead (DJ emailed CP. Need to ensure this is followed up.)

    • Wyclif is joining this next iteration now, so we're back on track

  • Stop pulling Daniel off of the RefApp work after a few days each time. 

    • He got the full iteration, at least

  • Elevate priority of ticket about CI-STG being slow ITSM-3609 (needs followup)

    • Commented on ticket last week, got no response from ITSM team. Will send email now. -DJ

  • Rafal to request shell access to ci-stg.

What Went Well

  • We made lots of progress on tickets in the first half of the iteration

  • We had time for extra tickets

  • Almost no problems with CI

  • Managed to get some smaller tasks done while in the dev swim lane

  • 15 tickets completed, with time estimate of 1 week + 4 days (2 weeks + 3 days of tickets still in dev or testing)

  • Am getting more farmilar with the various things around refapp development (Daniel)

  • Some tickets had very useful pointers regarding where to look. Well curated. (Daniel)

  • Tickets are reviewed fast enough for feedback when all is still fresh (Daniel)

What Went not-so-Well

  • Lee made almost no progress on automated UI tests or test framework. 

  • Lots of tickets going back from testing to development, multiple times (combination of stories being unclear, and people being less than careful)

  • Darius is the only one who does manual testing :(

    • DK: not used to testing

    • RK: always "last task for the day", never gets done

  • Didn't account for US labor day holiday in iteration planning

  • As the dev swim lane lead, i didn't get much done as i expected

  • There is still a reasonable number of un documented uiframework features hence end up spending a lot of time trying to figure out things that are actually so simple. :) (Daniel)

Other Discussion Points

  • How could we have gotten Lee unblocked earlier?

    • Most problems are of the "works for everyone else" variety

    • Lee works a lot in evenings and weekends, when others aren't available

    • Server logs contains lots of spurious error messages. Would help to remove the spurious ones.

  • Should we also work on some uiframework documentation tickets? This will make newbies move faster.

    • Daniel to highlight particular point that need extra work.

Action Items

  • DJ to email about ITSM-3609

  • RK to create ticket about dedicated scheduler user in demo data

  • Everyone: be more proactive about helping people get unblocked, even if they don't explicitly ask.

  • Curators should make sure the AC list in a story description is always complete

  • Devs should verify that they address all ACs and ticket comments before marking a ticket as ready-for-test

  • Every dev should test some stories every iteration (ongoing)

  • Community Dev swimlane lead should stick to picking smaller RefApp tickets

  • If you ever lose hours of dev time because something wasn't well-documented, report this, so we can get it documented better for the next person

  • Expand abbreviations on tickets (e.g. ADT), or maybe have a glossary