No jargon-on-jargon definitions — just what these terms actually mean and where you'd use them.
A visual board where tasks are cards that move across columns — typically To Do, In Progress and Done — so anyone can see the state of work at a glance without asking. Cards can carry assignees, due dates, tags and attachments.
Good for: ongoing work with no fixed end date — support queues, content pipelines, general team task tracking. Try it in TaskInSync's kanban board.
A fixed, short time box — commonly one or two weeks — during which a team commits to a specific set of tasks pulled from the backlog. At the end, the team reviews what shipped and plans the next sprint.
Good for: teams that want a steady, predictable rhythm of planning and delivery, especially engineering and product teams.
The full list of tasks, ideas and features a team intends to work on eventually, but hasn't yet scheduled into a sprint or given a date. A healthy backlog is groomed regularly — old or irrelevant items get removed, important ones get prioritized higher.
A horizontal bar chart that lays tasks out against a timeline — each bar shows a task's start date, end date and how it connects to other tasks. The classic tool for seeing a whole project's schedule at once.
Good for: projects with real deadlines and sequencing, like launches, builds or client deliverables. See TaskInSync's timeline view.
A rule linking two tasks so one can't start (or finish) until another finishes — for example, "design" must finish before "development" can start. Dependencies are what make a Gantt chart's timeline shift automatically when an earlier task slips.
A view that shows how much work is assigned to each person over a period of time, so a manager can spot who's overloaded and who has room for more — before it becomes a missed deadline.
A single point in time on a project's timeline that marks something significant — a launch date, a client sign-off, a phase completion — rather than a task with actual work attached to it. Milestones are usually shown as diamonds on a Gantt chart, not bars.
A specific, structured way of running agile work: fixed-length sprints, defined roles (like a product owner), and a set of recurring meetings — sprint planning, a daily stand-up, a sprint review and a retrospective.
A broad approach to project work built around short iterations, frequent feedback and adjusting the plan as you learn — instead of locking in the entire plan before work starts. Scrum and Kanban are both ways of practicing agile.
A project approach where phases run in strict sequence — requirements, then design, then build, then test, then release — with each phase starting only after the previous one is fully done. The opposite instinct from agile's "adjust as you go."
Related guides: Task management software · Project management software · Top 10 tools (2026) · AI project management · Pricing calculator