IBM DevOps and Software Engineering study materials
IBM DevOps and Software Engineering study resources

IBM DevOps and Software Engineering study plan

IBM DevOps and Software Engineering · Give each week a clear focus.

8 weeks · About 6 hours per week

Week 1

DevOps and Software Engineering Fundamentals

  • Define DevOps in your own words and contrast it with traditional waterfall-style delivery, citing at least three concrete differences

  • Diagram the CI/CD feedback loop and label where version control, automated build, automated test, and deployment gates sit

  • Explain the CALMS framework (Culture, Automation, Lean, Measurement, Sharing) and give one real example of each element from a project you know

  • Distinguish continuous integration, continuous delivery, and continuous deployment and state which one a given team scenario actually practices

Your checkpoint

A one-page written summary plus a hand-drawn or digital diagram of the DevOps lifecycle, with a 10-term glossary of core DevOps vocabulary

Week 2

DevOps and Software Engineering Fundamentals

  • Compare Git branching strategies (feature branch, trunk-based, GitFlow) and justify a choice for a small team

  • Practice the core Git workflow: clone, branch, commit, push, open a pull request, review, merge, and resolve a merge conflict

  • Identify what belongs in a repository versus what belongs in configuration or secrets management

  • Explain the role of infrastructure as code and name two tools that implement it

Your checkpoint

A public or local Git repository with at least three branches, a merged pull request, and a documented conflict resolution in the README

Week 3

Agile and Scrum Practices & DevOps and Software Engineering Fundamentals

  • Describe the Scrum framework: roles, artifacts, and events, and map each to its purpose

  • Write user stories with acceptance criteria in the 'As a ... I want ... so that ...' form

  • Estimate a small backlog using story points and relative sizing, then justify your estimates

  • Explain how Agile principles from the manifesto connect to DevOps practices like small batch size and fast feedback

Your checkpoint

A sample product backlog of 10 user stories with acceptance criteria and story-point estimates, plus a one-page explanation of how one sprint would run

Week 4

Agile and Scrum Practices

  • Simulate a sprint planning session and produce a sprint goal, selected backlog items, and a task breakdown

  • Define done using a team Definition of Done and apply it to each selected story

  • Interpret a burndown chart and identify at least two signals of scope creep or blocked work

  • Run a retrospective format (Start/Stop/Continue) and convert findings into two actionable improvement items

Your checkpoint

A complete sprint package: sprint goal, sprint backlog with tasks, a sketched burndown chart, and retrospective notes with two improvement actions

Week 5

Cloud Native and CI/CD Tooling

  • Explain what cloud-native means and contrast it with lift-and-shift migration

  • Describe the twelve-factor app principles and apply at least four of them to a sample service

  • Build a CI pipeline that installs dependencies, runs tests, and fails on a broken test

  • Explain how a CI/CD tool such as Jenkins, Tekton, or GitHub Actions triggers and reports pipeline stages

Your checkpoint

A working CI pipeline configuration file in a repository that runs tests automatically on push and shows a passing and a failing run

Week 6

Cloud Native and CI/CD Tooling

  • Distinguish continuous delivery from continuous deployment in pipeline design and describe the approval gate for each

  • Add automated testing layers (unit, integration, smoke) to a pipeline and explain what each layer catches

  • Describe artifact repositories and versioning of build outputs

  • Explain blue-green and canary deployment strategies and state when each reduces risk

Your checkpoint

An extended pipeline with at least two test stages and a documented release strategy for blue-green or canary deployment

Week 7

Containers, Kubernetes, and Application Modernization

  • Explain how containers differ from virtual machines in terms of isolation, startup, and resource use

  • Write a Dockerfile for a simple application and build and run the image locally

  • Describe Kubernetes core objects (Pod, Deployment, Service, ConfigMap) and what each solves

  • Apply a Deployment and Service manifest to a local cluster and verify the app is reachable

Your checkpoint

A Dockerfile plus Kubernetes Deployment and Service manifests that successfully run a sample app on a local cluster, with screenshots or command output as evidence

Week 8

Containers, Kubernetes, and Application Modernization & DevOps and Software Engineering Fundamentals & Agile and Scrum Practices & Cloud Native and CI/CD Tooling

  • Explain application modernization approaches: rehost, replatform, refactor, and retire, with a tradeoff for each

  • Describe how containers and Kubernetes fit into a CI/CD pipeline from build to deploy

  • Review weak areas across all four domains and close the top three gaps

  • Complete a timed practice set covering all domains and analyze every missed question

Your checkpoint

A full end-to-end summary: containerized app, pipeline config, deployment manifests, and a written gap analysis of your three weakest topics with a remediation plan

Milestones

Week 2: You can explain the DevOps lifecycle from memory and demonstrate a full Git branch-merge-conflict workflow without notes

Week 4: You can run a simulated sprint from planning to retrospective and produce a defensible backlog with estimates and acceptance criteria

Week 6: Your repository has a CI pipeline that automatically tests on push and documents a release strategy; you can explain each stage's purpose

Week 8: A containerized application runs on a local Kubernetes cluster, is wired into a pipeline, and your gap analysis identifies concrete next study actions