Deep dives into how Orvezo's features work, why they were built the way they were, and how to get the most out of them.
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.
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.
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.