2. Difficult to find the docs/ right doc version ->
Systematically apply existing solutions:
- For epic related to affilliation: check if spec of corresponding sprint had already downloaded in project folder: dev\doc\Specs\US\Sprint xxxx. Note: if not download and copy spec
- For epic related to assures: spec is changed continuously during development
    + BA should always inform when spec changed related to scope of current sprint and highlighed with color.
    + Set alert in sharepoint for doc changed

3. Test env not stable
- Not enough resources ( memory, CPU...) for 4 environments: turn off environment
+ Pod? : 14 GB Ram,
- Memory leak issues of GUIS-web-app
- Old data, dirty data
-> e.g Simulator Rafam (sedex) simulates duplicated message ID -> RabbitMQ retries processing messages -> increase RabbitMQ's memory -> RabbitMQ down : Need dev team check this issue
- Network unstable -> Down load missing versions to VN -> mistmach versions when build & deploy: escalate to higher management, VVH

4. Missing test scenarios for each epic.
- Done tests
- Test scenarios which links different user stories in epic

5. Lacking of test data
- Json, xml files

6. Too many bugs

7. French term
- Glossary in confluence pages

https://confluence.svc.elca.ch/display/CFLIPENSIONVN/Glossary 

 

8. Difficult to compare expected result