I love that video. It go straight to the topic with good and clear explanations and scenarios. I watched it many time for my pre. Still waiting for Episode 2 (since this is Episode 1).
This video was very informative. I’m in the process of applying for my fury scrum master job and this video is very helpful. Please keep making more like this.
The best and most informative video I’ve seen so far. Definitely deserves more attention and likes/subscribers. Please keep them coming, you’re doing an amazing job
Ok first of all where is the scope creep coming from. If you are working with a PO or a BA or Client representatives. In a typical scrum framework organization if the scope creep is coming from the PO, so having a working agreement with the PO before the start of the sprint or project where you explain to him this thing that scope creep must not happen unless it is absolutely critical for the survival of the team. If it does happen than bring it up in a meeting with the team and let them decide what they want to do because they are the ones who have to do the work. To avoid it work with the PO and communicate your pain and gain to make sure it does not happen again.
Managing dependencies between teams can be done through JIRA where you show the team dependencies with your project and unless those dependencies are resolved there sprint cannot be finished. If not that way than communicating with the scrum master from other team and quantifying the pains of not having the dependency met for your team and explaining to him the dependency and work with that or bring it up in scrum of scrums. Generally it is recommended to finish all dependencies before the start of the sprint because it can really delay the sprint goal sometimes and team can be forced to extend the sprint time from 2 weeks to 3 weeks or 4 weeks.
@@agilecore7289 Thank you for getting back. At 7.45 is Q3 (you have completed the work 2 days before sprint end and PO wants to put in more work). Subsequently you talk about how to handle scope creep and removing requirements before adding. But specifically wrt the scenario in Q3, the work is already completed, so I assume that there is no requirement to be removed before reviewing the new requirement from PO)?
So, this is good sign of weak refinement and weak sprint planning because this means that we are not doing our refinement properly and our sprint planning is weak. So, bring this up in the next retro and have discussions around it. Now, since we are done early and the PO wants to push more work, i would push back against that and keep the 2 days for bug fixes or pair programmimg exercises or any thing that might pop up during testing or maybe handling some technical debt instead of taking on more work. I will explain better in my live seasion. REPLY
Thank you, glad you find value. You have to be creative. Email me at cmalik@frontendcp.com and let's get on a call if you need help with job search or on job.
As a scrum master you are proposing new structure with scrum to follow, you have multiple features to be done every feature has a squard of 4 to 5 people, you have product managers and tech team (engineering manager and CTO) as per these role how you introduce the new scrum in the company who do what? In SOS case who is the conducting and owner of the scrum of scrum? What we need from tech team?
For the answer to the first question: Design a presentation and highlight the new process and try to educate the team on the value the new scrum process will bring as compared to the existing process. Make the presentation to be 45 minutes and than leave at least 15 to 30 minutes for questions and make sure the team understands the new process and are on board with the scrum process and understand it very well. For the second question: Generally Senior scrum masters are the owners but every team's SOS is different because in many teams even architects and designers join SOS. I have also seen senior product owners conducting SOS in many teams. It really depends. What do you need from tech team in what context? Please explain the question more clearly.
For Q3.. work is already done and PO wants put more work.. how can you remove some work from the sprint which is already completed to accommodate the new work.. I am confused here
If the work is already completed than there is no need to remove anything. If you are in the middle of the sprint amd there is work left over that is when you remove things and replace them with the incoming work.
There are enough videos on the channel answering that question. If you listen to the video closely you should be make an example yourself. I will again answer the question in the next videos.
Great, work together with the stakeholder, management and try to understand what roles are needed. Do not try to be perfect in the first sprint. Learn as you go and stay flexible.
Test whatever you have on hand and push that out. While doing this communicate with the stakeholder what is going on at all times. Discuss with the team what is the best way forward and most importantly bring this up in the retrospective and discuss the reason behind it so that it never happens again.
![[UNCUT] The Loyal Pin ปิ่นภักดิ์ EP.15 (3/4)](http://i.ytimg.com/vi/IVwR87OH0_A/mqdefault.jpg)
I think you need to create more videos like this, the Best one.
More coming soon.
I love that video. It go straight to the topic with good and clear explanations and scenarios. I watched it many time for my pre. Still waiting for Episode 2 (since this is Episode 1).
Thank you.
one of the best video I have seen till now
Thank you so much for watching. Glad you like it.
Your voice catches my attention and makes me to listen till last minute of the conversation.......
Thank you.
This video was very informative. I’m in the process of applying for my fury scrum master job and this video is very helpful. Please keep making more like this.
Glad it was helpful!
Very very helpful for situational questions. Thanks. Please keep more videos coming!!!
More to come!
The best and most informative video I’ve seen so far. Definitely deserves more attention and likes/subscribers. Please keep them coming, you’re doing an amazing job
Thank you! Will do!
Well explained in depth. The content is quite well detailed. A good tool for beginners
Glad it was helpful!
This video is really very helpful. Thank you so much for such an informative video. Looking forward for more such videos.
Glad it was helpful!
Please make episode 2 of this video.. Brilliant episode 1
Thank you.
Amazing video!!! Please do part 2
Thank you so much.
Thank you for this video awesomeness
Thank you for watching.
I lovvvveeee this video.....Explained perfectly. Thank you so much!
You're so welcome! Glad it was helpful.
Very useful and informative content. Thanks alot.
Thank you.
Thank you so much . This has been so informative and useful.. can’t wait to apply your content when necessary :)
Glad you find value. Thank you.
Excellent Description. Please do some video for Estimation of story point with respect to complexity/ risk/ effort
Coming soon.
Thanks for this video, it was well explained
Thanks for watching!
Awesome content.very uefull
Glad it was helpful!
Nice stuff buddy .congratulation for being 1000 family on YT .I am 1000th person 👫 .
Thank you so much Meraj, I very much appreciate you.
Thank you so much. It helps a lot.
More interviews please! This is great!
Thank you.
Thanks for making helpful video]]]] pl do part 2
Ok. it is coming.
How do you avoid scope creep? How do you manage dependencies between teams?
Ok first of all where is the scope creep coming from. If you are working with a PO or a BA or Client representatives. In a typical scrum framework organization if the scope creep is coming from the PO, so having a working agreement with the PO before the start of the sprint or project where you explain to him this thing that scope creep must not happen unless it is absolutely critical for the survival of the team. If it does happen than bring it up in a meeting with the team and let them decide what they want to do because they are the ones who have to do the work. To avoid it work with the PO and communicate your pain and gain to make sure it does not happen again.
Managing dependencies between teams can be done through JIRA where you show the team dependencies with your project and unless those dependencies are resolved there sprint cannot be finished. If not that way than communicating with the scrum master from other team and quantifying the pains of not having the dependency met for your team and explaining to him the dependency and work with that or bring it up in scrum of scrums. Generally it is recommended to finish all dependencies before the start of the sprint because it can really delay the sprint goal sometimes and team can be forced to extend the sprint time from 2 weeks to 3 weeks or 4 weeks.
Really grateful
Thank you !
You're most welcome!
One of the best I have come across. Keep doing a fantastic job.
Thank you so much 😀
This video is very helpful. Can you please send the link for Episode-2
Yes, it is live now.
Thank you for making a masterpiece like this.I appreciate your efforts 👍 Kindly let me know where I can find Episode 2?
It is on the way. Thank you for watching.
I truly love this video I have learned a lot of new things and they way he breaks down the example is just great!! Thank you so much for this!!
Glad you find value. Thank you so much for watching.
RE Q3. Since the work is already completed, what is there to remove before assessing the new requirement from PO?
Thank you for the question. Can you explain a bit more what you mean. I do not think i understood your question well.
@@agilecore7289 Thank you for getting back. At 7.45 is Q3 (you have completed the work 2 days before sprint end and PO wants to put in more work). Subsequently you talk about how to handle scope creep and removing requirements before adding. But specifically wrt the scenario in Q3, the work is already completed, so I assume that there is no requirement to be removed before reviewing the new requirement from PO)?
So, this is good sign of weak refinement and weak sprint planning because this means that we are not doing our refinement properly and our sprint planning is weak. So, bring this up in the next retro and have discussions around it. Now, since we are done early and the PO wants to push more work, i would push back against that and keep the 2 days for bug fixes or pair programmimg exercises or any thing that might pop up during testing or maybe handling some technical debt instead of taking on more work. I will explain better in my live seasion.
REPLY
Wow thank you so much for these questions! I do have one question, who would a person answer with no experience in scrum answer the last questions?
Thank you, glad you find value. You have to be creative. Email me at cmalik@frontendcp.com and let's get on a call if you need help with job search or on job.
As a scrum master you are proposing new structure with scrum to follow, you have multiple features to be done every feature has a squard of 4 to 5 people, you have product managers and tech team (engineering manager and CTO) as per these role how you introduce the new scrum in the company who do what?
In SOS case who is the conducting and owner of the scrum of scrum?
What we need from tech team?
For the answer to the first question: Design a presentation and highlight the new process and try to educate the team on the value the new scrum process will bring as compared to the existing process. Make the presentation to be 45 minutes and than leave at least 15 to 30 minutes for questions and make sure the team understands the new process and are on board with the scrum process and understand it very well.
For the second question: Generally Senior scrum masters are the owners but every team's SOS is different because in many teams even architects and designers join SOS. I have also seen senior product owners conducting SOS in many teams. It really depends.
What do you need from tech team in what context? Please explain the question more clearly.
For Q3.. work is already done and PO wants put more work.. how can you remove some work from the sprint which is already completed to accommodate the new work.. I am confused here
If the work is already completed than there is no need to remove anything. If you are in the middle of the sprint amd there is work left over that is when you remove things and replace them with the incoming work.
Please finish and upload Part 2
thank you
Yes, it is coming. Thank you.
Q7 you didn’t give an example of the recent sprint planning. You only mentioned the values.
There are enough videos on the channel answering that question. If you listen to the video closely you should be make an example yourself. I will again answer the question in the next videos.
Q4- What if there is no existing scrum team and you will be the scrum master who need to start it from scratch
Great, work together with the stakeholder, management and try to understand what roles are needed. Do not try to be perfect in the first sprint. Learn as you go and stay flexible.
howz productivity mesaured in a scrum team? ques 9. how do Scrum master knows that productivity has gone down in a team?
Will answer in the next video.
Fantastic
Thank you.
What if I don’t have experience? I have experience in management in hospitality
Sure, please email me at cmalik@frontendcp.com and i can help more.
"Smell blood" 🤣🤣🤣
Lol
Thank you so much for this. This is extremely insightful and helpful. How many questions are generally asked during an interview?
About 8 to 9 questions depending on the person.
@@agilecore7289 thank you so much!
What will be in working agrément for scrum master in général?
Watch the working agreement video on the channel.
Can you please post more !!!
Yes, more coming.
Great
Thanks.
If development team delay in delivery of code by 3 days to testing team
How to handle this situation
Test whatever you have on hand and push that out. While doing this communicate with the stakeholder what is going on at all times. Discuss with the team what is the best way forward and most importantly bring this up in the retrospective and discuss the reason behind it so that it never happens again.