1. Expected problems
   1. Global
      1. Lack of transparency of the process
      2. Reluctance to make decisions on new features
   2. Development
      1. Failure to accept MVP
      2. Desire to deliver full implementation immediately
   3. Testing
      1. lack of understanding of Software Testing in Team
      2. lack Software Testing in the development process
      3. setting testing tasks only from the head of department
2. Reality
   1. Global
      1. Lack of transparency of the process
      2. Failure to understand the company's plans and the product's plan
      3. SCRUM activities
         1. Planning
            1. Planning work on the next 2 weeks
            2. Core Team
            3. bugs
            4. new features
            5. Application
            6. new product features
            7. Grooming as needed
            8. Decomposition of tasks by head of department
            9. Separate planning
            10. Backend
            11. Frontend
            12. Directive testing tasks
            13. I can't plan well, because there are strong dependencies
            14. StandUP
            15. by features only developers
            16. Retro
            17. Not
            18. Demo
            19. Not
      4. Low communications
   2. Developers
      1. The problem
         1. Constant rewriting of the code associated with a change in the vision
            1. The desire to write good code and not throw it away
   3. Testing
      1. completely removed from the development process
      2. misunderstanding of the subject area
      3. failure to understand the theory of Software Testing
      4. use one automation tool for all needs
      5. only juniors
3. Actions
   1. Presentation of the company's products
   2. Presentation the Road map of Product
   3. Coordination of development plans of the remote Team
   4. Process Audit
      1. product creation in general
      2. development
      3. testing
   5. Share our experience of scaling by LESS
      1. for key employees
   6. An action plan to improve the performance of the remote Team
4. Plans
   1. Clear activities in clear time
      1. planning for all Teams
         1. presence of all interested parties
            1. PO
            2. Analysts
            3. Designers
         2. Formulate
            1. fix vision
            2. acceptance criteria
            3. DOD
      2. General Stand-ups
         1. with Team representatives
      3. General Retro
      4. General Demo
         1. with stakeholders
      5. Release Synchronization
         1. Warn about each other's releases
   2. Improved communications
      1. we find bottlenecks and eliminate
      2. additional chat rooms
   3. Improve Software testing process
   4. Agile way
      1. splitting on feature Teams
      2. LESS integration
   5. Expansion Division
      1. recruitment of employees with different competencies for a full-fledged product team
   6. Software Testing
      1. constant learning (theory)
      2. study other automation tools for API (Postman) and e2e
      3. further training
         1. courses
         2. conferences
      4. our testers share the project knowledge
         1. wiki
      5. general Stand-ups
5. Best Practices for Successful Management of Distributed Teams
   1. Tip #1: Hire people who are OK with remote work.
   2. Tip #2: Communicate.
   3. Tip #3: Build internal culture.
   4. Tip #4: Use software for remote work.
   5. Tip #5: Build trust.
   6. Tip #6: Learn from others.