diff --git a/ci/device-testing.rst b/ci/device-testing.rst
index 9cef4b1b51c9135bf4f20cfb892acd0c8c63d0b7..598b44295b705f4727f71ef20d83c80f2a1d4e74 100644
--- a/ci/device-testing.rst
+++ b/ci/device-testing.rst
@@ -15,7 +15,7 @@ and Validation Architecture (LAVA). This architecture creates an environment
 where you can operate the necessary physical infrastructure responsible for
 testing development on real devices, like operating system boot-loader and
 kernel development, while sharing access to a project-specific software
-infrastructure used in the public cloud. 
+infrastructure used in the public cloud.
 
 How does the CI system work?
 ----------------------------
@@ -51,7 +51,7 @@ to the public cloud:
 * If the network connection is poor, building and downloading the images
   locally is suggested.
 * If the network connection is robust, use the central build system directly to
-  build the images, where scalability is easy. 
+  build the images, where scalability is easy.
 
 Typically a micro-site that has limited throughput will be bound by the limited
 number of test devices and will be able to perform the builds locally much
@@ -72,6 +72,71 @@ What does LAVA do?
 5. The report is submitted back to Gitlab, and the developers can see the
    report in their merge request.
 
+Setting up Remote LAVA Worker
+-----------------------------
+
+A LAVA worker performs test execution in LAVA. LAVA workers can connect to the LAVA server on a local network or using the internet. We called it ``remote worker`` as it can be located anywhere that has internet access.
+
+A remote LAVA worker can be deployed manually by following this guide `Running the LAVA dispatcher in a Docker container <https://lava.readthedocs.io/en/latest/admin/advanced-tutorials/docker-worker/>`_. The process has been automated using ansible as well.
+
+Following are the steps for automatic deployment.
+
+1. Install Debian buster on your worker.
+2. Clone LAVA Ansible Playbooks repository.
+
+   .. code-block:: console
+
+      git clone https://git.ostc-eu.org/OSTC/infrastructure/lava/lava-playbooks.git
+
+3. Define a group of worker/workers in ``hosts`` and related group variables under ``group_vars``.
+
+   ``hosts`` example:
+
+   .. code-block:: console
+
+      [worker_dev]
+      # local VMs for dev
+      192.168.56.103 worker_name=<hostname.lab_name> server_token=<worker_token>
+      192.168.56.104 worker_name=<hostname.lab_name> server_token=<worker_token>
+
+   Worker token is generated on LAVA server. Ask LAVA administrator to create your worker and share authorization token.
+
+   ``group_vars/worker_dev.yaml`` example:
+
+   .. code-block:: console
+
+      lava_config_repo: https://git.ostc-eu.org/OSTC/infrastructure/lava/lava-playbooks.git
+      lava_config_repo_branch: master
+      # sudo user without password
+      ansible_user: <username>
+      server_url: http://192.168.56.102
+
+4. Run Ansible playbook for worker deployment.
+
+   Deploy to a worker group:
+
+   .. code-block:: console
+
+      ansible-playbook -l worker_dev playbooks/deploy-docker-worker.yaml -b
+
+   Deploy to a specific worker:
+
+   .. code-block:: console
+
+      ansible-playbook -l 192.168.56.103  playbooks/deploy-docker-worker.yaml -b
+
+5. Check service status with command ``systemctl status lava-docker-worker.service``.
+6. You can also optionally `provide arbitrary Dockerfile to LAVA docker worker <https://forum.ostc-eu.org/t/providing-arbitrary-dockerfile-to-lava-docker-worker/214>`_.
+
+Adding a Device to LAVA
+-----------------------
+
+Test devices are connected to their local LAVA worker and manged by LAVA server. The following wiki pages have been created for adding devices to LAVA.
+
+* `How to deploy wic image on Raspberry Pi in LAVA <https://forum.ostc-eu.org/t/how-to-deploy-wic-image-on-raspberry-pi-in-lava/228>`_
+* `Adding Arduino Nano 33 BLE Board to LAVA Lab <https://forum.ostc-eu.org/t/adding-arduino-nano-33-ble-board-to-lava-lab/215>`_
+* `Adding Nitrogen Board to LAVA Lab <https://forum.ostc-eu.org/t/adding-nitrogen-board-to-lava-lab/192>`_
+* `Adding Avenger96 Board to LAVA Lab <https://forum.ostc-eu.org/t/adding-avenger96-board-to-lava-lab/46>`_
 
 References
 ----------