Skip to content
tezvyn:

Agile & Scrum

Scrum, kanban, sprints, team velocity, shipping culture

127 bites

Test yourself: Top 30 easy Agile & Scrum interview questionsMultiple choice, with the correct answer and why it is correct on every question. Free, no sign-in.

Easy everything in Agile & Scrum, page 7

easy2 min read

Minimum Viable Product (MVP): Learn Faster with Less Code

An MVP is the smallest product version that delivers value to early users and provides feedback for future development. Use it to test a business hypothesis with minimal resources, like a single-feature app.

easy2 min read

User Stories: Features from the User's Perspective

A user story is an informal, natural language description of a software feature from the end user's viewpoint. Used in agile development, they're written by stakeholders like clients or developers on Post-its or in apps.

easy2 min read

User Stories: What Users Want, and Why

A User Story is a simple description of a feature from the user's perspective, focusing on the 'who, what, and why' instead of technical details. It's the primary unit of work in Agile, building a shared understanding of what to build.

easy2 min read

The Daily Scrum: A 15-Minute Team Sync

The Daily Scrum isn't just a status update; it's a 15-minute planning session for the next 24 hours. Team members sync on progress, identify blockers, and adjust their plan for the day. The footgun is treating it as a report to a manager.

The Sprint: A Timeboxed Rhythm for Work
easy2 min read

The Sprint: A Timeboxed Rhythm for Work

A sprint is a fixed-length container, typically 1-4 weeks, where a team turns ideas into a valuable product increment. Sprints give a predictable rhythm to software teams and marketing campaigns. The footgun is treating a sprint as a mini-waterfall project.

easy2 min read

Waterfall Model: Build Software Like a Building

The Waterfall model treats software development like building a house: each phase is fully completed before the next begins. It suits projects with fixed requirements, but its major footgun is that late-stage changes can force a costly restart from the…

easy2 min read

The Agile Manifesto: A Shift in Software Values

The Agile Manifesto is a value system, not a rigid process. It prioritizes people, working software, customer collaboration, and adapting to change over rigid plans and documentation. This philosophy underpins frameworks like Scrum.

We are hiring for this. Every open role lists the topics its interview covers, so you can prepare for the real thing rather than guessing.

See open roles