/
Backlog Grooming Sprint 12

Backlog Grooming Sprint 12

Jul 12, 2017

Attendees

Paweł Gesek, Jake Watson (Deactivated), Brandon Bowersox-Johnson, Chongsun Ahn (Unlicensed), Josh Zamor (Deactivated), Mary Jo Kochendorfer (Deactivated), Anna Czyrko (Unlicensed)

Notes

Expressed a desire to begin focusing the team by service and UI. We will identify leads for each service to facilitate coordination among the group. This is a shift from the current "all hands on deck" and will require VR preparing a list of tickets to begin shifting towards parallel work streams.  Mary Jo would like us to begin addressing tickets while moving forward on requisition functionality. Ideally, we could start implementing RBAC in requisitions, improve reference data, and emergency requisitions. We will hold off on moving forward with Order Exports for now.

Key points:

  • OOAD refactor will wait
  • Will split tickets by service
  • Brandon, Mary Jo and Josh to work on cleaning up tickets
  • Plan to do estimating on  during the SoS

All bugs:  Getting issues...

We've prioritized the following bugs.


THEME: CLEANING UP, UI for Convert to Order & View Order, and new Requisition template columns

Prioritized Tickets

Reference DataRequisitionUIDev/Build

VillageReach

OLMIS-1120 - Getting issue details... STATUS

OLMIS-1162 - Getting issue details... STATUS

SolDevelo

OLMIS-1118 - Getting issue details... STATUS

OLMIS-1104 - Getting issue details... STATUS



RAML:

OLMIS-894 - Getting issue details... STATUS

Wait for sprint 13: OLMIS-1187 - Getting issue details... STATUS

SolDevelo

OLMIS-1223 - Getting issue details... STATUS

OLMIS-1152 - Getting issue details... STATUS

OLMIS-882 - Getting issue details... STATUS

OLMIS-1032 - Getting issue details... STATUS

OLMIS-1092 - Getting issue details... STATUS (should be quick)

OLMIS-1175 - Getting issue details... STATUS

OLMIS-1077 - Getting issue details... STATUS

OLMIS-1164 - Getting issue details... STATUS

OLMIS-930 - Getting issue details... STATUS

OLMIS-929 - Getting issue details... STATUS

OLMIS-752 - Getting issue details... STATUS

OLMIS-870 - Getting issue details... STATUS

OLMIS-934 - Getting issue details... STATUS

OLMIS-869 - Getting issue details... STATUS

OLMIS-933 - Getting issue details... STATUS

Wait: good potential for sprint 13

OLMIS-924 - Getting issue details... STATUS

OLMIS-887 - Getting issue details... STATUS

OLMIS-886 - Getting issue details... STATUS

OLMIS-839 - Getting issue details... STATUS

OLMIS-1134 - Getting issue details... STATUS




VillageReach

OLMIS-1067 - Getting issue details... STATUS OLMIS-1024 - Getting issue details... STATUS OLMIS-1221 - Getting issue details... STATUS OLMIS-1036 - Getting issue details... STATUS OLMIS-1235 - Getting issue details... STATUS

SolDevelo

Clean Up

OLMIS-1088 - Getting issue details... STATUS OLMIS-1218 - Getting issue details... STATUS OLMIS-1216 - Getting issue details... STATUS OLMIS-1215 - Getting issue details... STATUS

New Features

OLMIS-1233 - Getting issue details... STATUS OLMIS-1224 - Getting issue details... STATUS OLMIS-1220 - Getting issue details... STATUS OLMIS-1214 - Getting issue details... STATUS OLMIS-1123 - Getting issue details... STATUS OLMIS-494 - Getting issue details... STATUS

3.0 Bugs

OLMIS-1169 - Getting issue details... STATUS OLMIS-1165 - Getting issue details... STATUS OLMIS-1068 - Getting issue details... STATUS OLMIS-1160 - Getting issue details... STATUS OLMIS-1167 - Getting issue details... STATUS OLMIS-1225 - Getting issue details... STATUS OLMIS-1214 - Getting issue details... STATUS

VillageReach

OLMIS-1226 - Getting issue details... STATUS

OLMIS-1013 - Getting issue details... STATUS

OLMIS-1069 - Getting issue details... STATUS

OLMIS-1170 - Getting issue details... STATUS

OLMIS-1234 - Getting issue details... STATUS

OLMIS-1168 - Getting issue details... STATUS

OLMIS-1186 - Getting issue details... STATUS

OLMIS-1184 - Getting issue details... STATUS


SolDevelo

OLMIS-982 - Getting issue details... STATUS

OLMIS-976 - Getting issue details... STATUS

OLMIS-1138 - Getting issue details... STATUS

OLMIS-1183 - Getting issue details... STATUS

OLMIS-1185 - Getting issue details... STATUS

Wait for sprint 13:

OLMIS-1109 - Getting issue details... STATUS



Ticket clean up questions

  • Are OLMIS-966 and OLMIS-1162 addressing the same issue? (They are two different issues, so I updated the table above. -Brandon)
  • OLMIS-1120 needs a review from Brandon Bowersox-Johnson and Mary Jo Kochendorfer (Deactivated) should we break this down? There are some related tickets like OLMIS-882, OLMIS-1074. (Response: 1120 needs significant work to explain what is intended and give acceptance criteria; in its current form it is not ready to work on. Tickets 882 and 1074 are related to each other, but not duplicates, so it's fine to work on both. -Brandon)
  • OLMIS-1104 needs a review from Brandon Bowersox-Johnson and Mary Jo Kochendorfer (Deactivated)
  • OLMIS-1077 needs a review from Brandon Bowersox-Johnson and Mary Jo Kochendorfer (Deactivated)
  • Are OLMIS-852 and OLMIS-956 still needed? Is it blocking anything? (Response:  Mary Jo Kochendorfer (Deactivated) and Josh and Brandon need to talk about these; both are Pengfei tickets in progress with little action since September; I'd like a quick group conversation to answer Mary Jo's question about whether they are still needed at this point.)
  • RAML tickets. there are a couple tickets out there (OLMIS-1175, 1170, 1110, 976, 894) What do we think is a reasonable step forward? (Mary Jo Kochendorfer (Deactivated) I had a number of suggestions here: 1175 is very reasonable and a small fix; I believe we should do it. 1170 relates to 1069, and I'd like to talk to Josh about how we do the parts of both that are mission-critical. 1110 I suggest we wait on for a future sprint. 976 I suggest we do now. OLMIS-1138 is another related RAML/Swagger issue that I believe we should do now (because not having it makes our Sonar test coverage reports inaccurate.) Chongsun agreed to write up a ticket that suggests what next step with RAML we can feasibly take during this next sprint, and I believe his ticket is related to the ideas in 894. -Brandon)
  • OLMIS-1013 is a contract test. Comment: This seems to be the next/most appropriate contract test to work on, and I think we should push ahead with contract testing. -Brandon
  • OLMIS-1035 is the gold standard extension point. (Brandon Bowersox-Johnson is 1035 the ticket you meant?)


Other potential tickets

Next steps


Related content

OpenLMIS: the global initiative for powerful LMIS software