Iteration 7 Retrospective Notes

Owned by Darius Jazayeri
Sep 18, 2013
2 min read

Action Items from previous iteration

  • DJ to email about ITSM-3609

    • Email happened. Things are stuck though. Address this after 2.0 release.

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

    • Not done. (But he did this right after.)

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

    • Nobody was blocked this iteration

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

    • Had no problems with this

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

    • Had no problems with this

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

    • Rafal tested something. Wyclif didn't.

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

    • No problems with this

  • 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

    • No problems with this

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

    • No problems with this

What went well

  • (Lee) Finally got a tiny bit of database cleanup working on UI test.

  • Made consistent progress on our priorities for this iteration: Clinician-facing Patient Dashboard, and Patient Lookup App

  • "91% done" with functionality for the OpenMRS EMR 2.0 target. Pretty good!

  • Rafal did some testing! :)

What didn't go well

  • (Lee) Not real happy with the UI test framework database support. So, no additional UI tests have been done.

  • Iteration ends with red CI :(

  • Didn't complete the tickets i picked up in time though i still have a day to go (Wyclif)

General comments

  • Next iteration is all about packaging and bugfixes. Functionality need to be finished ASAP or delayed until after 2.0 release

  • Better to finish off a mostly-done ticket than work on a new one, because the former can provider end-user value sooner.

Action Items

  • (Next iteration) Continue pushing on ITSM-3609

  • RK to create ticket about dedicated scheduler user in demo data (from last time) https://tickets.openmrs.org/browse/RA-229

  • Every dev should test some stories every iteration (ongoing, especially after ui test framework is ready)