»Does Your Kanban Board Include Sprint Backlog Tasks?
-
-
@agile Good point!
This is where different sorts of mix words like Scrumban or Krum come in to use some portions of the scrum concepts without the sprints or without the value focus and more for pure achievement of the teams chores (I don't say that this is a recommended way).There are a lot of scrum and kanban labeled teams out there with GettingThingsDone boards
-
@agile Good point!
This is where different sorts of mix words like Scrumban or Krum come in to use some portions of the scrum concepts without the sprints or without the value focus and more for pure achievement of the teams chores (I don't say that this is a recommended way).There are a lot of scrum and kanban labeled teams out there with GettingThingsDone boards
@st3fan
Don't agree much: if the system I want to represent is the team work, then the Kanban board shall contain techy things.
And it's not even necessary to do Scrum at all: Kanban cadences for replenishment and the like are enough as well.
And obviously you can hand different Kanban levels (operations, strategy, ...) on different boards.
@agile -
@st3fan
Don't agree much: if the system I want to represent is the team work, then the Kanban board shall contain techy things.
And it's not even necessary to do Scrum at all: Kanban cadences for replenishment and the like are enough as well.
And obviously you can hand different Kanban levels (operations, strategy, ...) on different boards.
@agile@AAMfP
That is ok with me, but as described in the blog post above:
The original concept is to visualize/steer the value flow, not the single tasks to achieve the value flow.It is like always a non true/false topic. The blog post was about to have the roll-up of the chores on the customer value item instead of having the value somewhere drilled down in the guts of the chores.
It always depends on the team scope and agile/hybrid setting of the organization, but the best way (in theory and in my opinion) would be value-centric kanban
@agile -
@AAMfP
That is ok with me, but as described in the blog post above:
The original concept is to visualize/steer the value flow, not the single tasks to achieve the value flow.It is like always a non true/false topic. The blog post was about to have the roll-up of the chores on the customer value item instead of having the value somewhere drilled down in the guts of the chores.
It always depends on the team scope and agile/hybrid setting of the organization, but the best way (in theory and in my opinion) would be value-centric kanban
@agile