I appreciate your explanations and examples! I've been very lucky over the last 2 sprints. My developers were hungry for work, and I and another scrum master cautioned them about the load they wanted to take based on their capacity, especially with people taking time off. However, I don't know how they do it, but they clear the sprint backlog, and if there's a story or two that carries over, it's because of something technical, like an unplanned update, that happens. And then when it comes to closing the Sprint, my scrum master trainer has made it very explicit that we do it as manually as possible so Jira doesn't do the automatic stuff it likes to do.
Thank you 🥰 I found your channel this week and I am enjoying a lot your content! It is helping me a lot to learn more about the agile world from the practical perspective!
Can you do a tutorial on how you use Jira app and how it helps you and any basics or tips? Also a new intro song would be nice 👍 sounds kind is outdated
Thanks for your explanation. The 2nd C is conversation, shouldn't that happen at the retro to find out reasons for not completing before moving it to product backlog? secondly, what's the whole point of actionable item and assigning it if we are just going to move it to product backlog?
1- Some columns on my active board, I can't pull issues or glitches under them (I have previously worked on the workflow and it was working fine, not sure if someone from the team made any changes). How can add "Categories" on the workflow 2- Jira stories can be moved one status forward only (on my active board). Please can you advise why? 3- How can modifying the workflow remove some of the sprint issues from the current active sprint? 4- How can one track and know in how many sprints the story was built in?
I appreciate your explanations and examples! I've been very lucky over the last 2 sprints. My developers were hungry for work, and I and another scrum master cautioned them about the load they wanted to take based on their capacity, especially with people taking time off. However, I don't know how they do it, but they clear the sprint backlog, and if there's a story or two that carries over, it's because of something technical, like an unplanned update, that happens. And then when it comes to closing the Sprint, my scrum master trainer has made it very explicit that we do it as manually as possible so Jira doesn't do the automatic stuff it likes to do.
Exactly. What is highly important is that 3Cs. Thank you very much for adding your voice Joe 😊
Thank you 🥰 I found your channel this week and I am enjoying a lot your content! It is helping me a lot to learn more about the agile world from the practical perspective!
You're so clued up Caren...well done you!
Very clear and helpful. Thank you.
You are welcome 😊
Thank you. This is really good info
You are very welcome 😊
Can you do a tutorial on how you use Jira app and how it helps you and any basics or tips? Also a new intro song would be nice 👍 sounds kind is outdated
Thanks for your explanation. The 2nd C is conversation, shouldn't that happen at the retro to find out reasons for not completing before moving it to product backlog? secondly, what's the whole point of actionable item and assigning it if we are just going to move it to product backlog?
1- Some columns on my active board, I can't pull issues or glitches under them (I have previously worked on the workflow and it was working fine, not sure if someone from the team made any changes). How can add "Categories" on the workflow
2- Jira stories can be moved one status forward only (on my active board). Please can you advise why?
3- How can modifying the workflow remove some of the sprint issues from the current active sprint?
4- How can one track and know in how many sprints the story was built in?
How have you managed spilled-over user stories? Please share your experience. Thank you so much!
What about the 3rd C which talks about the size? So will you have to reestimate or repoint?
3rd C talks about Confirmation which is Acceptance Criteria.