CSE4033 - IT Project Management | Module 4: Agile Project Management
By the end of this section, you will be able to:
DevOps is a set of practices that combines software development (Dev) and IT operations (Ops) to shorten the systems development life cycle while delivering features, fixes, and updates frequently in close alignment with business objectives.
DevOps addresses the traditional conflict between development teams (who want to deploy new features quickly) and operations teams (who want to maintain system stability):
Developers merge code changes frequently (at least daily) into a shared repository where automated builds and tests verify the changes.
Code changes are automatically built, tested, and prepared for release to production, enabling rapid and reliable software delivery.
Managing and provisioning infrastructure through code and automation rather than manual processes.
Tracking application and system performance to understand impact on user experience and inform improvements.
Breaking down silos between development, operations, and other stakeholders through shared tools and processes.
Building security into the development process from the beginning rather than adding it at the end (DevSecOps).
Click through the stages of a typical CI/CD pipeline to understand the DevOps workflow:
Git, GitHub, GitLab, Bitbucket
Jenkins, CircleCI, Travis CI, GitHub Actions
Ansible, Chef, Puppet, Terraform
Docker, Kubernetes, OpenShift
Prometheus, Grafana, ELK Stack, New Relic
AWS, Azure, Google Cloud, DigitalOcean
Selenium, JUnit, TestNG, Postman
Slack, Microsoft Teams, Jira, Confluence
| Aspect | Traditional IT | DevOps |
|---|---|---|
| Release Frequency | Months/quarters | Days/hours |
| Team Structure | Silos (Dev vs Ops) | Cross-functional |
| Process | Manual, linear | Automated, iterative |
| Failure Response | Blame culture | Blameless postmortems |
| Change Management | Change advisory boards | Automated testing/gating |
1. What does CI stand for in DevOps?
2. Which of these is NOT a benefit of DevOps?
3. What is the purpose of Infrastructure as Code?
4. Which tool is commonly used for container orchestration?