@@MyGodisfaithful4ever Hi, I don’t know if it applies to the scrum boards but I use it for the kanban board. It’s an admin function that you turn on called days in column. The benefit of this feature is it tells you how many days for example a story has been in progress. Some people don’t realize that kanban should be time boxed as well meaning it’s generally not OK for something to in progress for 36 days if you’re not actually working on it. Meaning work still needs to get done in a timely manner. I also recommend enabling the product backlog for kanban board’s. The benefit is you don’t have to try and organize your work in the To Do column and it allows you to create Epics so you can organize and prioritize your work.
We are a pretty large team; so, we split into 2-3 groups of 5-6 people using virtual breakout rooms once in a while. We still talk about our status updates but in a smaller group which often leads to more fruitful discussions. As a Scrum Master, I can jump between the groups and if I detect a topic that requires an entire team, I normally take it our retrospectives.
I would love to see a "Your Daily Scrum" around the sprint goal. Most times there are multiple smaller "goals" and not just one overarching theme. For example, within a 2 week sprint I could have a user story to add feature A and another story to add feature B, that share no commonality. I see companies get around this by either just having multiple sprint goals and/or a long sentence with a lot of commas :). Curious to hear your guys thoughts.
I am based in South Africa and will be working remotely as a Scrum Master at month end. How do you conduct a daily meeting if your developers and team members are also remote workers? What are the major drawbacks or challenges facing us with the daily meeting?
I agree that the 3 questions can sound robotic however we do it we answer the questions as a conversation and focusing on the sprint goal. This way sounds more natural
The team I'm with right now has had great success with walking down the board from top to bottom discussing each item including current progress and what is needed to move it forward and if anything is holding up progress. I agree focus on the Sprint Goal is an easy one to forget but something we should find away to make it a focal point. Sprint Goal: This is the way!
I have a question for both Scrum Minds. Requesting you to answer if you had came across such a situation. As a SM, have you ever done wrong something and you only later figured out what’s wrong? Thanks in advance Ryan and Todd
Hi @@osnyzinho , I do not know your context and reason for why your team cannot do the daily scrum in 15 mins but you can try to do a workshop with the team to make them understand the purpose of scrum events (specially Daily Scrum in your case). In the workshop, I generally will ask the team members to first put their thoughts on stickies around the daily scrum to point what they do in daily scrum and for what purpose. Then will move on to have discussion about the purpose of daily scrum per the guide which is for the developers to plan their day and why everything they do which does not help in planning (not solutioning) should move out of the daily scrum. Hope this may help you and your team together to understand the purpose of daily scrum 🙏🏻
You can use the 3 questions if they help your team make a plan for the next 24-hours to amake progress towards their Sprint Goal. We've found that alternatives can sometimes work a little bit better. :-)
@@AgileforHumans I agree to work towards Sprint Goal. I haven't tried the way you mentioned in your video and I'm not sure I got the way you mentioned. Checking the PBI during dailies? Shouldn't it happen during planning or refinement sessions? Also dailies are for developers and aren't the good opportunities for them to bring up problems and SM can try to find ways to remove impediments that cause problems? The way you said does not have that function to me.Maybe you can conclude it and write that on the screen at the end of each episode? I don't know 😕 ...it's just a suggestion...it's an awesome video.:-).
We prefer Professional Scrum with Kanban if you are looking to bring Kanban practices into a Scrum Team. If you are looking to do Kanban on it's own, then prokanban.org is a great place to start.
Thanks Brandon! We are working on the right balance between fun and informational. We are also considering adding in chapters (timestamps) so that people can skip around. We appreciate the feedback.
But if you skip the filler you miss TLC and then it's all work and no play... Same applies to my daily scrums, always try to kick off with something funny to get people in the right mood and it's not just people saying " done this, working on this, no blockers", that's just boring and doesn't really add to the spirit of collaboration and knowledge sharing
What is your favorite way to facilitate the Daily Scrum? Leave us a comment and help us all level up our Daily Scrum facilitation skills.
The song is now stuck in my head too. Thanks! lol
One of the things I like about Jira is the days in column feature.
Hello, how do I view this feature? Thanks
@@MyGodisfaithful4ever Hi, I don’t know if it applies to the scrum boards but I use it for the kanban board. It’s an admin function that you turn on called days in column. The benefit of this feature is it tells you how many days for example a story has been in progress. Some people don’t realize that kanban should be time boxed as well meaning it’s generally not OK for something to in progress for 36 days if you’re not actually working on it. Meaning work still needs to get done in a timely manner. I also recommend enabling the product backlog for kanban board’s. The benefit is you don’t have to try and organize your work in the To Do column and it allows you to create Epics so you can organize and prioritize your work.
@@laverndowsley8850 Thank you! I’ve found it on the Jira scrum board.
We are a pretty large team; so, we split into 2-3 groups of 5-6 people using virtual breakout rooms once in a while. We still talk about our status updates but in a smaller group which often leads to more fruitful discussions. As a Scrum Master, I can jump between the groups and if I detect a topic that requires an entire team, I normally take it our retrospectives.
I would love to see a "Your Daily Scrum" around the sprint goal. Most times there are multiple smaller "goals" and not just one overarching theme. For example, within a 2 week sprint I could have a user story to add feature A and another story to add feature B, that share no commonality. I see companies get around this by either just having multiple sprint goals and/or a long sentence with a lot of commas :). Curious to hear your guys thoughts.
Great idea! We've added this idea to the backlog. Keep your eyes open for a future episode covering the Sprint Goal.
The TLC thing made my day! ✌🏻
Very interested to hear more on ideas on what liberating structure would help with daily scrum. Thanks!
Thanks Guys! Love the Banana peel. Good shift to the item aging - puts the focus on the value item and teamwork, and the sprint goal.
Our pleasure! Thanks for posing the question, Jodie!
I am based in South Africa and will be working remotely as a Scrum Master at month end. How do you conduct a daily meeting if your developers and team members are also remote workers? What are the major drawbacks or challenges facing us with the daily meeting?
What is the value of talking about already done work (what I did yesterday) in stand ups?
I agree that the 3 questions can sound robotic however we do it we answer the questions as a conversation and focusing on the sprint goal. This way sounds more natural
That's awesome! How else do you facilitate the Daily Scrum?
The team I'm with right now has had great success with walking down the board from top to bottom discussing each item including current progress and what is needed to move it forward and if anything is holding up progress.
I agree focus on the Sprint Goal is an easy one to forget but something we should find away to make it a focal point. Sprint Goal: This is the way!
Walking the work is another excellent practice. Thanks for sharing, Christoper!
Great episode! 👍🏼.. "Regardless of Practice FOCUS on the Sprint Goal! "
Q. Is there something called "spillover" of items to next Sprint in Scrum?
I have a question for both Scrum Minds. Requesting you to answer if you had came across such a situation.
As a SM, have you ever done wrong something and you only later figured out what’s wrong?
Thanks in advance Ryan and Todd
Hello! Any tip of how to teach the developers that the daily must be finished in 15min or less?
A stopwatch?
@@AgileforHumans thanks for the answer! But I wonder: a stopwatch is not too much predictive ? I mean does not sounds to aggressive?
Hi @@osnyzinho , I do not know your context and reason for why your team cannot do the daily scrum in 15 mins but you can try to do a workshop with the team to make them understand the purpose of scrum events (specially Daily Scrum in your case).
In the workshop, I generally will ask the team members to first put their thoughts on stickies around the daily scrum to point what they do in daily scrum and for what purpose. Then will move on to have discussion about the purpose of daily scrum per the guide which is for the developers to plan their day and why everything they do which does not help in planning (not solutioning) should move out of the daily scrum.
Hope this may help you and your team together to understand the purpose of daily scrum 🙏🏻
Even they are removed, it doesn't mean they can't be used for dailies. As long as daily goes on well with developers.
You can use the 3 questions if they help your team make a plan for the next 24-hours to amake progress towards their Sprint Goal. We've found that alternatives can sometimes work a little bit better. :-)
@@AgileforHumans I agree to work towards Sprint Goal. I haven't tried the way you mentioned in your video and I'm not sure I got the way you mentioned. Checking the PBI during dailies? Shouldn't it happen during planning or refinement sessions? Also dailies are for developers and aren't the good opportunities for them to bring up problems and SM can try to find ways to remove impediments that cause problems? The way you said does not have that function to me.Maybe you can conclude it and write that on the screen at the end of each episode? I don't know 😕 ...it's just a suggestion...it's an awesome video.:-).
Ryan and Todd, can it be Scrumban or just Kanban? Do they both have their place?
We prefer Professional Scrum with Kanban if you are looking to bring Kanban practices into a Scrum Team. If you are looking to do Kanban on it's own, then prokanban.org is a great place to start.
I would love you to cover the topic of integrating Scum/Agile and Security
Don't go chasing waterfalls............... fa la la
Start at 1:54 to skip the filler
Thanks Brandon! We are working on the right balance between fun and informational. We are also considering adding in chapters (timestamps) so that people can skip around. We appreciate the feedback.
But if you skip the filler you miss TLC and then it's all work and no play... Same applies to my daily scrums, always try to kick off with something funny to get people in the right mood and it's not just people saying " done this, working on this, no blockers", that's just boring and doesn't really add to the spirit of collaboration and knowledge sharing
More like 2:45