Cold shoulder from your boss and trying to undermine your opinion are surely signs of you getting fired. I see these signs now and I know it's coming. In the meantime I'm doing my best to get another job.
So on this topic it always good to continue to grow in one's learnings especially while in a job. No one ever knows when a decision is going to be made and many times there is nothing you can do about it. I know many agile people are negative about certifications, but taking a class in some new growth area and getting a certification is just bonus. During these quite times in holiday offices, I would like to encourage people to study and take a class.
If you notice that all of your meetings for later that week were canceled, and that one was scheduled for that Friday afternoon with your boss and with anyone with HR - they're firing you.
Here are some other signs that you will be let go: 1) if your hours keep on getting reduced. 2) HR gives you dirty looks or starts laughing at you every time they see you. What I learned is that HR is not Police Department. They are just workers like everybody else. If there is a conflict between two workers, they are going to do what is right for the company, not the victim, especially if the victim is just a "pawn' within the organization. Usually, HR will get rid of the victim who is just a "pawn" in the company.
In my previous workplace, they couldn’t fire people unless they did something horrendous (aka blatantly illegal). However, they could put you in a dead end job. One way that happens is if they put you on a “Special Project” for work that you can do like the back of your hand. Sometimes Special Projects are good if they allow you to grow new skillsets though. Another thing one has to watch out for is if one notices that those who are not “yes” people keep getting pushed out of their leadership roles. In “yes” cultures, non-yes personnel won’t survive unless they decide to tow the line. In that case, one has to decide if working for such an organization is worth it. In my case, I was put on a “Special Project”. I won’t go into details but the manager acknowledged a mess was created. Organizational morale was impacted. In my case, it bought me some time to turn over a large project as I had just finished interviewing with 4 organizations, and I was waiting for a final offer before I gave my notice. They ended up getting 4-5 weeks of me turning over my project vs. 2-3 weeks. Still if one is cutting a person out of a role, managers need to be really careful on how it is done to minimize a negative employee experience, and to minimize negative impact to organizational morale. Having HR involved is good to help ensure everything is done on the up and up and minimize potential legal repercussions. If HR is not involved, I think management can potentially put themselves or the organization at risk.
I like this little nugget of information! Almost done watching all 447 videos. :) Question: since I live in an area where SAFe seems to be prevalent, could you do a video on elevating Scrum or Kanban in a SAFe environment? Or maybe you could do a video with Yuval Yeret of some things that he found works to gain some traction especially in introducing empiricism. I suspect empiricism is missing in SAFe implementations. I also suspect there is more focus on predictability, in SAFe, than on empiricism. Predictability is good (if flow metrics are used), and not the silver bullet. I know it’s all context dependent, and sometimes when I hear someone share their experiences, it gives me some ideas of what kinds of content I might try to have next.
As a scrum team we are trying to adopt throughput based capacity planning. The main challenge we are observing that varying size of work items throwing our projections off the curve. Can you discuss on how to handle this situation? Thank you
Are you attaching a probability to the throughput you are considering? Do you have an SLE with a probability? Are you questioning whether something is "right-sized" for the Sprint (then splitting when necessary)? Are you considering other factors (retro improvements, definition of done changes, the type of work, vacations)? Capacity based planning alone will never give you the answer that you are looking for regardless of the method you are using.
@@AgileforHumans - I think, I got my next step to explore 'right-sizing'. Thank you. And to rephrase my original question - "We are trying to adopt throughput based planning over velocity based sprint planning. Our goal is to reliably forecast how many 'work-items' we can deliver at end of the sprint. Varying size of work-items introducing high variance. Looking for some tips around there. Thanks again.
Hey guys love your content Questions what are some other things I should look forward to when interviewing as a scrum master. What are the general questions that I will Be asked
Hey Guys, As a scrum master we are often asked about domain experience , eg: If you have experience in Finance, Cash management, Retail and so on. How should we handle such questions, since our role in more inclined towards assuring that agile mindset is inculcated be it any domain. But still looking for your opinion. Thanks
Can handle that one right here 😊. Don't do it. The teams capacity should be one of many inputs into Sprint Planning. Others might include: previous performance, retrospective improvements, the definition of done, the Product Backlog (of course), etc...
Hi Ryan and Todd, sorry if this is not the right place to ask this question but I was not able to find the section to privately message you. I am currently a project manager at a tech company and would like to shift gears into a scrum master role. I have watched many of your videos and find them very helpful. Thank you! I've seen videos where you recommend books about scrum, but the options were many. I am looking for a single book to start with where I can learn to speak intelligently about scrum, help me pass an interview, but also teach best practices. Is "Fixing Your Scrum" suited to help me achieve this? Other than "Fixing your Scrum" could you recommend a single book out of the many options that you've spoken about? I would greatly appreciate it. Again, looking for a book explaining best practices, but also one that can help me obtain knowledge to speak intelligently about scrum, and also to help pass "interview" type questions. Thank you both for always providing great content!
Fixing your scrum was my first Scrum Master book erver, which Im still using after 2 years! The other one I really liked is the Zombie Scrum Survival Guide.
@@DanielLee-dy4fj I was lucky that my company had a traineeship for becoming a Scrum Master. Before I started I was master student Information Management