DevOps and methodologies 1 introduction

How DevOps Works
Development and operations teams are no longer "silos" in a DevOps architecture. These two teams are sometimes combined into a single team where the engineers work across the whole application lifecycle, from development and testing to deployment and operations, and develop a diverse set of abilities that aren't limited to a particular role.
Quality assurance and security teams may become more closely linked with development and operations, as well as throughout the application lifecycle, in some DevOps models. When everyone in a DevOps team is focused on security, this is referred to as DevSecOps.
These groups employ best practices to automate procedures that were previously manual and slow.
DevOps practices rely on effective tools to help teams rapidly and reliably deploy and innovate for their customers. These tools should automate manual tasks, help teams manage complex environments at scale, and keep engineers in control of the high-velocity pace that is DevOps.
4
The DevOps workflow consists of phases:

• 
  Planning the next iteration of the product’s development
  
• 
  Building the code
  
• 
  Testing and deploying to the production environment
  
• 
  Delivering product updates
  
• 
  Monitoring and logging software performance
  
• 
  Gathering customer feedback
  

Planning. Schedule planning and task tracking tools are needed to ensure the DevOps team knows what tasks are at hand, what is currently being done, and whether there are any risks of falling behind schedule. Tools like Confluence and Jira help DevOps teams achieve a seamless and efficient project management cycle and ensure timely product delivery.
Build and delivery. Developers need rapid deployment of development and testing environments and can’t wait long for repairs when something goes wrong. Docker containerization ensures consistency across multiple development and release cycles and provides repeatable development, build, test, and production environments. Other popular tools for this phase include Kubernetes, Terraform, Chef, Ansible, and Puppet.
Testing. Look for tools such as Jenkins, CircleCI, and GitLab CI, which help minimize the time and effort devoted to testing without compromising the code quality or user experience.