BLOCKER Don't lose the CI failure in the daily
This pull request is blocked by a failed CI run.
Ask: Is the CI fix clear, or does the author need help right away?
Sources: ci | repo
Daily prep, done for you For Tech Leads and Scrum Masters
Know what's stuck
before the daily.
The review nobody picked up. The build left red overnight. The teammate who went quiet. Your tools already saw all of it. Scrum-OS puts it on one agenda before the meeting starts, so the daily solves problems instead of hunting for them. Below: Thursday morning of a demo team.
Get early access See what it catches
6 months free for everyone on the waitlist.
Team cockpit | Lead Bottleneck Sample data, not a real team.
REV | Review Hub Thursday | 09:15
CI red | Thu 09:15
-
Flow risks
2
PRs or tickets need a decision today.
-
CI
1 red Blocks merge
Required check blocks the merge of fix/rev-101-timezone-activity-filter | PR #1001.
-
Reviews
1
1 pull request has been waiting longer than 1 day for feedback.
-
Ops
PROD alert
review-hub-api looks off after a deployment.
-
Since last daily
8 events
3 developers active | 0 new PRs | 1 merge
-
Sprint goal
25% Tense
1 of 4 sprint items done
Reachable if the open flow risks are settled today.
Open reviews by permitted reviewer
3 of 3 open pull requests may only be reviewed by one person.
- MiraLead3 open reviews
- JonasBackup reviewer0 open reviews
- LeaAuthor0 open reviews
- NoahAuthor0 open reviews
Daily agenda
since daily WED 09:15
Today the team needs 3 decisions so flow doesn't tip.
A review stall, a red required check and an ops signal worth a look are the most important talking points from the event store.
-
-
REVIEW STALL Clear the review stall first
This pull request needs a review or a pairing decision.
Ask: Who takes the review today, or who helps the author directly?
Sources: repo | review
-
DEPLOY WATCH Watch the service after the deploy
The alert for review-hub-api lines up in time with a deployment.
Ask: Is the alert understood, or does someone look at the deploy today?
Sources: cd | monitor
7 sources analysed
One sprint week
Three dailies. Three problems nobody mentioned.
None of them is dramatic, and that is exactly why they slip through. Each one quietly costs the sprint days before anyone says it out loud. Here is how Scrum-OS catches them on the morning they matter.
01 Wednesday | 09:15
A pull request waiting since Monday. Nobody noticed.
Lea opened it on Monday evening. The one person allowed to review it had a packed Tuesday, and by Wednesday it has dropped off everyone's radar. Scrum-OS puts it on the agenda with the branch, the PR number and how long it has been waiting. It gets raised today instead of whenever someone remembers, and nobody has to be the one who nags.
- feature/rev-102-open-pr-filters | PR #1002 waiting 1d 15h without review activity
- No CI card and no ops card: there is nothing to report there yet, and the cockpit says so instead of filling the gap.
Team cockpit | Lead Bottleneck Sample data, not a real team.
REV | Review Hub Wednesday | 09:15
Synced | Wed 09:15
-
Flow risks
1
PRs or tickets need a decision today.
-
Reviews
1
1 pull request has been waiting longer than 1 day for feedback.
-
Since last daily
6 events
2 developers active | 2 new PRs | 0 merges
-
Sprint goal
0% Stable
0 of 4 sprint items done
Goal: make the review bottleneck around the lead visible and cut waiting times.
Daily agenda
since daily TUE 09:15
-
REVIEW STALL Clear the review stall first
This pull request needs a review or a pairing decision.
Ask: Who takes the review today, or who helps the author directly?
4 sources analysed
- No CI card: every run in the store so far reports success.
- No ops card: no deployment and no alert in the event store yet.
02 Thursday | 09:15
The build went red at 17:15. Nobody touched it overnight.
A review comment, a fix pushed at 16:50, a failed run at 17:15, then silence. Scrum-OS knows the difference between a build someone is fixing and a build nobody has picked up. Only the second one deserves time in the daily. On the same agenda: a second review waiting since that night and an alert still open after Wednesday's deployment.
- fix/rev-101-timezone-activity-filter | PR #1001 red for 16h, nothing pushed since
- refactor/rev-103-api-client-list-cleanup | PR #1003 waiting 1d 21h without review activity
Team cockpit | Lead Bottleneck Sample data, not a real team.
REV | Review Hub Thursday | 09:15
CI red | Thu 09:15
-
Flow risks
2
PRs or tickets need a decision today.
-
CI
1 red Blocks merge
Required check blocks the merge of fix/rev-101-timezone-activity-filter | PR #1001.
-
Reviews
1
1 pull request has been waiting longer than 1 day for feedback.
-
Ops
PROD alert
review-hub-api looks off after a deployment.
Daily agenda
since daily WED 09:15
-
BLOCKER Don't lose the CI failure in the daily
This pull request is blocked by a failed CI run.
Ask: Is the CI fix clear, or does the author need help right away?
-
REVIEW STALL Clear the review stall first
This pull request needs a review or a pairing decision.
Ask: Who takes the review today, or who helps the author directly?
-
DEPLOY WATCH Watch the service after the deploy
The alert for review-hub-api lines up in time with a deployment.
Ask: Is the alert understood, or does someone look at the deploy today?
7 sources analysed
03 Friday | 09:15
Noah went quiet. That's a question, not a verdict.
Noah opened his pull request on Tuesday and nothing has come from him since. His one permitted reviewer never got to it, so there was nothing to answer and nothing to push. Scrum-OS does not treat that as a performance problem and reports it nowhere. It adds one line to the agenda, so the lead can ask what is in the way on Friday instead of next week.
- Noah, no recorded activity for more than two days
- refactor/rev-103-api-client-list-cleanup | PR #1003 on the agenda for the second daily in a row
Team cockpit | Lead Bottleneck Sample data, not a real team.
REV | Review Hub Friday | 09:15
Synced | Fri 09:15
-
Flow risks
1
PRs or tickets need a decision today.
-
Reviews
1
1 pull request has been waiting longer than 1 day for feedback.
-
Ops
PROD alert
review-hub-api looks off after a deployment.
-
Since last daily
8 events
3 developers active | 0 new PRs | 1 merge
Daily agenda
since daily THU 09:15
-
REVIEW STALL Clear the review stall first
This pull request needs a review or a pairing decision.
Ask: Who takes the review today, or who helps the author directly?
-
DEPLOY WATCH Watch the service after the deploy
The alert for review-hub-api lines up in time with a deployment.
Ask: Is the alert understood, or does someone look at the deploy today?
-
IDLE DEV Talk to the quiet developer
Noah has produced no visible activity for more than 2 days.
Ask: Blocker, context switch, or missing work packages?
6 sources analysed
- No CI card: no failing run open in the store.
Where the signals come from
Eight tools. One morning briefing.
Nobody watches repo, reviews, tickets, CI, builds, deployments, monitoring and docs at the same time. Scrum-OS does. It pulls every event into one record, so your daily runs on what actually happened, not on what someone remembered to mention.
Eight engineering sources, code repo, code review, issue tracker, CI, build server, CD, monitoring and documentation, all feeding one central event store.
Event store
- Code repoCommits & PRs
- Code reviewReviews & approvals
- Issue trackerTickets & sprint
- CIPipelines & checks
- Build serverBuilds & artifacts
- CDDeployments
- MonitoringAlerts & metrics
- DocumentationGoals & tasks
Every item in the cockpit points back to a real event with a timestamp. No guessing, and no summary without evidence.
How it works
Set it up once. Get a ready agenda every morning.
Connect your stack
Plug in the repo, review tool, CI, issue tracker and monitoring your team already uses. Nobody logs anything twice, and nobody has to change how they work.
It watches the work
Scrum-OS follows what is open, what is waiting and what is red. It follows the work, not the people: no scores, no rankings, nobody gets rated.
Walk in ready
Your agenda is waiting before the meeting starts, sorted by what is holding things up most. The daily goes to decisions, not to status updates.
Start with the daily. Keep the same view open for the rest of the sprint.
What it catches
The problems you usually hear about too late.
Most sprint blockers are not hidden. They are scattered across five tools and only get noticed when someone happens to look at the right moment. Scrum-OS looks every morning and puts what it finds on one page.
Work that stopped moving
A change that has been open for a while with nothing happening on it. Often it is fine, and the daily confirms that in ten seconds. Sometimes it is not, and you find out before it costs a week.
Reviews nobody picked up
Waiting for a review is the quietest way a sprint loses days. Scrum-OS shows what is waiting and for how long, so it no longer depends on who happens to notice.
Builds left red
A failing check with no fix pushed. If someone is already on it, it is not a topic for the daily. If nobody is, it is. Scrum-OS tells you which.
Work going in circles
The same change coming back round after round. That is rarely a careless author. It is usually a scope nobody really agreed on, and it needs a conversation, not another round.
Someone who went quiet
No visible activity for a while. Blocked? Pulled onto something else? Working somewhere Scrum-OS cannot see? It is a question for the lead to ask, never a conclusion for the tool to draw.
Every signal points at a piece of work, never at a person. If one is wrong, a single sentence in the daily corrects it.
Your data
It reads your stack. It can't change a thing.
Before a team lets a tool near its repo, it wants answers. Here they are, up front.
Read-only, always
Scrum-OS reads events and writes nothing back: no comments, no labels, no status changes, no merges. Switching it on changes nobody's workflow.
Metadata, never your code
Branch names, titles, authors, reviewers, timestamps, build results, ticket references. File contents and diffs are never ingested.
No scores, no rankings
Scrum-OS never rates a person and never produces a number about one. It shows a piece of work and how long it has been stuck.
Early access
Your next daily could start with the answers.
We are starting with the daily and building towards the whole sprint. Join now and you get Scrum-OS free for six months, plus a direct say in what we build next.
6 months free at launch.
What happens next
- Join in under a minute Your email is all we need. A few optional questions about your team and tools help us build for you, and skipping them won't cost you your spot.
- Get your invite When your spot opens, you get one email with your access link and a short guide to connect your repo and CI.
- Six months free Everyone on the waitlist gets the first six months after launch at no cost.