If you have looked at a single tech job listing in the past five years, you have seen the words Agile, Scrum, sprint, standup, or retrospective. For people coming from outside the tech industry, this vocabulary can feel like a barrier. It is not — the concepts underneath the jargon are straightforward, and you can learn them in an afternoon. Here is a plain-English guide to everything you need to know.
Agile: a mindset, not a method
Agile is a philosophy for building software. The core idea: instead of planning everything upfront and then building for months before showing anyone, deliver working software in short cycles, get feedback from real users, and adjust based on what you learn. Agile values iteration over perfection, collaboration over documentation, and responding to change over following a fixed plan. Most tech companies operate in some version of an agile way.
Scrum: the most popular agile framework
Scrum is the most widely used way of putting agile into practice. It gives teams a specific structure — defined roles, regular ceremonies, and clear artifacts — that makes agile concrete and repeatable. When a job description says "you will work in an agile environment," they almost always mean Scrum or something close to it.
The 3 Scrum roles
The Product Owner sets the direction — they own the backlog (the prioritized list of work) and make decisions about what the team builds next and why. The Scrum Master facilitates the process — they run the ceremonies, remove obstacles that slow the team down, and protect the team from scope changes during a sprint. The Development Team does the building — typically engineers, designers, and QA, working together to deliver the sprint goal.
The 4 Scrum ceremonies
Sprint Planning happens at the start of each sprint. The team pulls items from the backlog, commits to what they will deliver in the next two weeks, and breaks the work into tasks. The Daily Standup is a fifteen-minute daily check-in where each team member answers: what did I do yesterday, what am I doing today, and is anything blocking me? The Sprint Review happens at the end of the sprint — the team demos what they built to stakeholders and collects feedback. The Retrospective follows immediately after: what went well, what did not, and what will we do differently next sprint?
The 3 Scrum artifacts
The Product Backlog is the master prioritized list of everything the team might build — maintained and ordered by the Product Owner. The Sprint Backlog is the subset of items the team has committed to delivering in the current sprint. The Increment is the sum of everything completed in the sprint — working, potentially shippable software.
Why this matters for your job hunt
You do not need to have worked in a Scrum team to be credible about it in an interview. What you need is the vocabulary and the underlying logic. When an interviewer asks how you handle shifting priorities, you can reference sprint planning and backlog grooming. When they ask about cross-functional collaboration, you can speak to the three Scrum roles and how they interact. The vocabulary signals that you will not need a month of onboarding to understand how the team operates. For a structured path into the Scrum Master role specifically, the Scrum Master track on NewRoleKit covers certifications, practical skills, and how to land your first role.