/
Backlog Grooming Sprint 116

Backlog Grooming Sprint 116

Jan 14, 2019

Dates: Jan 3, 2019 - Jan 16, 2019 

 

Team Parrot Sprint

Sprint Goal: Process to deprecate test cases and more automated testing (Sprints 115 and 116)

Focus: https://openlmis.atlassian.net/browse/OLMIS-5651 and https://openlmis.atlassian.net/browse/OLMIS-5496

Performance: need to review and consolidate performance epics and tickets - they are currently a big mess

Q: How do we group/maintain performance related tickets? Per service? Per type? (Fix performance / add performance test / profiling)

 A: Per service is fine, unless it grows really big - we will need to consider how to split it into smaller ones then

@Sebastian Brudziński to work on cleaning up epics/tickets related to performance

Tickets:

https://openlmis.atlassian.net/browse/OLMIS-5653(optional, needs coordination with someone with Jira admin)

Future:

Team Parrot to use 20% of their capacity to fix the following prioritized bugs:

Team Parrot to use 20% of their capacity to fix the following prioritized Tech Debt tickets:

@Sebastian Brudziński to add Tech Debt backlog here
Regression testing cycle as needed (@Joanna Bebak (Deactivated))

Team Ona Gap

Sprint Goal: 

 

Tickets:

Type your task here, using "@" to assign to a user and "//" to select a due date

Future Ideas:

 

Team JSI Gap

Sprint Goal:

 

Tickets:

Type your task here, using "@" to assign to a user and "//" to select a due date

Future:

Type your task here, using "@" to assign to a user and "//" to select a due date

Team Mind the Gap

Sprint Goal: 

Capacity: Please add # of days you are working this sprint

  • @Sam Im (Deactivated)  - 10 days

  • @Chongsun Ahn (Unlicensed)

  • @Nikodem Graczewski (Unlicensed)

  • @Łukasz Lewczyński (Deactivated) - available after 7th January

  • @Joanna Szymańska (Deactivated) - 10 days

Tickets:

Priority 1: Customizable notifications

We need to size the following stories: https://play.planningpoker.com/play/game/GmH4Be3RQd2MRWUiA7KOUZfue66QnnM0

Size these in the slack channel

 

Feature flags meeting & steps to use:  

  • Question: What is the LOE to retroactively configure Multiple Supply Partners for admin to be turned on or off? 

    • If we don't do this, then an admin will see the ability to configure multiple supply partners regardless of whether splitting requisitions feature is turned on or off. Could lead to some misconfiguration but may not be worth the additional work to prevent.  (@Nikodem Graczewski (Unlicensed), @Łukasz Lewczyński (Deactivated), @Chongsun Ahn (Unlicensed))

    • Answer: We will disable the configuring of multiple supply partners in the UI for the Multiple Suppliers feature flag

 

Priority 2 Tech Debt/Other work:

 

Notifications bugs:

https://openlmis.atlassian.net/browse/OLMIS-3477  https://openlmis.atlassian.net/browse/OLMIS-3474 (Are these duplicates? @Nikodem Graczewski (Unlicensed) @Chongsun Ahn (Unlicensed))

Future:

Review MTG section: 3.6 Scope Planning

 

OpenLMIS: the global initiative for powerful LMIS software