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).
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
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.
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.
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.
@@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
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.
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.
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.
