This video is very helpful, thank you Daria. I was watching while taking a look at my teams sprint report and definitely see room for improvement. Looking forward to some powerful questions we can ask but this video was great❤. Thank you, thank you
How to do the calc between Items committed vs Items completed vs Items not completed vs Items removed from the sprint? Say for ex: if committed is 60 and completed is 50, from where i need to match the remaining 10 story points?
I hope this video was helpful. 📌 Cover the essential functionality you need to know as a non-admin Jira user with my course ➡ store.scrummastered.com/products/jira-for-scrum-masters-and-agile-teams 📖 If you need support and guidance on your professional journey, check out my guides and templates: store.scrummastered.com/collections/all 📩 Subscribe to my newsletter to get updates on new stuff and special offers: scrummastered.com/free-downloads/
First of all, thank you for all you doing. I am new to Jira and following your class is very difficult as for example I can't find most links..the UI is constantly changing. It's just sad. Different versions by Jira almost every month its hard to catch u
Yes, they keep changing, so even if the video is just a few months old, it may no longer look the same. But I think the main functionality is about the same.
Can you do a detailed video, as soon as possible if possible, taking all the job titles I am going to mention here and review them, explaining which will transfer over to SM but most importantly go over a few 2-3 job postings for each position and see what duties are important that will transfer to SM. And how to list it in a resume and what to mention during a SM interview etc. I don't think you or anyone done this before so it would be a special treat for all the subscribers . job titles to review thoroughly, 1. Product analyst 2. Product designer 3. Product developer 4. Product development analyst 5. Product development manager 6. Product director 7. Product lead 8. Product leader 9. Product marketing 10. Product marketing manager 11. Product policy managers 12. Product purchasing coordinator 13. Product support 14. Product support associate 15. Product specialist. (I can't think of anything but except everything I said in the beginning. By when do you think you can make an hour or so video covering this topic. It took me months to collect these job titles. Now I want to challenge you to review each title plus 2-3 postings and see if you find any similarities to SM and etc) feel free to talk about PO. Wouldn't be a bad thing to hear about that either . I am unemployed and i am going to apply to all SM positions sometime this summer or fall in September. Just in case something goes wrong. I want to have a backup plan and that's where this video will come in handy for that backup plan
I always “scold” team members when they call stories “tickets.” They are stories! Now, I have an influencer calling them tickets. Should I join the club or keep strong?😆
@@parris05 because ticket give me feel that this is some kind of bugs for. Which ticket raise 😁 and story means task which we need to plan and implement
This video is very helpful, thank you Daria. I was watching while taking a look at my teams sprint report and definitely see room for improvement. Looking forward to some powerful questions we can ask but this video was great❤. Thank you, thank you
Thank you for watching!
How to do the calc between Items committed vs Items completed vs Items not completed vs Items removed from the sprint? Say for ex: if committed is 60 and completed is 50, from where i need to match the remaining 10 story points?
Love your videos
@sa-pg6or, thank you for watching!
I hope this video was helpful.
📌 Cover the essential functionality you need to know as a non-admin Jira user with my course ➡ store.scrummastered.com/products/jira-for-scrum-masters-and-agile-teams
📖 If you need support and guidance on your professional journey, check out my guides and templates: store.scrummastered.com/collections/all
📩 Subscribe to my newsletter to get updates on new stuff and special offers:
scrummastered.com/free-downloads/
First of all, thank you for all you doing.
I am new to Jira and following your class is very difficult as for example I can't find most links..the UI is constantly changing.
It's just sad. Different versions by Jira almost every month its hard to catch u
Yes, they keep changing, so even if the video is just a few months old, it may no longer look the same. But I think the main functionality is about the same.
Can you do a detailed video, as soon as possible if possible, taking all the job titles I am going to mention here and review them, explaining which will transfer over to SM but most importantly go over a few 2-3 job postings for each position and see what duties are important that will transfer to SM. And how to list it in a resume and what to mention during a SM interview etc. I don't think you or anyone done this before so it would be a special treat for all the subscribers . job titles to review thoroughly, 1. Product analyst 2. Product designer 3. Product developer 4. Product development analyst 5. Product development manager 6. Product director 7. Product lead 8. Product leader 9. Product marketing 10. Product marketing manager 11. Product policy managers 12. Product purchasing coordinator 13. Product support 14. Product support associate 15. Product specialist. (I can't think of anything but except everything I said in the beginning. By when do you think you can make an hour or so video covering this topic. It took me months to collect these job titles. Now I want to challenge you to review each title plus 2-3 postings and see if you find any similarities to SM and etc) feel free to talk about PO. Wouldn't be a bad thing to hear about that either . I am unemployed and i am going to apply to all SM positions sometime this summer or fall in September. Just in case something goes wrong. I want to have a backup plan and that's where this video will come in handy for that backup plan
Hey! Thank you for the super chat! @going-remote2passport-bro
Let me read through your question and I can do a few shorts for you
@@ScrumMastered its kind of long can you do a lengthy video on it
I always “scold” team members when they call stories “tickets.” They are stories! Now, I have an influencer calling them tickets. Should I join the club or keep strong?😆
Is there a reason why you don’t like stories being called tickets? Just curious.
@@parris05 because ticket give me feel that this is some kind of bugs for. Which ticket raise 😁 and story means task which we need to plan and implement
@@parris05 what Mayank says below
How do you call technical work items and tasks then?
I wouldn't call myself an influencer... I'm a Scrum Trainer :)