How a software team runs a sprint in Emitii
- 1
Space
Create a Project space and turn on Docs & Files.
- 2
Backlog
Add cards labelled Feature, Bug or Chore with priorities.
- 3
Spec
Write a spec doc for larger features and discuss it in comments.
- 4
Planning
Move cards to Ready and add the sprint label at the planning event.
- 5
Build
Work across In progress, Review and Testing with a card limit.
- 6
Standup
Post daily in a Pulse thread or ask Emit for a summary.
- 7
Release
Post release notes, archive done cards and hold the retro.
Who this setup is for
Small software teams, product studios and agencies building apps for clients. It suits teams that want a clear board and written specs without configuring a heavy issue tracker.
This is a written setup you follow by hand, and it takes a few minutes.
Spaces to create
| Space | Space type | Purpose |
|---|---|---|
| Product or project name | Project | Backlog, sprints, specs, standups |
| Engineering | Internal | Team conventions, on-call notes, hiring |
For client builds, create one Project space per client project and invite the client as guests.
Modules to turn on
The Project type starts with Board, Tasks, Schedule, Timesheet, Posts and Activity, plus Pulse. Turn on Docs & Files. Keep the Timesheet for client work; turn it off for internal products if nobody tracks hours.
Board columns
Backlog, Ready, In progress, Review, Testing, Done.
- Set a card limit on In progress (for example, two per developer).
- Labels: Feature, Bug, Chore, plus one per sprint ("Sprint 12").
- Priority: Urgent, High, Medium, Low.
- Use Mark as blocked with a reason instead of a separate Blocked column.
- Use the card checklist for acceptance criteria, and "Turn into a card" when an item grows.
Task lists and example to-dos
- Release: "Update release notes", "Tag release", "Post release announcement"
- Maintenance: "Review open bugs" (repeats weekly), "Rotate test accounts" (repeats monthly)
Docs and folders
Create folders for Specs, Decisions, Architecture and Release notes. Write one spec doc per larger feature and link to it from the card description. Team members comment on the spec before work starts.
Schedule
Add recurring events for sprint planning, a weekly demo and a retro at the end of each sprint. Card due dates appear on the Schedule, which helps before a release.
Pulse and Posts
Run the daily standup as a thread in Pulse. Emit, the space AI, can answer "What is blocked or overdue?" or write a sprint recap into Docs & Files after you approve it. Use Posts for release announcements and decisions the whole team must read.
If your organisation has the Emitii CLI turned on, developers can let coding agents read and update cards and docs through MCP.
Timesheet
For client builds, log time against cards, marked billable, and submit each week. Hours export to CSV.
Optional board Rules
- When a card with the Bug label is created, set priority to High.
- When a card enters Review, assign the reviewer.
- When a card enters Done, mark it complete.
- When a card is reopened, move it to In progress.
Keeping the board honest
A board is only useful if it matches reality. Agree as a team that a card moves the moment its status changes, not at the end of the day. Use the board filters (People, Labels, Priority, Blocked, Hide done) before planning sessions to see what is stuck, and search the board for a bug before reporting it again, since search covers descriptions, checklists and comments. After each sprint, archive the cards in Done so the next sprint starts clean. If a column keeps hitting its card limit, that is a signal to finish work before starting more.
Try it
Read the product development use case, see how software companies use Emitii, and learn about board automation. Emitii is invite-only: request access, or try the software team live demo from the Emitii home page.
Frequently asked questions
- How do I track acceptance criteria?
- Use the card checklist. Each item can be ticked off, and a checklist item can be turned into its own card.
- Can board moves be automated?
- Yes. Board Rules can set priority, assign people or mark a card complete when it is created or enters a column. Rules have a preview, a run log and undo.
Related
- Product developmentHow software and product teams run features, bugs, specs and standups in an Emitii space, with board rules, docs and the CLI for coding agents.
- Software companiesSoftware companies use Emitii for sprint boards, standup chat, specs and client delivery in one place, with a CLI and MCP server for coding agents.
- Board automationEmitii board Rules react to card changes with triggers, conditions and actions, and include a dry-run preview, a run log and undo for every run.
- Emitii vs JiraCompare Emitii and Jira on boards, planning, chat, docs, time tracking, automation, AI, integrations and access, and find out which kind of team fits each.
- Tasks & boardSet up board columns and cards in Emitii, use priorities, labels, blocked flags and checklists, filter the board, run to-do lists and write board rules.