A sprint you cannot see is a sprint you find out about at the end. Three things make it visible while there is still time to act.
Velocity
The velocity trend shows how many points the team has completed across recent sprints. It answers one question well: is this round consistent with what we normally do?
Use it for capacity, not for performance. Velocity varies with the kind of work as much as the effort, and a team measured on it will inflate estimates, which destroys the only thing it was good for.
On track
The sprint carries a status showing whether it is progressing as expected. It is a summary, not a diagnosis. When it says a sprint is behind, the board tells you why.
Standups
Standups can link automatically to meetings already in your calendar, or you can link one by hand. The automatic match works off the meeting title, so a clearly named recurring meeting is worth having.
Retros, and where the learning goes
A retro closes the sprint. What matters is not the conversation but what survives it.
Learnings are recorded in the Learning Ledger, which is the durable record across sprints. That is deliberate: a note attached to one sprint gets read once and never again, whereas the ledger is the thing a team can look back through when the same problem reappears.
If your retros are producing no ledger entries, the retro is happening but not landing.
The Scrum Manager
A built-in assistant watches the sprint and gives short plain updates: what is in progress, how many points are done, whether anything is blocked. You can also ask it directly, for example why the team is behind or what is blocked right now.
It reads the board. That means it is exactly as accurate as the board is current, and a team that updates status once a week at the end will get answers that were true on Monday.
Did this answer your question?
No, ask a person