diff --git a/docs/getting_started/building-with-shrinkwrap.rst b/docs/getting_started/building-with-shrinkwrap.rst
new file mode 100644
index 0000000..6045289
--- /dev/null
+++ b/docs/getting_started/building-with-shrinkwrap.rst
@@ -0,0 +1,194 @@
+.. SPDX-License-Identifier: BSD-3-Clause
+.. SPDX-FileCopyrightText: Copyright TF-RMM Contributors.
+
+.. _using_shrinkwrap_with_rmm:
+
+Building with Shrinkwrap
+************************
+
+This document explains how to build and run |RMM| in |FVP|, including all
+necessary firmware images, by using `Shrinkwrap`_.
+
+Introduction
+____________
+
+`Shrinkwrap`_ is a tool that helps to simplify the process of building and
+running firmware on Arm |FVP| by providing an intuitive command line interface
+frontend and (by default) a container-based backend.
+
+Shrinkwrap works by using *configs*, which are defined in YAML and can be easily
+extended using a built-in layering system.
+
+For instructions on how to setup Shrinkwrap on your local machine as well as for
+further information, you can refer to the `Quick Start Guide`_. In particular,
+for development with RME enabled Linux in Normal World, please refer to the
+`3 world configuration`_. In case that the Secure World also needs to be
+included, please refer to the `4 world configuration`_
+
+Setup local RMM with Shrinkwrap
+_______________________________
+
+This section assumes that you have your local |RMM| repository cloned
+and that it is used for your development. In order to help using
+Shrinkwrap with your development workflow, the project provides some
+configs and overlays.
+
+Also, from now on, it is assumed that your current directory (pointed by
+``${PWD}``) is the root of your |RMM| development repository.
+
+In order to use the configs defined in |RMM|, it is essential to configure
+the ``${SHRINKWRAP_CONFIG}`` environment variable to point to 
+``${PWD}/tools/shrinkwrap/configs`` directory so the tool can locate the
+config yaml files.
+
+    .. code-block:: shell
+
+      export SHRINKWRAP_CONFIG=${PWD}/tools/shrinkwrap/configs
+
+It is also recommended to override the default ``${SHRINKWRAP_BUILD}`` and
+``${SHRINKWRAP_PACKAGE}`` environment variables to a known workspace directory,
+as shown below:
+
+    .. code-block:: shell
+
+      export WORKSPACE=${HOME}/workspace
+      export SHRINKWRAP_BUILD=${WORKSPACE}
+      export SHRINKWRAP_PACKAGE=${SHRINKWRAP_BUILD}/package
+
+When building, Shrinkwrap will store the sources inside
+``${SHRINKWRAP_BUILD}/source/<CONFIG_NAME>`` and the build artifacts and
+packages will be stored inside ``${SHRINKWRAP_BUILD}/build/<CONFIG_NAME>`` and
+``${SHRINKWRAP_PACKAGE}/<CONFIG_NAME>`` directories respectively.
+
+.. note::
+
+      By default, if ${SHRINKWRAP_BUILD} and ${SHRINKWRAP_PACKAGE} are not
+      specified, Shrinkwrap will use the ``${HOME}/.shrinkwrap`` as default
+      value for ${SHRINKWRAP_BUILD}. It is only necessary to overwrite the
+      environment variables in the case it is needed to build in a different
+      location.
+
+.. _3_world_testing:
+
+3-World testing
+_______________
+
+|RMM| provides a number of overlays that can be used in conjunction with some
+of the configs provided by Shrinkwrap. One of the overlays, specifically
+``rmm.yaml``, can be used along with the ``cca-3world.yaml`` to
+build a 3 World demonstrator using the ``master`` branch of |TF-A| and the
+local |RMM| repository.
+
+As an example, the following command line would build the 3-World demonstrator.
+It assumes that Shrinkwrap is called from within the ``<RMM_ROOT>`` directory:
+
+    .. code-block:: shell
+
+       shrinkwrap build cca-3world.yaml --overlay=buildroot.yaml --overlay=rmm.yaml --btvar=GUEST_ROOTFS='${artifact:BUILDROOT}' --btvar=RMM_SRC=${PWD} --no-sync=rmm
+
+You can find further instructions on how to build and package the filesystem
+and required binaries in the `3 world configuration`_ documentation.
+
+To run the demonstrator, use the following command:
+
+    .. code-block:: shell
+
+       shrinkwrap run cca-3world.yaml -rtvar=ROOTFS=${SHRINKWRAP_PACKAGE}/cca-3world/rootfs.ext2
+
+Testing RMM with TFTF
+_____________________
+
+|RMM| provides a config that brings together a software stack to test |RMM|
+and Arm RME extension utilizing `TF-A-Tests`_. The main Test payload in
+TF-A-Tests is the |TFTF| binary. In this config, |TF-A| is in Root World, |RMM|
+is in Realm EL2 and |TFTF| is in Normal World.
+
+In order to build the config, you need to run the following command:
+
+    .. code-block:: shell
+
+      shrinkwrap build --btvar=RMM_SRC=${PWD} rmm-tftf.yaml --no-sync=rmm
+
+and you can run it through
+
+    .. code-block:: shell
+
+      shrinkwrap run rmm-tftf.yaml
+
+For further documentation about this configuration, you can check the docs through
+
+    .. code-block:: shell
+
+      shrinkwrap inspect rmm-tftf.yaml
+
+The build and run commands can also be found in the documentation of the config
+yaml file. When invoking the ``build`` command, Shrinkwrap will store the
+external repositories inside the ``${SHRINKWRAP_BUILD}/sources/<CONFIG_NAME>``
+directory.
+
+Overlays
+________
+
+Overlays can be used to extend the functionality of a config by overwriting
+both build and runtime settings. They can be used on any configuration and they
+can be combined in any way needed.
+
+In order to use an overlay, they need to be specified on the command line, through
+the ``--overlay`` keyword, as follows:
+
+    .. code-block:: shell
+
+      shrinkwrap build rmm-tftf.yaml --btvar=RMM_SRC=${PWD} --overlay=<OVERLAY_FILE_NAME> --no-sync=rmm
+
+The path to the overlay can be relative to where Shrinkwrap is called from and you
+can use as many ``--overlay`` statements as needed.
+
+Overlays are stored in the ``<RMM_ROOT_DIR>/tools/shrinkwrap/configs/`` directory,
+alongside with the configuration files.
+
+The available Overlays are sumarized in the next table
+
+.. csv-table::
+   :header: "Overlay", "Description"
+   :widths: 2 8
+
+   model-enable-lpa2.yaml,Overlay used to enable ``FEAT_LPA2`` on the |FVP| model at run time. In addition this overlay also sets the ``PA_SIZE`` on the model to 52
+   model-wait-debugger.yaml,Overlay to configure the |FVP| model to listen for Iris connections on port 7100 and make it wait until a debugger is connected before starting execution
+   rmm-debug.yaml,Overlay to build |RMM| (as well as |TF-A|) in debug mode
+   clean.yaml,Overlay used to avoid an exception with ``Shrinkwrap clean`` in which a path with a valid format needs to be specified for |RMM|
+
+Example of use
+~~~~~~~~~~~~~~
+
+Below is an example on how to use one of the available overlays with the
+existing configuration. The example specifies ``--runtime=null`` to use the
+native toolchain (without the Docker container) to build the artifacts and
+``--no-sync-all`` to prevent Shrinkwrap from updating/cleaning any of the
+repositories:
+
+    .. code-block:: shell
+
+       shrinkwrap --runtime=null build rmm-tftf.yaml --overlay=model-enable-lpa2.yaml --btvar=RMM_SRC=${PWD} --no-sync-all
+
+Then you run your tests with
+
+    .. code-block:: shell
+
+       shrinkwrap --runtime=null run rmm-tftf.yaml
+
+.. note::
+
+      Note that ``runtime=null`` is specified for the run, as it must match
+      the same setting as used on the build stage. Also, with this setting,
+      the appropriate FVP (FVP_Base_RevC-2xAEMvA) needs to be present in the
+      system ${PATH}.
+
+-----
+
+.. _Shrinkwrap: https://shrinkwrap.docs.arm.com
+.. _Quick Start Guide: https://shrinkwrap.docs.arm.com/en/latest/userguide/quickstart.html#quick-start-guide
+.. _3 world configuration: https://shrinkwrap.docs.arm.com/en/latest/userguide/configstore/cca-3world.html
+.. _4 world configuration: https://shrinkwrap.docs.arm.com/en/latest/userguide/configstore/cca-4world.html
+.. _TF-A-Tests: https://trustedfirmware-a-tests.readthedocs.io/en/latest/index.html
+.. _btvar: https://shrinkwrap.docs.arm.com/en/latest/userguide/configmodel.html#defined-macros
+.. _rtvar: https://shrinkwrap.docs.arm.com/en/latest/userguide/configmodel.html#defined-macros
diff --git a/docs/getting_started/getting-started.rst b/docs/getting_started/getting-started.rst
index 367b1d6..4b8bfbc 100644
--- a/docs/getting_started/getting-started.rst
+++ b/docs/getting_started/getting-started.rst
@@ -286,10 +286,16 @@
 or an appropriate Test utility running in Non-Secure world which can interact
 with |RMM| via Realm Management Interface (RMI).
 
