Jira Scrum vs Kanban Project Workflows Explained!
Вставка
- Опубліковано 15 чер 2023
- What is the difference between Scrum and Kanban workflows inside of Jira?
If you have struggled to understand the difference between these two very popular project templates, this video was created to guide you through the process of picking the right type for you and your team.
If you are enjoying the content and want to help support the channel, check out the links down below!
Udemy - Jira Fundamentals Course - www.udemy.com/course/jira-clo...
Apetech Merch Store - my-store-dc4aec.creator-sprin...
Subscribe to The Jira Life - / @thejiralife
And don’t forget to check out channel sponsors down below!
#workflows #workflow #scrum #kanban
Link to my other Atlassian Jira videos
• Jira Tutorials
Link to my Atlassian Live Streams:
• Jira Community Live St...
Link to Atlassian's Jira products:
www.atlassian.com/software
Link to my Fiverr profile:
www.fiverr.com/alexortiz924?u...
Link to my Upwork profile:
www.upwork.com/freelancers/~0...
Thanks, very useful
Glad to hear that!
Back logs are 'Wishlist' not necessarily committed to deliver
I see this often in dual-track agile setups. Or how would you approach this?
We use automations to move issues from discovery (kanban) to delivery (scrum) for example.
But you never showed how you imbedded the new scum within an existing Kahban project. What are the steps to add the new scrum board? New subbie 💪🏽
Great video! What’s the best practices for filtering both the scrum and kanban boards under the same project, since all the issues will all be mixed together without doing so, thanks!
What exactly are you trying to filter. An issue is still an issue. Nothing about it being in Kanban or Scrum makes it unique (other than the statuses that you start off with).
@@ApetechTechTutorials We have 2 different teams working under the same project, one on Scrum and the other on Kanban board. Just wondering what’s the best way to differentiate issues between these two teams and showing only what they need to see in their own board.
@@coldeyes168 Ahh, that makes more sense. I typically tell teams to use either component field or the fix version field. If you are on Jira Premium, you can use the Team field. My preference to to make sure you use a field that can only have 1 value that way you can ensure that the issue only shows up in one board.
@@ApetechTechTutorials Didn’t realized there’s a Team field available, we’re on Jira Premium and this should come in handy, thanks for your helpful insights!
@@coldeyes168 Yes, you'll want to create a Shared Team under your Plans section up in the Navigation Bar.
legend