DevOps for Product Managers :

2 min readAug 12, 2022

Did you ever hear the developers say the “Build Failed” or I am seeing “Merge Issues” or “Code Commits” and so on

These are the real issues once the dev has completed his/her code.

Next comes the task to push the code to production (Not that easy).

When too many developers are trying to work on the same workspace, one needs a mechanism to bring order and more importantly with increased efficiency.

Simple put:

DevOps = Development + Operations [IT]

In a DevOps model all the teams inclusive of Devs, Ops, Quality, and Security become more tightly integrated with development and operations throughout the application lifecycle

[When security comes in its called DevSecOps]

DevOps Lifecycle :

1. Plan: DevOps Team teams up to ideate and defines the problem they will be solving

2. Build: Dev team goes ahead with actual coding.

3. CI/CD: Developers continuously keep merging their code into a common shared repository and the development works never stops

4. Monitor and Alert: Keep a tab on issues if any and address them quickly

5. Operate: Manage all the end-to-end delivery of IT services

6. Feedback: Always make sure to collect feedback and improve for the next cycle

DevOps Practices :

1. CI/CD: Continuous Integration/Development to keep the momentum of the team high

2. Version Control: A mechanism deployed to manage the code in different versions, keep track of revisions, history backups and so forth

3. Agile mindset: DevOps seeks agile methodologies in order to complete the lifecycle from build to feedback and incorporate them in shorter cycles for higher efficiency

4. Infrastructure as code: Defines system resources in a manner to let the team use it as they code

5. Configuration Management: CM refers to managing the states of resources in a system including servers, Virtual Machines (VMs) and databases.

6. Continuous Monitoring: CM means full real-time visibility into the performance and health of the application stack

DevOps Tools:

1. Plan: Jira Software, Confluence, Slack

2. Build: Kubernetes, Docker, Inc, Puppet, Terraform Labs

3. CI/CD: Jenkins, Amazon Web Services (AWS), BitBucket

4. Monitor and Alert: Grafana Labs, Splunk, New Relic, Inc.

5. Operate: Chef, Ansible Labs

6. Feedback: Slack, Teams, GetFeedback, Pendo.io

Finally after putting in place a DevOps model what are the benefits :

1. Collaboration and Trust: Create an environment to let all team members trust the process

2. Accelerate to Market: As the system makes sure there are no breakpoints, GTM cycle time reduces

3. Maintenance: Less effort on work that is more operational than actual development

DevOps model of operations is the new norm in the way we build and ship applications.

References :

#DevOps #Technology #BuildDeploy #ProductManagement #ProductManager #KPKR

DevOps for Product Managers :

Written by K Praveen Kumar Reddy

Responses (1)