Troubleshoot and improve your Kanban system. Here are 5 ideas for you to try and use. Download the PDF below. --> allthingsagile.co/post/kanban-practices-and-principles/
Great explanation! I'm a Team Leader with more experience in Scrum and I think Kanban causes a mental gap for many professionals, including for me. I will watch this video more times, but, I understand the context in practice finally now. Thanks for this content.
That's very interesting! I'm glad the explanations helped. I'd love to know more about what you call the mental gap. I'd be happy to make further videos addressing them.
I have a question for you. I just started working for a new company (8 days ago). They are using JIRA to keep a list of all their projects and track to a completion date. They do not use Agile (i think waterfall). They do not want to use agile. They are not recording tasks. They do not have employees assigned to tasks. They are asking me "How can we use JIRA more effectively?" i'm not sure where to start. What are your thoughts? Any suggestions?
Hey @Hubbs3of6 that's quite a situation, but you are not alone. Not only people think tools themselves do the job (which they don't), but Jira in itself started as a mere ticketing system. So, without magic wand solutions, I think some good clues are hiding in what you mentioned: I would ask them what they really want Jira to give them? How and why they started with that particular tool? What was their original ambition? Like so, you can understand where they are, leave the "agile talk" aside, and gain a more solid footing on their expectations. Once you have that, I think a good next question for them is "in that context, what does 'more effectively' means?". Maybe they want to be able to get their timesheets straight from it. Maybe use graphs and reports. Maybe have better prioritization. That will open the doors for you to introduce individual practices of Lean and Agile without dogmatism and straight into solving for their needs. I hope this makes sense. Thoughts?
Hi @theagilelifestile, a definition of methodoloy is "a system of methods used in a particular area of study or activity". So indeed you can say Kanban is a methodology. It's common some people call the whole "doing Kanban", practicing it as the "kanban method" and the board and your policies and the work all put together as "the kanban system". The old school kanban most manufacturing uses and based on the Japanese school is sometimes named as an "inventory system". I wouldn't worry much about how people mention it though. Nomenclature can vary in organizations and use as well. I hope this helps!
Troubleshoot and improve your Kanban system. Here are 5 ideas for you to try and use.
Download the PDF below.
--> allthingsagile.co/post/kanban-practices-and-principles/
Great stuff, thank you for emphasizing simplicity
Thanks for the video. Clear and easy to understand.
Glad it was helpful!
Great explanation!
I'm a Team Leader with more experience in Scrum and I think Kanban causes a mental gap for many professionals, including for me.
I will watch this video more times, but, I understand the context in practice finally now.
Thanks for this content.
That's very interesting! I'm glad the explanations helped. I'd love to know more about what you call the mental gap. I'd be happy to make further videos addressing them.
Very nice and easily explained. Appreciate for sharing these videos. Thanks
Thanks. I'm glad it was helpful!
I have a question for you. I just started working for a new company (8 days ago). They are using JIRA to keep a list of all their projects and track to a completion date. They do not use Agile (i think waterfall). They do not want to use agile. They are not recording tasks. They do not have employees assigned to tasks. They are asking me "How can we use JIRA more effectively?" i'm not sure where to start. What are your thoughts? Any suggestions?
Hey @Hubbs3of6 that's quite a situation, but you are not alone. Not only people think tools themselves do the job (which they don't), but Jira in itself started as a mere ticketing system.
So, without magic wand solutions, I think some good clues are hiding in what you mentioned: I would ask them what they really want Jira to give them? How and why they started with that particular tool? What was their original ambition?
Like so, you can understand where they are, leave the "agile talk" aside, and gain a more solid footing on their expectations.
Once you have that, I think a good next question for them is "in that context, what does 'more effectively' means?". Maybe they want to be able to get their timesheets straight from it. Maybe use graphs and reports. Maybe have better prioritization.
That will open the doors for you to introduce individual practices of Lean and Agile without dogmatism and straight into solving for their needs.
I hope this makes sense.
Thoughts?
@@AllThingsAgile Thank you. This is helpful. Wish me luck.
@@Hubbs3of6 I'd love to hear from you in a little bit, once you try some of your ideas!
Is Kanban a methodology?
Hi @theagilelifestile, a definition of methodoloy is "a system of methods used in a particular area of study or activity".
So indeed you can say Kanban is a methodology.
It's common some people call the whole "doing Kanban", practicing it as the "kanban method" and the board and your policies and the work all put together as "the kanban system".
The old school kanban most manufacturing uses and based on the Japanese school is sometimes named as an "inventory system".
I wouldn't worry much about how people mention it though. Nomenclature can vary in organizations and use as well.
I hope this helps!