The Agile and DevOps primer trips up many new joiners not because it is difficult, but because it is concept-heavy and vocabulary-driven. There is little to calculate and nothing to compile; instead you must know precise definitions and be able to match a scenario to the correct Agile or DevOps idea. That is good news, because concept-based primers are very learnable in a short time if you study the right terms.
This guide walks through everything the Agile and DevOps primer commonly covers: the Scrum framework, its roles and ceremonies, core DevOps practices like continuous integration and delivery, version control basics, and the mindset that ties them together. We also include sample question styles so you know exactly what to expect.
Why Agile and DevOps appear together in one primer
Agile is a way of managing work in small, iterative cycles with frequent feedback, while DevOps is a culture and set of practices that shorten the path from writing code to running it in production. They appear together because modern Accenture delivery uses both: teams plan in Agile sprints and ship using DevOps automation.
The primer expects you to understand both as complementary, not competing, ideas. Agile answers how the team organises and prioritises work; DevOps answers how that work gets built, tested and deployed reliably. Keeping that distinction clear in your head makes scenario questions much easier to answer.
The Scrum framework: roles you must know
Scrum is the most widely used Agile framework and the primer leans on it heavily. There are three accountabilities you must know cold. The Product Owner owns the product backlog and decides what gets built and in what priority. The Scrum Master serves the team, removes impediments and protects the process. The Developers, sometimes called the development team, build the increment each sprint.
A common trap is confusing the Scrum Master with a traditional project manager. The Scrum Master is a facilitator and coach, not a boss who assigns tasks. Equally, the Product Owner sets priorities but does not dictate how the team does the work. Knowing these boundaries answers many primer questions directly.
- Product Owner: owns and prioritises the product backlog
- Scrum Master: facilitates, coaches, removes impediments
- Developers: self-organise and build the sprint increment
- Scrum Master is not a manager; the team is self-organising
Sprints, ceremonies and artefacts
A sprint is a fixed-length time box, often two weeks, in which the team produces a usable increment. Within each sprint there are four events. Sprint Planning decides what the team will deliver. The Daily Scrum is a short daily sync to inspect progress. The Sprint Review demonstrates the increment to stakeholders. The Sprint Retrospective reflects on how to improve the next sprint.
You should also know the three artefacts: the Product Backlog, the Sprint Backlog, and the Increment. Questions often pair a ceremony with its purpose or ask which artefact a given activity updates, so practise matching them quickly.
- Sprint Planning: decide the sprint goal and selected work
- Daily Scrum: 15-minute sync, not a status report to a manager
- Sprint Review: demonstrate the increment to stakeholders
- Sprint Retrospective: inspect and improve the process
- Artefacts: Product Backlog, Sprint Backlog, Increment
DevOps core concepts: CI, CD and pipelines
DevOps questions centre on continuous integration and continuous delivery. Continuous integration means developers merge code frequently into a shared branch, where automated builds and tests run on every change to catch problems early. Continuous delivery extends this so that a validated build can be released to production at any time with minimal manual steps; continuous deployment goes one step further and releases automatically.
A CI/CD pipeline is the automated sequence that takes code from commit to deployment: build, test, package, and release. The primer wants you to understand why this matters, namely faster feedback, fewer integration surprises, and more reliable releases, rather than the configuration details of any single tool.
- Continuous integration: frequent merges with automated build and test
- Continuous delivery: always-releasable builds with a manual gate
- Continuous deployment: automatic release with no manual gate
- Pipeline stages: build, test, package, deploy
Version control and collaboration basics
Version control underpins both Agile and DevOps, so the primer usually includes a few Git-flavoured questions. Understand that a repository stores your project history, a commit records a set of changes, and a branch lets you work in isolation before merging back. Know what a merge conflict is and why pull requests or merge requests help teams review changes before they land.
You do not need to memorise advanced Git commands. Focus on the concepts: why teams branch, what merging does, and how code review fits into the DevOps flow. These ideas connect directly to the CI/CD pipeline questions discussed above.
Sample question styles and how to prepare
Expect three flavours of question. Definition questions ask you to pick the correct meaning of a term like burndown chart or impediment. Role and ceremony questions give a scenario and ask who is responsible or which event applies. Concept questions test the why, such as the main benefit of continuous integration.
Because the material is definition-led, flashcard-style revision works extremely well. Read the concepts, then drill yourself with practice questions until the vocabulary is automatic. A topic-wise question bank for Agile and DevOps, followed by a timed mock that mixes both areas, is the most efficient way to lock in the terminology before your assessment.
- Definition questions: match a term to its precise meaning
- Scenario questions: identify the right role, ceremony or artefact
- Concept questions: explain the benefit of a practice like CI
- Revise with flashcards, then drill timed practice questions
Frequently Asked Questions
Is the Agile and DevOps primer difficult?
It is concept-heavy rather than difficult. There is nothing to calculate or compile; you mainly need precise definitions and the ability to match scenarios to the right idea. Because it is vocabulary-driven, it is one of the most learnable primers in a short time.
What is the difference between the Scrum Master and a project manager?
The Scrum Master is a facilitator and coach who helps the team follow Scrum and removes impediments, but does not assign tasks or command the team. A traditional project manager directs work and owns delivery. The Scrum team is self-organising, which is a common primer test point.
What is the difference between continuous delivery and continuous deployment?
Continuous delivery keeps every validated build ready to release but a human triggers the actual release. Continuous deployment removes that manual gate, so every change that passes the pipeline is released to production automatically. Both rely on strong continuous integration first.
Do I need to know Git commands for the DevOps primer?
You need the concepts more than the commands. Understand repositories, commits, branches, merges, merge conflicts and pull requests, and how code review fits into the pipeline. Memorising advanced command syntax is not the focus of the primer.
How long should I study for the Agile and DevOps primer?
Two to three focused days is usually enough because the content is definition-led. Spend one session on Scrum roles, ceremonies and artefacts, one on CI/CD and version control, and a final session on timed practice questions to make the vocabulary automatic.
What is the best way to revise Agile and DevOps concepts?
Use flashcard-style revision for the terminology, then drill a topic-wise question bank covering both Agile and DevOps. Finish with a timed mock that mixes the two areas so you can recognise concepts quickly under exam conditions.
Ready to practice?
Put this into action with 1400+ Accenture primer questions, 2026 mocks and coding hands-on.
Start practising free