-The `TF-A`_ project includes build and run instructions for an RME enabled
-system on the FVP platform as part of `TF-A RME documentation`_.
-The ``rmm.img`` binary is provided to the TF-A bootloader to be packaged
-in FIP using ``RMM`` build option in `TF-A`_.
+Building all of the involved stack is complicated. We recommend using the
+`Shrinkwrap`_ tooling to bootstrap the stack. For more details on `Shrinkwrap`_
+and utilizing configs and overlays included in |RMM| please refer to
+:ref:`using_shrinkwrap_with_rmm` and, specially for building a demonstrator
+for 3-world, you can refer to :ref:`3_world_testing`.
+
+The |TF-A| documentation also provides some documentation to build |TF-A| and
+other pieces of firmware for RME in `TF-A RME documentation`_. The |RMM| build
+option in |TF-A| should point to the ``rmm.img`` binary generated by building
+|RMM|.
 
 If |RMM| is built for the `fake_host` architecture
 (see :ref:`RMM Fake Host Build`), then the generated `rmm.elf` binary can
@@ -305,3 +311,4 @@
 .. _TF-A RME documentation: https://trustedfirmware-a.readthedocs.io/en/latest/components/realm-management-extension.html
 .. _TF-RMM Gerrit page: https://review.trustedfirmware.org/admin/repos/TF-RMM/tf-rmm
 .. _Git hooks documentation:  https://git-scm.com/docs/githooks
