DEV101 · DevOps Culture and Practices
About Course
Understand what DevOps really means: a way of working that joins development and operations to deliver software in small, safe, frequent changes. You will map how a small business delivers software today and propose concrete improvements.
Who it is for
Developers, IT staff, project leads and business owners who want to understand DevOps before learning its tools.
Prerequisites
No technical prerequisites; familiarity with how software or websites are updated in a business is helpful.
What you will be able to do
- Explain the goals and principles of DevOps using the CALMS model and the three ways.
- Describe core DevOps practices, including version control, CI/CD, infrastructure as code and monitoring.
- Calculate and interpret the four DORA delivery metrics for a team.
- Map a software delivery value stream and identify waste and bottlenecks.
Lessons
- Lesson 1 · What DevOps is and why it exists
- Lesson 2 · Core DevOps practices
- Lesson 3 · Measuring and improving delivery
- Lesson 4 · Lab and assignment
Lab: Map a delivery value stream
Using a realistic scenario of a small e-commerce team, you will draw every step from a change request to the change running in production, with work time and waiting time for each step. You will then calculate lead time and flow efficiency in a spreadsheet and estimate the four DORA metrics from a short sample release log.
Free tools: draw.io (diagrams.net, free in the browser) and a free spreadsheet such as Google Sheets or LibreOffice Calc
Assessed assignment
Choose a small organization you know, or use the provided scenario of a local online store, and write a three-page DevOps improvement proposal. Include a value stream map of the current delivery process with work and wait times, the four DORA metrics estimated from available data, the three biggest bottlenecks you found and a 90-day plan with three prioritized improvements. For each improvement, state the expected effect on at least one metric and a risk to watch.
| Criterion | Weight | What excellent work looks like |
|---|---|---|
| Value stream map | 30% | All steps, handoffs, work times and wait times are shown, and lead time and flow efficiency are calculated correctly. |
| Metrics analysis | 25% | The four DORA metrics are estimated from data with clear assumptions and interpreted sensibly. |
| Improvement plan | 30% | Three improvements target the real bottlenecks, are realistic for a small team and are linked to metric changes. |
| Clarity and communication | 15% | The proposal is concise, readable by a non-technical manager and free of unexplained jargon. |
Portfolio piece
A value stream map and a metrics-based DevOps improvement proposal for a small organization.
Next step
Continue with DEV102 · Linux and the Command Line for DevOps · 4 hours · $28.00
Course Content
DEV101 · DevOps Culture and Practices (4 h)
-
Lesson 1 · What DevOps is and why it exists
-
Lesson 2 · Core DevOps practices
-
Lesson 3 · Measuring and improving delivery
-
Lesson 4 · Lab and assignment
-
DEV101 Assessment · DevOps Culture and Practices