Scrum👥 scrumia-teams
Standing roles, and the policy that decides which model runs a ticket.
slot · team
version · 0.5.0
What it is responsible for
Owns who is in the room: the manager, the business and the tech roles, each permanent through project memory and board state rather than a live process. Owns the sprint too — a batch of tickets consumed as dynamic workflows, one isolated worktree each — and the scope × risk matrix that answers which model a ticket runs on.
What it refuses
Each role is defined by what it declines. The manager owns no business rule, the business role owns no architecture, the tech role owns no priority — without those lines the three collapse into one generalist and the split stops paying for itself.
The assumption it makes
Assumes a split that refuses is worth more than a generalist that agrees. Costs a configuration to keep honest: three is not a magic number, and turning a role off is a documented trade-off rather than a downgrade.
Its skills
scrumia-sprintscrumia-sprint-fastscrumia-standupscrumia-team-setup
What it plugs into
| Register | Direction | Module |
|---|---|---|
convene | opens | scrumia-design |
sprint | opens | no contribution |
Install it
/plugin install scrumia-teams@scrumia