What are the maturity levels of a company?
Companies, like living beings, follow a process of evolution. They are born, grow and can expand, stagnate or disappear. This life cycle profoundly impacts the culture, the techniques and tools they use, and the role of the teams, including the role of DevOps. Understanding how a company evolves is crucial for a DevOps expert, as the strategies and tools available depend on the culture and maturity of the company.
What does a DevOps person do in a startup?
When a company starts integrating DevOps, they are likely to look for a DevOps specialist after discovering information online about its benefits. However, these companies may lack tools or a team dedicated to continuous improvement. The main focus will be:
- Initial diagnosis: Assess the current state of the company.
- Improvement plan: Design a plan to improve the workflow.
- Change implementation: Gradually introduce improvements and tools.
The biggest challenge will be to convince the teams of the need and usefulness of these changes. Herein lies the real challenge: fostering acceptance and cooperation to adopt new practices.
What role does a DevOps player play in a company migrating to the cloud?
Companies migrating to the cloud already recognize the value of DevOps and are looking to improve their competency. In this context, the DevOps does not need to convince about the change, his work is focused on:
- Assisting in the migration of applications and data to the cloud.
- Creating cloud infrastructures that mirror the existing private network.
The mission is focused on facilitating this transition so that the processes are as smooth as possible.
How to ensure software quality?
In companies where software quality assurance is lacking, the goal is to establish systems that ensure acceptable standards before sending code to production. This implies:
- Implementing tools that verify the code.
- Stopping the flow of code until it meets the quality standards predefined by the company (e.g. 80% or 90%).
This stage is crucial to prevent problems in production and ensure robust and reliable software.
What should a DevOps person know in a new project?
When a company starts a project and has the resources to build a DevOps team from scratch, the opportunity is unique. In this scenario, the primary task includes:
- Planning from scratch: Ensuring that best practices and tools are integrated from the start.
- No need to convince: The role here is more proactive, focusing on creation and implementation.
It is crucial to talk to all teams and oversee that established practices remain effective, ensuring software quality from the start.
In short, each company has unique characteristics that directly affect the DevOps role, influencing how strategies and processes should be approached. With the right knowledge, DevOps can drive efficiency and quality at various stages of a company's lifecycle.
Want to see more contributions, questions and answers from the community?