Page Comparison

Why: Prokopovych will disband once Orchid is released. A new team(s) must be assigned to own/release inventory modules. 

Plan: Spitfire and Folijet co-own modules and backlog 

Transition date: Orchid GA date 

Responsible for Orchid hotfix/service patch: Yes 

Poppy expectations:

• No new functionality.
• Developers' focus is on acquiring knowledge especially around the release process with so many contributors.
• QA's focus is on acquiring knowledge and defining a plan for managing these additional modules/workflows. 
• PO's focus is on reviewing backlog and evaluating work for Q and R releases  
• Only address P1 issues and if possible P2. 
• May need to address

  Jira Legacy
  server System JiraJIRA serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key MODINVSTOR-960

  but details are unclear.  

Transitioning back-end modules

Transitioning front-end modules

https://wikifolio-org.folioatlassian.orgnet/wiki/display/REL/Team+vs+module+responsibility+matrix

Useful Jira filters

• Prokopovych unclosed epics:

  Jira Legacy
  server System JiraJIRA jqlQuery filter=15219 count true serverId 01505d01-b853-3c2e-90f1-ee9b165564fc

  (2)
• Prokopovych unclosed features:

  Jira Legacy
  server System JiraJIRA jqlQuery filter=15218 count true serverId 01505d01-b853-3c2e-90f1-ee9b165564fc

  (94)
• Prokopovych unclosed issues (no epics, umbrellas, new features) - note that this includes ALL modules, not just Inventory-related ones: https://issuesfolio-org.folioatlassian.orgnet/issues/?filter=15187 (449)
  • P1/P2 issues (21 issues)
  • P3/P4 issues (245 issues)
  • TBD/None issues (177 issues)
• Prokopovych unclosed Inventory issues (no epics, umbrellas, new features): https://issuesfolio-org.folioatlassian.orgnet/issues/?filter=15188 (396)
• Prokopovych unclosed Inventory bugs (no epics, umbrellas, new features): https://issuesfolio-org.folioatlassian.orgnet/issues/?filter=15189 (36)

Backlog management 

• POs will review above backlog and will only move items as ready to do so. 
• There maybe times that Spitfire PO will assign work to Folijet and vice versa. 

Proposed way to break up work 

Spitfire 

• Inventory search and browse 
• Select an instance record via plug-in

Folijet

• CRUD Instance
• Fast add instance/holdings/item plug-in
• CRUD Holdings
• CRUD Items?
• Settings 

Potential UX work over the next couple of releases

• Replace Inventory search and sort with react? 
• Replace search facets 
• Improve interacting with long lists 
• Hide fields support
• Template support 
• Add a link to search documentation 

Questions

1. What additional help is needed to make this transition go smoothly? 
   1. Folijet: 1 Backend developer (what level? - Kate will make recommendation) |  Frontend developer (what level? - Ivan will make recommendation): TBD based on RTL/Jest conversation | TBD :  Manual QA? | TBD : AQA 
   2. Spitfire: TBD :  Manual QA? | TBD : AQA 
2. Confirm Karate tests coverage – speak with Marc 
3. What about RTL/JEST remaining work? 
   1. NES still working on it? What do we need to do?

Action items 

1. QAs: QA to do (meeting on 3 May)
   1. Transition AQA test cases (Natalia and Ivan can schedule a meeting to discuss plan)
   2. Transition Jenkins test failure messages (still appearing in Prok Slack channel)
   3. QAs: Transition manual QA test cases in TestRail (Natalia and Ivan can schedule a meeting to discuss plan) 
   4. Review remaining Prok Jest test
   5. Review remaining E2E Smoke, Critical Path tests to automate
   6. Reassign Karate tests to Spitfire and Folijet 
2. KG: Communicate change to community 
3. KG: Address the RTL/Jest situation with LeeB.
4. KG/AMB: Review P1/P2 Prokopovych issues 
5. AMB - : will come up with a plan for backlog organization 
6. Reassign Karate tests to Spitfire and Folijet Each team creates a story to reassign mod-inventory and mod-inventory-storage  KG/AMB/CSR: reassign features and epics
7. Each team review Poppy features capacity based on #5. Possibly create another feature for this work.