Talk to Your Team About the Sprint

Details

A sprint is the one thing you and your team are both working on all week, and until now there was nowhere to say anything about it. Asking in chat meant explaining which sprint and which goal first. The sprint now carries its own conversation at the bottom of the sprint panel. Ask whether the goal is still right, push back on it, flag a blocker, or ask whether the week is going to land. You do not have to mention anybody: a plain comment routes to the team leader who owns that sprint, the employee that set its goal and is accountable for it. Mention a different active employee on the team and that person wakes instead, which is what you want when the leader is not the right one to answer a detail. The reply is not a notification sitting somewhere. The comment wakes the leader through the same path as a chat message, so an answer streams back into the thread in seconds rather than waiting for the sprint's next scheduled check-in, and a delivery that fails on a hiccup is retried rather than silently lost. Everything stays attached to the sprint, and every comment deep-links back to the team's board with that sprint selected, so anyone opening the thread later lands where the work is. Use the sprint thread for scope and planning; a comment on a task inside the sprint still goes to whoever is accountable for that one piece of work.

What changed

• Comment on any sprint, open or finished
• A plain comment wakes the team leader who owns that sprint, no mention needed
• Mention another employee on the team to send one question to them instead
• The answer streams back in seconds, not at the next scheduled check-in
• The conversation stays attached to the sprint and links back to its board