Extremely happy for you 🙏🏾🙏🏾. Congratulations, you deserve it 🙏🏾🙏🏾. I provide mentorship for new scrum master. You are always welcome to join our paid COP. Email: admin@aishascrumtech.com
Aisha, we really appreciate your videos because they are all very informative. I agree with you because if properly used, the Backlog Refinement could clearly replace Sprint Planning even though all Scrum Events are valuable.
I think for me I will merge the sprint review and retrospective. I feel planning is equally important. Review and retrospective ultimately translate to same thing, yes different stakeholders might attend in the different events but ideally you are reviewing what was done and planning better(lesson learned)
Aisha, thank you for this response. This is a tricky question. My thoughts to this is all the 4 scrum events are important and taking away one event, then we can't be talking of scrum. I would rather look on best ways to manage or run each event to make it interesting for the team to participate. Like you rightly said Backlog refinement is not a ceremony but a continuous process. My opinion. Thinks for advise.
@@AishaTech655 😂😂 Yes most interviewers do insist on certain questions. To the beat of my knowledge I will stick to the Scrum guide as can not deviate from it. It might be to test my knowledge band application of the scrum guide. My thoughts!!😊😊
Oh Lord. So if the required scrum events are 1. Sprint Planning, 2. Daily Standup, 3. Sprint Review and 4. Retrospective, you notice that "backlog refinement" is NOT one of the scrum events you mentioned. In the guide, refinement is "recommended but not required", since it doesn't have to be a meeting. So, it is very odd that you suggest removing a required scrum event with one that was not even given as an option in your introductory statement, and is not a formal event in scrum. Now, let's pretend that you did include backlog refinement as event #5. It is possible to plan stories in the refinement sessions, that is true. But since there is constant change on a scrum team, it is very unsafe to presume that whatever stories were "planned" on last Friday are still valid come the next sprint start on Wednesday. So there is risk in skipping planning due to this alone. Additionally, the team needs to AGREE on the scope within the sprint, and they cannot do that if they don't meet one last time to review and plan and commit. Finally, part of sprint planning is looking at capacity; "Who will be out this sprint? How many days? How many points/stories should we remove from the sprint?" If you skip this step, you are likely to overcommit the team. As a hiring manager and coach, I would never propose dropping an event. Instead, I would expect the SM to say: "Dropping an event is a serious decision and we would need to investigate this. I would want to gather more information, and speak with our coach and my manager first." Then I would want the candidate to ask questions back to me, as the interviewer. "What events do you currently use? What reasons are they giving for wanting to drop an event? Is there an event they think is useless? Have they made suggestions about how I can improve it?" When I see a candidate is too scared to ask questions, and is instead quickly willing to scrap the scrum guide to keep the team happy, without exploring options, I know we are about to have problems.
@@AishaTech655 Aisha I watched and pointed out an issue. Perhaps instead of automatically presuming I did not watch you should pause and consider the constructive input I am giving. I've been hiring, managing and coaching scrum masters for 15+ years. I listened to your argument twice and then responded. It is bad advice. I have had to deal with the consequences of this type of advice before and it creates a mess. But if we focus only on the interview, your recommendation is likely to cause candidates to fail the interview! Scrum clearly states that the required ceremonies are key parts of scrum and if you remove those you are not doing scrum. You are promoting what we call "scrum-but". As in: "we say we do scrum, BUT we dont do planning". This is an anti-pattern.
Question number one is very tricky and the interviewer might ask you the below question ; so I might need to disagree with you . But there won’t be any product to deliver. If the team doesn’t stick to the sprint planning, how would they know what to prioritize based on user stories? If there is no sprint planning, the spring backlog is not enough
The review should involve the scrum team and all stakeholders. Sometimes, you will have to adjust as issues arise, but always ensure your stakeholders are informed🙏🏾🙏🏾🙏🏾
I strongly disagree with your backup argument in response to the first question ;Which of the agile events will you eliminate if given the chance. Stating your response as sprint planing is fine. Arguing that it can be replace by backlog refinement is wrong. Officially backlog refinement is not one of the agile recommended events and it should not be considered as an official event. I will rather do away with retrospective. It is process improvement but can be merged or communicated during other events. Besides, good planning will have a team working agreement that can be updated My take
Sprint planning and backlog refinement of you do the same time it will take more time or at the same time, because if there is the team that needs technical clarification or some thing that the team cannot understand the requirements. So for just an interview you can say this to impress your interviewer, if not this is an anti pattern. I think if the scrum doesn't want first place why do they need to keep in the scrum guide 😂. My opinion this is not good 💡 idea. Have a wonderful day.
Aisha. Thank you for all the knowledge . Can you please start a free whatsapp group for your channel subscribers, where we can share and expand our knowledge under your supervision/ facilitation?
I agree with the Sprint Planning only if we have been doing backlog refinement 😂😂. Could this be one of those tricky questions where they want to make sure we know the importance of all the ceremonies?
ABSOLUTELY and you observed a problem with her answer. She essentially suggested replacing a critical REQUIRED event with one that is NOT a formal scrum event. Bad idea. Were I the interviewer I would hit the buzzer.
Our website is now live:
www.aishatechs.com
Thanks to you content, I got my first Scrum Master gig. Though a contract role, its a foot in the door.
Extremely happy for you 🙏🏾🙏🏾. Congratulations, you deserve it 🙏🏾🙏🏾. I provide mentorship for new scrum master. You are always welcome to join our paid COP. Email: admin@aishascrumtech.com
Congrats. Just be aware that just because someone has a youtube channel does not make them knowledgeable.
Congratulations
How did you do it ?
Aisha, we really appreciate your videos because they are all very informative. I agree with you because if properly used, the Backlog Refinement could clearly replace Sprint Planning even though all Scrum Events are valuable.
Thank you 🙏🏾 🙏🏾🙏🏾
I think for me I will merge the sprint review and retrospective. I feel planning is equally important. Review and retrospective ultimately translate to same thing, yes different stakeholders might attend in the different events but ideally you are reviewing what was done and planning better(lesson learned)
Aisha, thank you for this response. This is a tricky question. My thoughts to this is all the 4 scrum events are important and taking away one event, then we can't be talking of scrum. I would rather look on best ways to manage or run each event to make it interesting for the team to participate. Like you rightly said Backlog refinement is not a ceremony but a continuous process. My opinion. Thinks for advise.
Totally agree with you, but if the interviewer insists which one will you eliminate 😬
@@AishaTech655 😂😂 Yes most interviewers do insist on certain questions. To the beat of my knowledge I will stick to the Scrum guide as can not deviate from it. It might be to test my knowledge band application of the scrum guide. My thoughts!!😊😊
*** To the best of my knowledge!!
I would rather not eliminate any of the events and stick to the scrum guide.
Yes that a safe choice 🙏🏾🙏🏾
If you smile through your interview like Aisha, there's no way you won't get the job...always love the smile
Thank you 🙏🏾, I appreciate it 😍
It’s actually quite repulsive/fake smile. There’s no need to put a smile when it’s not necessary…
But it’s very american so I understand the reason 😊
Thank you Aisha, I like your style of teaching.
Thank you 🙏🏾 🙏🏾🙏🏾
Thank you Aisha, your videos always makes me smile, your personality is top notch.
Thank you 🙏🏾, I appreciate it.
Aisha, I really appreciate your videos. They are so detailed and informative. I thoroughly enjoy your content.
Thank you 🙏🏾, I appreciate your feedback 🙏🏾🙏🏾
Hello Aisha, Thank you so much for all you are doing for the community. Please do you offer SAFe Scrum training/coaching?
Thank you 🙏🏾. No I do not but @SAFeChartroom do. Contact Dr. Francis 🙏🏾🙏🏾
Great explanation to a very tricky question. By the way I just ordered a Hoodie from your store. Any discount for future orders?
Thank you, not yet discount we just lunched 😬😬
Great answer!!! Thank you Aisha...
You are amazing in all your videos...
Thank you 🙏🏾, I appreciate it. Thank you for watching
Excellent content! Thank you.
Thank you for watching 🙏🏾🙏🏾🙏🏾
Oh Lord. So if the required scrum events are 1. Sprint Planning, 2. Daily Standup, 3. Sprint Review and 4. Retrospective, you notice that "backlog refinement" is NOT one of the scrum events you mentioned. In the guide, refinement is "recommended but not required", since it doesn't have to be a meeting. So, it is very odd that you suggest removing a required scrum event with one that was not even given as an option in your introductory statement, and is not a formal event in scrum. Now, let's pretend that you did include backlog refinement as event #5. It is possible to plan stories in the refinement sessions, that is true. But since there is constant change on a scrum team, it is very unsafe to presume that whatever stories were "planned" on last Friday are still valid come the next sprint start on Wednesday. So there is risk in skipping planning due to this alone. Additionally, the team needs to AGREE on the scope within the sprint, and they cannot do that if they don't meet one last time to review and plan and commit. Finally, part of sprint planning is looking at capacity; "Who will be out this sprint? How many days? How many points/stories should we remove from the sprint?" If you skip this step, you are likely to overcommit the team. As a hiring manager and coach, I would never propose dropping an event. Instead, I would expect the SM to say: "Dropping an event is a serious decision and we would need to investigate this. I would want to gather more information, and speak with our coach and my manager first." Then I would want the candidate to ask questions back to me, as the interviewer. "What events do you currently use? What reasons are they giving for wanting to drop an event? Is there an event they think is useless? Have they made suggestions about how I can improve it?" When I see a candidate is too scared to ask questions, and is instead quickly willing to scrap the scrum guide to keep the team happy, without exploring options, I know we are about to have problems.
Did you really watch the full video??? Anyways thank you so much for your in put, greatly appreciated 🙏🏾🙏🏾🙏🏾
@@AishaTech655 Aisha I watched and pointed out an issue. Perhaps instead of automatically presuming I did not watch you should pause and consider the constructive input I am giving. I've been hiring, managing and coaching scrum masters for 15+ years. I listened to your argument twice and then responded. It is bad advice. I have had to deal with the consequences of this type of advice before and it creates a mess.
But if we focus only on the interview, your recommendation is likely to cause candidates to fail the interview! Scrum clearly states that the required ceremonies are key parts of scrum and if you remove those you are not doing scrum.
You are promoting what we call "scrum-but". As in: "we say we do scrum, BUT we dont do planning".
This is an anti-pattern.
u the best 💯💯
Thank you 🙏🏾
Question number one is very tricky and the interviewer might ask you the below question ; so I might need to disagree with you .
But there won’t be any product to deliver. If the team doesn’t stick to the sprint planning, how would they know what to prioritize based on user stories? If there is no sprint planning, the spring backlog is not enough
Very valid point 🙏🏾
Excellent contribution ❤
Thank you 🙏🏾
As Salaamu Alakium
Ramadan Mubarak 🎉
May Allah accept our fast and grant us mercy Ameen
Ameena, MashaAllah 🙏🏾🙏🏾🙏🏾🙏🏾
ruclips.net/video/FCliDQggOsA/видео.html
Key Differences Between Scrum Master and Project Manager
Ok
Hello Aisha, thank you for the good work you do. I have a question what happens if the stakeholders do not come for the sprint review.
Very good question, the session will go on. Also reschedule with the stakeholders.
So the review meeting would now be made up of the Scrum Master, PO and developers?
The review should involve the scrum team and all stakeholders. Sometimes, you will have to adjust as issues arise, but always ensure your stakeholders are informed🙏🏾🙏🏾🙏🏾
@@AishaTech655 Thank you so so much!!
I love your approach about this. Thank you
Thank you 🙏🏾
I strongly disagree with your backup argument in response to the first question ;Which of the agile events will you eliminate if given the chance. Stating your response as sprint planing is fine. Arguing that it can be replace by backlog refinement is wrong. Officially backlog refinement is not one of the agile recommended events and it should not be considered as an official event.
I will rather do away with retrospective. It is process improvement but can be merged or communicated during other events. Besides, good planning will have a team working agreement that can be updated My take
Thank you for your feedback 🙏🏾🙏🏾
Sprint planning and backlog refinement of you do the same time it will take more time or at the same time, because if there is the team that needs technical clarification or some thing that the team cannot understand the requirements. So for just an interview you can say this to impress your interviewer, if not this is an anti pattern. I think if the scrum doesn't want first place why do they need to keep in the scrum guide 😂.
My opinion this is not good 💡 idea.
Have a wonderful day.
Thank you for your insight, much appreciated 🙏🏾🙏🏾🙏🏾
Aisha. Thank you for all the knowledge . Can you please start a free whatsapp group for your channel subscribers, where we can share and expand our knowledge under your supervision/ facilitation?
Thank you for watching, I appreciate it. I do have mentorship group on WhatsApp but it paid ☺️☺️☺️
How much is the paid whatsapp? I have interest because you are a fantastic coach
Thank you 🙏🏾, I appreciate it. Please our site for price
www.aishatechs.com
I agree with the Sprint Planning only if we have been doing backlog refinement 😂😂. Could this be one of those tricky questions where they want to make sure we know the importance of all the ceremonies?
Yes for sure 😅😅😅.
ABSOLUTELY and you observed a problem with her answer. She essentially suggested replacing a critical REQUIRED event with one that is NOT a formal scrum event.
Bad idea. Were I the interviewer I would hit the buzzer.
Q: "Do Scrum Master jobs have any type of incusion for minorities?"
A: "Does money grow on trees?"
You tell me