+.. _Shrinkwrap: https://shrinkwrap.docs.arm.com
diff --git a/docs/getting_started/index.rst b/docs/getting_started/index.rst
index b9d1cb3..4e808ff 100644
--- a/docs/getting_started/index.rst
+++ b/docs/getting_started/index.rst
@@ -10,3 +10,4 @@
 
     getting-started
     build-options
+    building-with-shrinkwrap
diff --git a/docs/global_substitutions.txt b/docs/global_substitutions.txt
index aeac5a3..8e3e344 100644
--- a/docs/global_substitutions.txt
+++ b/docs/global_substitutions.txt
@@ -5,3 +5,5 @@
 .. |RD| replace:: :term:`RD`
 .. |PAR| replace:: :term:`PAR`
 .. |PAS| replace:: :term:`PAS`
+.. |TFTF| replace:: :term:`TFTF`
+.. |FVP| replace:: :term:`FVP`
diff --git a/docs/glossary.rst b/docs/glossary.rst
index ef679b3..38a985d 100644
--- a/docs/glossary.rst
+++ b/docs/glossary.rst
@@ -51,4 +51,10 @@
    VHE
       Virtualization Host Extensions
 
+   TFTF
+      Trusted Firmware Test Framework
+
+   FVP
+      Fixed Virtual Platforms
+
 .. _`Arm Glossary`: https://developer.arm.com/support/arm-glossary