How do sprints work in Horizon?

Sprints run on whole calendar weeks, one to four weeks long, always Sunday to Saturday. Tasks carry story points, the header tracks committed against done, a velocity bar builds a picture of your weeks, and each sprint has a goal, a review, a retro, and a carryover step that moves unfinished work forward on purpose.

Where does Didi take over the sprint busywork?

Through its four layers pointed at the sprint. Capture turns mid-cycle intake into real tasks, Compose drafts the plan so planning is editing not inventing, Clarify shapes a doable today from your due dates and priorities, and Celebrate reads what you finished into your Daily Win Recap and half-writes the retro.

Do I need a Scrum Master or a team to use this?

No. You do not need a Scrum Master, a ceremony calendar, or a room of people. A solo maker or a small squad gets the cadence and the honest account of what finished, with Didi handling the intake, first-draft plan, daily triage, and end-of-cycle reckoning.

Keep the Agile, drop the admin: Didi as your Scrum support

Q: What parts of Agile does ToDidIt actually keep?

Two: working in short cycles so you commit to a little and finish it, and being honest at the end of each cycle about what actually shipped. The cadence and the honesty are the whole value; everything else is administration.

Agile has a reputation problem, and it earned it honestly. Somewhere between the original idea and the average Tuesday, a lightweight way of working turned into a full time job of grooming tickets, updating statuses, sizing everything twice, and sitting through standups that could have been a glance at a board. The method got blamed, but the method was never the problem. The busywork was.

Strip it back and Agile is two good ideas. Work in short cycles so you commit to a little and finish it. Be honest at the end of each cycle about what actually shipped. That is it. The cadence and the honesty are the whole value. Everything else is administration, and administration is exactly the kind of work a good AI partner should quietly absorb. That is the job we gave Didi.

The cadence is built in, not bolted on

The Sprint view in Horizon gives you the cadence without asking you to configure a methodology. Sprints run on whole calendar weeks, one to four weeks long, always Sunday to Saturday. Tasks carry story points, the header tracks committed against done, and a velocity bar builds a real picture of what your weeks hold. Each sprint has a goal at the start, a review and a retro at the end, and a carryover step that moves unfinished work forward on purpose. The framework is there when you want it and silent when you do not.

Where Didi takes over the admin

Scrum has a support role for a reason: someone has to clear the path so the team can just do the work. Didi plays that part through the four layers it already runs across ToDidIt, pointed at the sprint.

Capture is the sprint intake. When an idea or a bug or a request lands mid cycle, you throw it at Quick Capture in plain language and Didi turns it into a real task with a sensible title, due date, and priority, ready to pull into a sprint. Nothing waits in your head or a side note until refinement day.

Compose is sprint planning without the blank page. Describe a goal in a sentence and Project Blueprint drafts the whole project: tasks, subtasks, priorities, and due dates you can size and pull straight into a sprint. Planning stops being a meeting where you invent structure from nothing and becomes editing a first draft that is already mostly right.

Clarify is the daily decision. A sprint backlog is still a list, and a list is not a plan. Clarify reads your due dates, priorities, and what is slipping and helps you shape a doable today. It never hides work or decides for you. It just makes the obvious next move obvious, which is most of what a good standup was ever for.

Celebrate is the honest close. At the end of the day and the end of the sprint, Didi reads what you actually finished and reflects it back in your Daily Win Recap, marks it with Celebration Mode, and keeps your streak without nagging about a missed one. The retro writes half of itself when the record of what shipped is sitting right there in plain language.

What is coming to the sprint

The Daily Focus Brief has since shipped, and it opens your day with the handful of things that matter: what frees up the most other work, and what has been quietly slipping. It is free on every plan.

Some of the most useful Scrum support is still on the way, and we would rather name it as roadmap than pretend it already ships. A Standup Generator that turns your recent activity into a done, doing, blocked summary. Time insight that learns how long work actually takes so your estimates get honest over time. These build on the same metered Didi foundation the other layers use, and they land as they are ready.

Agile for a team of one, or a few

You do not need a Scrum Master, a ceremony calendar, or a room of people to get the good part of Agile. You need a cadence you trust and an honest account of what you finished. Didi handles the intake, the first draft of the plan, the daily triage, and the end of cycle reckoning, so a solo maker or a small squad gets the rhythm of Agile without the overhead that made everyone resent it. The ceremony should serve the work. The admin should serve itself, quietly, in the background, which is exactly where Didi keeps it.