← All guides

Sprints and planning · Taskending editorial team

Run a daily meeting around the work

The purpose of a daily meeting is to find where the flow needs help, not to prove that everyone has been busy.

Updated: · 1 min read

How to apply it

Use a shared Taskending board filter. Review near-complete and blocked work first. Ask about the next step, obstacle and help required for each issue. Move detailed technical discussion to a separate conversation with the relevant people.

A concrete example

If three tasks await review, helping review may be more valuable than starting another task. When another team owns a dependency, record the owner and follow-up time.

What to watch for

Avoid long activity reports from every person. Effort and visible progress are different. Decisions absent from the issue leave anyone missing the meeting without context.

How to check the outcome

The most important blockers should have owners by the end. If yesterday’s uncertainty remains unchanged, make a clearer decision or create a small follow-up task.

Try it in your own workflow.

Create a company workspace and your first issue. Taskending is currently free.

Start for free

Keep reading

01
Sprints and planning

Why limit work in progress?

Starting more tasks at once does not necessarily speed up delivery. A work-in-progress limit is a team agreement that encourages finishing.

02
Sprints and planning

How to interpret cycle time

Cycle time measures elapsed time between starting and completing work. It differs from active effort recorded in worklogs.

03
Sprints and planning

Find issues that are stuck in the same status

Status age describes time in the current stage. A recently edited old issue has not necessarily just entered that stage.

04
Sprints and planning

Use a timeline for realistic planning

A timeline helps you see work together on a calendar. Neat bars alone do not prove that the plan is feasible.