<p><strong>Document the functional process</strong></p>

<p>When I create a new project and want to deploy it I always start to right down the manual steps in a README, but one could also create a txt file or sheet like you did.</p>

<p><strong>Feel the pain</strong></p>

<p>At a certain moment when I have deployed the project manually the pain of certain steps will become clear. For example, I add per step how much time it takes.</p>

<p><strong>Automate the high ROI steps</strong></p>

<p>If for example a certain step takes half an hour an one deploys twice a week, one could investigate how long it will take if one automates this step (investment) and what time it will save (return). One could decide to create issue tickets and automate steps every sprint.</p>

<p><strong>Example deployment plan</strong></p>

<p>For one of my current projects I have to deploy multiple microservices. I will not provide all details, but initially the plan was two pages long. Now I only use a Continuous Integration/Deployment (CI/CD) plan and a lot of abstractions. If the deployment will fail some day I could still read the initial plan so that the functional flow is still clear.</p>

<p><strong>Configuration as Code</strong></p>

<p>Another benefit of automating the manual step is that one could save the code in a Git repository as a pipeline script. When another person reads the scripts then it becomes clear how the project is deployed and one could also trace who made some change, what modifications were done and when.</p>

CC BY-SA 4.0
2018-05-22T09:29:56.413Z
Thanks for sharing your experiences. I have similar stuff but in Excel documented. My trouble here is that it has lot of main and sub steps and it is becoming difficult to track and follow. I was wondering if there are any software which can handle this?
KK99
CC BY-SA 4.0
2018-05-18T17:43:27.107Z
2018-05-18T17:43:27.107Z
030
<p>I deploy applications on servers. While the process itself is automated but there are lot of manual steps involved surrounding the automation due to various reasons.</p>

<p>I manage the manual procedure in Excel. But this is getting cumbersome.  </p>

<p>I am wondering if there are any tool where the procedure can be described and easy to manage.</p>

<p>Thanks </p>

CC BY-SA 4.0
2018-05-18T17:21:16.353Z
Could you add some content of the Excel?
030
CC BY-SA 4.0
2018-05-25T09:03:31.930Z
Steps Involved, IF this step Fails what to do, If this step is not abvl what to do, status, who is doing it, etc..
KK99
<deployment>
Any tools available for rollout planning / checklist
KK99
# Any tools available for rollout planning / checklist

(Asked by: username_0 on 2018-05-18)

I deploy applications on servers. While the process itself is automated but there are lot of manual steps involved surrounding the automation due to various reasons.

I manage the manual procedure in Excel. But this is getting cumbersome.

I am wondering if there are any tool where the procedure can be described and easy to manage.

Thanks

**Tags:** deployment

> **Comments:**
> **username_1**: Could you add some content of the Excel?  
> **username_0**: Steps Involved, IF this step Fails what to do, If this step is not abvl what to do, status, who is doing it, etc..  

---

## 1 answers

### Answer by username_1 on 2018-05-18. Score: 2

**Document the functional process**

When I create a new project and want to deploy it I always start to right down the manual steps in a README, but one could also create a txt file or sheet like you did.

**Feel the pain**

At a certain moment when I have deployed the project manually the pain of certain steps will become clear. For example, I add per step how much time it takes.

**Automate the high ROI steps**

If for example a certain step takes half an hour an one deploys twice a week, one could investigate how long it will take if one automates this step (investment) and what time it will save (return). One could decide to create issue tickets and automate steps every sprint.

**Example deployment plan**

For one of my current projects I have to deploy multiple microservices. I will not provide all details, but initially the plan was two pages long. Now I only use a Continuous Integration/Deployment (CI/CD) plan and a lot of abstractions. If the deployment will fail some day I could still read the initial plan so that the functional flow is still clear.

**Configuration as Code**

Another benefit of automating the manual step is that one could save the code in a Git repository as a pipeline script. When another person reads the scripts then it becomes clear how the project is deployed and one could also trace who made some change, what modifications were done and when.

> **Comments:**
> **username_0**: Thanks for sharing your experiences. I have similar stuff but in Excel documented. My trouble here is that it has lot of main and sub steps and it is becoming difficult to track and follow. I was wondering if there are any software which can handle this?  

---

