-
Notifications
You must be signed in to change notification settings - Fork 32
Digital Kanban
Ryan Wold edited this page Jul 1, 2019
·
5 revisions
- 📥 Inbox - ideas, user feedback, new specifications that emerge as work is delivered.
- ❄️ Icebox - valid work, but needs definition
- ✏ Needs Design - valid work, but needs design and definition
- 📋 Backlog - valid work, prioritized according to 1) user value + 2) throughput
- 🎯 Current - valid work, prioritized and scope for one iteration
- 👀 Acceptance - review to ensure work is delivered according to definition
- ✅ Done - accepted work. work otherwise done. work otherwise decided not to do and is done being considered.
- New cards are added to the Inbox. Anybody can add a card.
- Cards move left toward
Done
. - People add themselves to card. Don't assign somebody to a card unless on their behalf. Team members take ownership for their work.
- Inbox is groomed by the team at least weekly.
- is a card clearly written?
- Does the Card have an Owner?
- If the Card has more than 1 member, is a specific member referenced in the Checklist?
- Does the Card have acceptance criteria/a clear definition of done?
- Does the Card have a checklist representing the work to be done to get from the current state to the desired
done
state? Is that work bite-sized enough? (Objectively complete-able?)
- Always to try to move a card forward by adding clarity or taking action