You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upstream is where work is born, sorted, and prepared. In agile context this is comparable to backlog. It's all the things that you could potentially do, in no particular order, not sorted — yet. Things ideally move from left to right in a kanban, in the upstream board you are pushing them up-hill. Towards the tipping point.
Tipping point The tipping point is when an item is prioritized, and made workable and you are pushing it into the downstream board
Downstream is all the stuff that is in your near-future focus, stuff that must be done within the next couple of days. In the downstream board things flow downhill — easy, frictionless.
Minimize work in progress in the downstream board we actively strive to minimize the amount of work in progress, it's carefully balanced to the actual ressources available through a pull system.
kanban means "signal" in a kanban board, some of the columns are defined as kanbans, You can say that thy are supposed to be empty, so when they are not it's a signal. "Blockers" is an example of a kanban
Upstream and downstream in the same board. This is an adaption to usage in GitHub, it's simply easier to model it like this.
The tipping point is between Is Workable and To Do.
Kanbans needs immediate focus
Backlog Half baked ideas, memos, wishes, note to self. Anything goes in this column. No rules!
Is Workable Last stop in the upstream board before the tipping point to the downstream board. Issues here must qualify to downstream.
Unambiguous description
Desired outcome is known (ask: "What are you hoping to achieve")
To Do Welcome to the downstream board, issues here are in scope and should be worked in the nearest foreseeable future (2-5 days, cycle time is ticking ⏳)
In Progress issues here are actively being worked by someone (assign someone to the issue) This column has a WIP limit
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Upstream and Downstream
Kanban lingo
Upstream and downstream in the same board. This is an adaption to usage in GitHub, it's simply easier to model it like this.
The tipping point is between Is Workable and To Do.
Kanbans needs immediate focus
Backlog Half baked ideas, memos, wishes, note to self. Anything goes in this column. No rules!
Is Workable Last stop in the upstream board before the tipping point to the downstream board. Issues here must qualify to downstream.
To Do Welcome to the downstream board, issues here are in scope and should be worked in the nearest foreseeable future (2-5 days, cycle time is ticking ⏳)
In Progress issues here are actively being worked by someone (assign someone to the issue) This column has a WIP limit
Done Archive regularly, ritually reflect-on.-action
Kanbans
Make workable Issues has priority, they need to enter the downstream board, but they don't qualify yet - hurry!
Blocked Issues has been started, but for some reason they are now blocked and can not move forward - Somebody pulled the andon
All reactions