/
Backlog Grooming Sprint 107

Backlog Grooming Sprint 107

Nov 13, 2018

Dates: Aug 30, 2018 - Sep 12, 2018 

Team Parrot Sprint

Sprint Goal: 



Tickets:

This is priority for 3.4.1:  https://openlmis.atlassian.net/browse/OLMIS-5314

Continue working on tickets in: https://openlmis.atlassian.net/browse/OLMIS-4658 and https://openlmis.atlassian.net/browse/OLMIS-4834



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 Ona Gap

Sprint Goal: 



Tickets:

Brainstorming notes from Backlog Grooming Meeting:

@Jason Rogena (Unlicensed) please create Epic and tickets → (Priority: High | Jason) Deployment of NiFi to a production environment

TLS - Figure out access to the Nifi Registry behind HTTPS (Currently, HTTP is required without Sign-in and may be )
Backup all persistent NiFi Registry data
Antonate
Recap with Janette's Stock on Hand work
Clay can identify an appropriate report with the target to have this spec'd by Thursday next week.
Team:
Work to structure
@Clay Crosby (Unlicensed) or @Peter Lubell-Doughtie (Unlicensed), create a research epic for sprint 107 → Role Based Access Controls in Superset

When an administrator sets up a user in Superset, what roles do we need to create for a particular user?
Superset filters data based on a dataset, we are talking about row based access controls
Restrict which dashboards can be seen by a particular group
Ticket based on  ^ Clay will write up a proposal on how it should work and a technical person (maybe Peter) will identify the software development required.
Evaluate OpenLMIS roles and compare to eLMIS reporting roles
Role Based Access Controls in Nifi Registry
Role Based Access Controls in Nifi for system admins
Clay & Craig:
Post Meeting Recap to create tickets
@Clay Crosby (Unlicensed) and @Craig Appl (Unlicensed) revisit this on Wednesday
@Clay Crosby (Unlicensed) create a ticket here: Develop SRS for Superset requirements
User profiles
Indicators we need to see
At what summary level
Do a research task to test the user profile process.
@Craig Appl (Unlicensed), @Antonate Maritim (Unlicensed) and @Wambere (Unlicensed), meet this week to identify Janette's priorities for this sprint

To Do:

  • OLMIS-5757 - Pull out horizontal scaling from this epic and create a research task in the backlog

  • Craig review OLMIS-5288 and figure out if it should be in the current sprint 106, the EPIC OLMIS-5266 should be complete this sprint.

  • Craig: Look at how long it will take to deliver SSO vs RBAC. If we prioritize one vs the other, will that cause the other to fail. What are the risks, can they be delivered in parallel?

    • Develop a task: Evaluate if the 

  • Craig: Talk to Dickson about resourcing of Janette and the new hire.

Future:



Team JSI Gap

Sprint Goal: Continue with report services with Ona team and FHIR interface with Mind the Gap team

Tickets:

@Ashraf please make sure to update the grooming pages with what your team plans to work on (from bugs, techdebt or tickets supporting MTG or Team Ona.

Future:

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

Team Mind the Gap

Sprint Goal: Continue research options for mCSD, 

Tickets are listed in priority from top (highest priority) to bottom (lowest priority) on this page, and in the active sprint Jira board.

mCSD research (Priority 1):

Set up meeting to review with team & Josh after Elias' spike to discuss LOE, and what we will actually do based on LOE (@Sam Im (Deactivated) to schedule for Friday)

Other Gap Feature requirements gathering (Priority 2):

@Nikodem Graczewski (Unlicensed) to update tickets based on Thursday meeting, so that the team can review them in next grooming



Tech Debt tickets:

@Nikodem Graczewski (Unlicensed) to check with @Sebastian Brudziński on which epics Team Parrot is working on, and add tech debt tickets this sprint
Question: who is working on orderables edit? This epic still needs to be cleaned up and prioritized. https://openlmis.atlassian.net/browse/OLMIS-3804 (These tickets are not a priority to complete for these next few sprints. Gap features are more important.)

Bugs:

https://openlmis.atlassian.net/browse/OLMIS-5235 @Nikodem Graczewski (Unlicensed) or @Chongsun Ahn (Unlicensed) should we take this on since Nikodem already started?
https://openlmis.atlassian.net/browse/OLMIS-4555 (assigned to @Hussein Hassan)
https://openlmis.atlassian.net/browse/OLMIS-5105 - without the fix, we can have the incorrect docker image
https://openlmis.atlassian.net/browse/OLMIS-5233 - only if we know the root cause and it is easy to fix
https://openlmis.atlassian.net/browse/OLMIS-3541 - easy to fix, we could assign it to @Hussein Hassan if he needs more work in the sprint otherwise we could omit it.



Future:

 
 





OpenLMIS: the global initiative for powerful LMIS software