Chapter 1. Getting Started with rolloutMan

The following sections describe details that will kick start you for using rolloutMan.
Use cases
rolloutMan helps you to manage software releases. Full stop. 
This software takes away the management pain - viz. planning / scheduling, collaboration, implementation planning, execution tracking and reporting.
For e.g. some typical use cases where you could use rolloutMan are:
  • You want to manage a software release - this could be:
    • rollout of a completely new Application
    • rollout of a "Upgrade" of an existing Application
    • rollout of a "Integration" or a ESB scenario
    • Platform Upgrade scenario - Databases, OS's or any such hardware
    • rolling out of a Process / Training etc.
    • rollout of a entire suite of applications etc.
    • rollout of a regulation with checklists.
As you go through the rest of the guide, it will get more and more clearer on how to manage the different tasks and risks associated with each of these different kinds of rollouts.
What rolloutMan is not?
rolloutMan is not a Continuous Integration (CI) or a Deployment tool. This is a "management software" built for management and planning of releases.
However, rM as a platform can brilliantly integrate with other CI / CD tools - e.g. Jenkins or Ansible, Puppet or Chef IO, and provide real time reporting of the executions / post execution steps to management/ planning team.
User roles
rolloutMan is a very user aware product, and manages users of different roles to participate in the release management. Read through the User roles concept pages to understand these better.
Next Steps
Read through the Initial Configuration followed by Fundamental Concepts sections as a guide on specific configurations, to be followed before starting using rolloutMan.
To maximise benefit from this documentation, we recommend you to go through the following documentation at the very least before going ahead with the implementation. 
If you are further interested, feel free to explore the Advanced Features of the product, followed by APIs documentation.