Product updates, practical delivery workflows, and build-in-public notes from the Orvezo team.
A 47-tab Google Sheet. A column called STATUS2 that nobody could explain. Sprint planning that took two hours and fifteen minutes for a team of three. Here is what actually happens when a team tracks sprints in a spreadsheet for too long.
Sprint planning overhead — writing tickets from PRDs, setting up boards, tracking blockers, closing sprints — takes hours that compound across every sprint. Here is what actually changes when you connect an AI agent to your project management tool.
Sprint planning should take 60 to 90 minutes for a two-week sprint. Most teams spend three to four hours. The difference is almost never the meeting itself — it is everything that did not happen before the meeting started.
Sprint blocker indicators stop working when teams use them for everything. Here is why sprint blockers get ignored, how dependency fatigue happens, and how to separate active blockers from sequencing constraints so the signal stays meaningful.
Notion requires you to build your own sprint system from scratch, then maintain it. No native sprint lifecycle, no backlog zones, no dependency graph. Here is what breaks and what dev teams use instead for sprint-based project management.
GitHub Projects is free and lives next to your code. For teams running structured sprints with a real backlog and carry-over handling, the configuration overhead adds up fast. Here is where it falls short and what to use instead.
Linear is well-designed and increasingly built for teams of 15 or more. For a 2 to 5 person dev team, you are paying for features you will never use and hitting a 250-issue free plan cap faster than you expect. Here is how they compare.
Trello has no native sprints, no backlog, no epics, and no dependency management. Dev teams running agile workflows end up assembling these from Power-Ups that do not integrate cleanly. Here is what you are missing and what to use instead.
Jira is the default for dev teams. For teams of 2 to 5 people it is also the wrong choice. Here is an honest breakdown of setup cost, pricing, sprint workflow, and daily friction — and what to use instead.
How to plan, run, and close a two-week sprint for a small dev team. Sprint lifecycle states, how to populate a sprint from the backlog, what to do with carry-over, and how to plan multiple sprints ahead.
Jira, Linear, Asana, and Orvezo all model sprint dependencies differently. Some give you one relationship type for everything. Others separate active blockers from planned sequencing. Here is how each tool handles it and why the distinction matters.
How to track story dependencies in a sprint — which stories block other stories, which are sequenced after something else, and how to make both visible on the board so nothing gets missed during planning or execution.
How to select multiple stories and reassign, reprioritize, or move them to a different sprint in one action. The fastest way to clean up a backlog, handle carry-over, or redistribute work when team composition changes.
How to set up a sprint workflow for a small dev team from scratch. Covers workspaces, projects, backlog structure, sprints, epics, the board, and how to go from zero to a running sprint in one session.
How to see all your assigned stories across multiple projects in one view — what is due today, what is in progress, what is coming up — without switching between project boards.
How to structure a sprint backlog so planning is fast and stories are ready to pull. The difference between a parking lot, a backlog queue, and an active sprint — and why keeping them separate matters.
Most teams that set up Jira correctly still end up not using it. The system gets too heavy, updates stop happening, and the board stops reflecting reality. Here is how that happens and what small teams do instead.
How to separate ideas that are not ready from work that is queued and ready to pull into a sprint. A parking lot keeps your backlog clean without losing anything that might matter later.
How to set up and run a sprint board for a small dev team. What the columns mean, how to surface blocked work before standup, and what happens when you close a sprint versus marking a story done.
Sprint after sprint, something breaks — carry-over, scope creep, retro action items that vanish. The team is not the problem. These are structural issues that exist before the sprint starts. Here is what is actually breaking your sprints and how to fix each one.