Agile vs Waterfall
Waterfall builds the whole house from blueprints before anyone moves in — if the family wanted a bigger kitchen, you find out at handover. Agile builds one livable room at a time and asks the family after each one.
How the code gets from a ticket to production. Scrum roles and ceremonies, Kanban, story points, Jira and Confluence, Waterfall vs Agile and the DevOps pipeline.
Waterfall builds the whole house from blueprints before anyone moves in — if the family wanted a bigger kitchen, you find out at handover. Agile builds one livable room at a time and asks the family after each one.
Scrum is a sports season played in short rounds. The Product Owner picks what matters most, the Developers play, and the Scrum Master is the coach who clears obstacles. Every round (a sprint) has a game plan, daily huddles, a showcase and a team talk.
A user story is a wish written from the customer's seat: “As a shopper, I want to save my cart, so I can buy later.” Story points measure how big the job feels — effort, complexity and uncertainty — not hours.
Kanban is a restaurant's order rail. Tickets move from left to right, and there's a limit on how many can be on the grill at once. Stop starting, start finishing.
Jira is the team's to-do board, with receipts. Confluence is the team's wiki: where decisions, designs and runbooks live, so nobody has to ask twice.
CI/CD is airport security for code. Every change is scanned (build), checked (tests) and cleared (quality gates) automatically before it can board (deploy). DevOps is the culture that makes the people who build the plane and the people who fly it one crew.
Each topic pairs a plain-language explanation with code, interview questions, and related practice where available.