Please note. In this video, I incorrectly used the term 'swim lanes' for the columns of a scrumban board. Swim Lanes are themed horizontal paths we use to group tasks that progress across the board. They are similar to work streams in predictive project management. As far as I know, there is no jargon name for the columns, they are just columns. I'm sorry for the error. I learned or was taught this incorrectly a long time ago!
Great video. One small point: the columns on an agile board are not swim lanes; swim lanes are rows. (Most boards don't have a swim lane - or have exactly one - depending on how you look at it.)
I can see pros and cons to this approach (more informed choices in moving -or not- a task to the sprint backlog vs abortive requirements gathering work on tasks that never make it to a sprint). This is a great example of an organization finding a tweak to a process that obviously works well for you, in your context.
I a afraid I don't have anything specific to Scrumban, but take a look at How to Do Risk Management in Agile Projects - ruclips.net/video/f3SY_lM7Hhs/видео.html
Hi Mike, First of all,many thanks for share valuable knowledge. Let me I have a question, I am working as Supply Chain Manager. So,how I can implement scumban methodology in my job processes ? If you give me some advice I would have apply especially to purchasing.
I suspect pure Kanban may be more appropriate to your environment - as you will have to deal with a continuous flow of requirements. However, you may decide to backlog all new requirements and draw a subset into your agenda each we, fortnight, or month. Whichever you go for, your key task is to define the stages that you will represent as columns in your Kanban or Scrumban board. From there, each procurement will follow the sequence. See also my video on Kanban: ruclips.net/video/W8dKoRjFvTY/видео.html
Please note. In this video, I incorrectly used the term 'swim lanes' for the columns of a scrumban board. Swim Lanes are themed horizontal paths we use to group tasks that progress across the board. They are similar to work streams in predictive project management. As far as I know, there is no jargon name for the columns, they are just columns. I'm sorry for the error. I learned or was taught this incorrectly a long time ago!
Great video. One small point: the columns on an agile board are not swim lanes; swim lanes are rows. (Most boards don't have a swim lane - or have exactly one - depending on how you look at it.)
Thank you, that's helpful. I clearly misunderstood (or was mis-taught) quite a long time ago.
that's correct. columns go top to bottom and swimlanes go left to right
At my workplace, we usually gather the requirements before moving a task from backlog to sprint backlog, hence specify/specified columns aren't needed
I can see pros and cons to this approach (more informed choices in moving -or not- a task to the sprint backlog vs abortive requirements gathering work on tasks that never make it to a sprint). This is a great example of an organization finding a tweak to a process that obviously works well for you, in your context.
Sir could you please share any article link where I can learn about "Risk management with Scrumban"
I a afraid I don't have anything specific to Scrumban, but take a look at How to Do Risk Management in Agile Projects - ruclips.net/video/f3SY_lM7Hhs/видео.html
I really like the agile concept, so I have been using agile project management software to manage my life and work. I recommend looking at Zen Tao.
Not very subtle my friend, but I'll let your comment stand as ZenTao has a free tier.
@@Onlinepmcourses Thank you very much. I also sincerely invite you to test this software.
@@philip7184 Thanks - maybe will
It is not a methodology, it is a framework
Fair point.
Hi Mike,
First of all,many thanks for share valuable knowledge.
Let me I have a question,
I am working as Supply Chain Manager.
So,how I can implement scumban methodology in my job processes ?
If you give me some advice I would have apply especially to purchasing.
I suspect pure Kanban may be more appropriate to your environment - as you will have to deal with a continuous flow of requirements. However, you may decide to backlog all new requirements and draw a subset into your agenda each we, fortnight, or month. Whichever you go for, your key task is to define the stages that you will represent as columns in your Kanban or Scrumban board. From there, each procurement will follow the sequence. See also my video on Kanban: ruclips.net/video/W8dKoRjFvTY/видео.html
@@Onlinepmcourses many thanks for valuable advice.
@@mertser65 My pleasure
Great video!
Glad you enjoyed it
Scrum lacks flexibility, kanban lacks structure for projects, I am a fan of scrumban.
Hybrid vigor