Every tech job listing mentions Agile, Scrum, or Kanban. If you are coming from outside the industry, those words can feel like a foreign language. They are not complicated — but understanding them will make you sound fluent in interviews and help you hit the ground running when you land your first role.
Waterfall: the traditional approach
Waterfall is a sequential project management approach. Teams work through distinct phases in order: requirements gathering, design, development, testing, deployment. Each phase must be complete before the next begins. Waterfall works well when requirements are fixed and well-understood upfront — think large infrastructure projects, government contracts, or construction. In software, it fell out of favor because requirements almost never stay fixed, and the cost of discovering a problem late (in testing or after launch) is enormous.
Agile: the iterative alternative
Agile is a philosophy, not a single method. It prioritizes delivering working software in short cycles, responding to change over following a fixed plan, and keeping users at the center of every decision. Instead of building everything before testing anything, agile teams release frequently and learn from real user behavior. Most tech companies are agile-first — which means the vocabulary matters from day one.
Scrum: agile in practice
Scrum is the most common agile framework. It organizes work into sprints — typically two-week cycles where the team commits to a defined scope and ships it. Key terms: a sprint is the work cycle; sprint planning is where the team decides what to build; the daily standup is a short check-in where everyone shares what they did yesterday, what they are doing today, and what is blocking them; the sprint review is where the team demos what was built; the retrospective is where the team reflects on how to work better. The backlog is the prioritized list of all work to be done. The sprint backlog is the subset pulled into the current sprint. Understanding these terms lets you participate meaningfully in any product team from week one.
Kanban: continuous flow without sprints
Kanban is a lighter approach that uses a visual board — columns like To Do, In Progress, and Done — to track work items as they flow through the system. There are no sprints; work moves continuously. Kanban is common for support teams, operations roles, and some engineering teams that prefer a steady flow to a fixed sprint cadence. Tools like Jira and Linear both support kanban-style boards.
How to talk about it in interviews
You do not need to have worked in an agile environment to demonstrate fluency. What interviewers want to see is that you understand the vocabulary and the underlying logic. "I understand your team runs two-week sprints — I am comfortable with that cadence and have studied the scrum framework" is a credible statement from a career changer. Being able to ask intelligent questions about the team's ceremonies, backlog management, or how they handle scope changes signals that you will integrate quickly. That vocabulary gives you the confidence to show up on day one sounding like you belong.