Sprint 14

24 Nov. 2016 - 7 Dec. 2016 (sprint starts while Team ILL is away for U.S. Thanksgiving holiday)

Themes

Process Improvements

Team ILL Sprint 13 retrospective:

1) Designate Component Leads: Chongsun=fulfillment; Nick=UI; Josh=platform/architecture/tooling; Brandon=requisition; Josh=referencedata. These component leads will help to groom the tickets in that component, always working with the Architect and Product Owner. We will add components and leads in JIRA, and tell SolDevelo so our component lead is a go-to person and they might name component leads on their side that we collaborate with. Then later we should clean up some old components from JIRA; and talk with @Mary Jo Kochendorfer (Deactivated) about epics, components, process.

2) Don't let tickets roll over; take on a feasible amount of points for sprint 14. Brandon will crunch a few numbers and post guidance on the Backlog Grooming Sprint 14 page.

3) Stop using sub-tasks. Basically use them much less, and only where appropriate. If it's work that happens in parallel, make parallel tasks. If it's step-by-step work done in sequence by one person (not in parallel) just put it in one ticket. If it is UI and API work (or any work that happens on separate components by separate people), then make separate tasks so the parts go through QA and review separately. This might be a bit of extra work to connect related tickets and mark which are blockers, but it also gets rid of the complexities of sub-tasks (like all rolling over to a next sprint if one sub-task is not done).

(click to view full size)

Teams AYIC/TOP:

See SolDevelo Retrospective 2016-11-24

Velocity

Team ILL completed 28 story points. Teams AYIC/ToP completed 124 story points. This was a slight slow-down from the previous two sprints. Let's discuss this during retrospectives. Team ILL is also going to do an exercise to review the scope for 3.0 in case any adjustments are needed.

see Burn-up for 3.0 Release for details

Showcase

Video:

The following 22 tickets were completed this sprint and covered at the showcase:

Key	Summary	Story Points	Status
OLMIS-1419	Update test cases after last sprint (TOP/AYIC Sprint 13)		DONE
OLMIS-1417	"Small" regression TOP/AYIC Sprint 13		DONE
OLMIS-1407	Design for supplying partner scenario - add diagram for tech committee	8	DONE
OLMIS-1405	Design for Supplying Partner - ideation workshop for UI extension	5	DONE
OLMIS-1388	Move Fisheye to new Server	3	DONE
OLMIS-1386	Add configuration settings for external fill for fulfillment	5	DONE
OLMIS-1381	Spike: Select potential FTP server to bundle in reference distribution	5	DONE
OLMIS-1369	Proof of concept: Basic FTP hard-coded workflow	8	DONE
OLMIS-1330	Contract test for initiating/authorizing/approving/rejecting a requisition	8	DONE
OLMIS-1319	Spike: Choose FTP configuration/integration approach for Fulfillment Service	8	DONE
OLMIS-1314	Order Service: split Ordering/Fulfillment from Requisition Service	21	DONE
OLMIS-1299	Apply styling and code fixes to the adjustment modal	3	DONE
OLMIS-1288	Publish openlmis-example-extension to maven	5	DONE
OLMIS-1281	Get namespace for Maven publishing	1	DONE
OLMIS-1279	Extension: Publish Example Service to Maven	13	DONE
OLMIS-1218	Translate unit tests for Requisitions-UI	13	DONE
OLMIS-1178	Requisition repository layer should not use DTOs and should not call external services	3	DONE
OLMIS-1157	Do not construct new objects using no args constructors unless it makes sense	3	DONE
OLMIS-1152	Initiate requisition endpoint should validate the user has right at the facility and program specified	3	DONE
OLMIS-1026	Ability to Extend Entities - "Extra Data"	8	DONE
OLMIS-882	Add Rights checks to requisitions save/submit/approve/delete endpoints	13	DONE
OLMIS-752	Display/Hide of Non-Full Supplies on Requisitions by program	13	DONE

If sub-tasks are counted, there are 51 tickets representing 152 story points completed. View these tickets in JIRA