User manual
Day-to-day work in Maevu: triage, planning, calendars and sharing.
Alpha. Screens and details will change. This describes how Maevu is meant to be used.
Triage
Triage is how a pile becomes a plan. Maevu reads your backlog through a hierarchy adapter, so epics, stories, tasks and bugs from any tracker map onto the same shape.
- Buckets — order work into quarters (this quarter, next, later). Buckets are about ordering, not commitment: not everything gets scheduled, and that’s fine.
- Fullness — each bucket shows how full it is against rough capacity, so you can see when a quarter is overcommitted before you promise it.
- Split — break a larger item into phases (analysis, build, review, test) when you want finer control.
Planning
Planning is where Maevu earns its keep. A real constraint solver schedules the work you’ve triaged, respecting:
- Capacity — who is available, part-time, or away.
- Roles — an architect reviews and designs; a developer implements. Assignment respects who does which kind of work, not just who’s named on a ticket.
- Skills — the right person is faster at the right work; Maevu weighs “free but slow” against “busy but expert.”
- Calendars — meetings and time off shrink the day before anything is scheduled.
Every placement can explain itself: which dependency, whose capacity, which date drove it.
Calendars
Connect a calendar (Microsoft or Google) and Maevu subtracts real commitments — team ceremonies, personal events, time off — from each person’s day. It reads free/busy by default: when someone is busy, never why.
Sharing
Publish a read-only board or daily calendar and send the link. Different audiences get different views — internal detail for your team, a clean summary for a customer.