TL; DR: Scrum Master Job — 4 Steps to Identify Suitable Employers or Clients
Are you considering a new Scrum Master job? However, you are not sure that it is the right organization? Don’t worry; there are four steps of proactive research to identify suitable employers or clients for Scrum Masters and avoid disappointment later.
I have used those four steps for years to identify organizations I would like to work with, and they never failed me. Read on and learn how to employ search-engines, LinkedIn’s people search, reaching out to peers in the agile community, and analyzing the event markets in the quest for your next Scrum Master job.
TL; DR: Agile at Tesla, Roadmap Bankruptcy—Food for Agile Thought #276
Welcome to the 276th edition of the Food for Agile Thought newsletter, shared with 30,023 peers. This week, we delve into Agile at Tesla; we learn how Retrospectives work in the most unlikely places, and we embrace a new approach of risk-mitigating by utilizing the Product Backlog.
We then analyze what product managers can do to deliver more value with existing processes; we detail three cases that indicate that your product roadmap is not up to the job but in desperate need of a restart, and we point at three common mistakes when calculating customer lifetime value.
Lastly, we explore a simple visualization tool to help teams turn learnings into a better way of working, and we ask: Is SAFe® safe?
Job ads for Scrum Master positions reveal great insight into an organization’s progress on becoming agile. I analyzed more than 50 job ads for Scrum Master positions to gain these. Learn more about what makes job ads such a treasure trove with the following 22 Scrum Master anti-patterns derived from job ads.
TL; DR: Bureaucratic Blunderland, Saying No—Food for Agile Thought #275
Welcome to the 275th edition of the Food for Agile Thought newsletter, shared with 29,852 peers. This week, we delve into the sheer variety of folly at play in any bureaucratic blunderland; we analyze different kinds of technical debt and how to best measure it, and we embrace a simple process to apply swarming as a team practice to solve critical challenges.
We then learn five practical tips to say no without offending senior or assertive stakeholders, and we enter a quest for magic metrics by ‘counting things that happened that you care about.’ We also check general product manager salary data based on January 2021.
Lastly, we examine a formula and a process that may allow us to figure out why things are less agile than hoped.
While the new Scrum Guide is less prescriptive and more inclusive, it also ties loose ends by including elements better, namely the previously free-floating Sprint Goal and the Definition of Done with the creation of Scrum commitments. This inclusion works remarkably well in the former’s case; regarding the latter, we need a shoehorn, though.
TL; DR: Scrum History, State of PM 2021 Report — Food for Agile Thought #274
Welcome to the 274th edition of the Food for Agile Thought newsletter, shared with 29,681 peers. This week, we delve into Scrum history, and we enjoy an interview with Jeff Sutherland and Ken Schwaber on the changes of the Scrum Guide 2020 and what motivated them. Also, we dissect the dilemma surrounding the estimation process.
We then enjoy the results of two product management related surveys; we discuss user stories, tasks, and features in disguise to release more value sooner, and we learn from Martin Eriksson’s decision stack.
Lastly, we welcome John Cutler’s comprehensive checklist to support decision-making at a high-quality level, maintaining the decision flow. Speaking of decision-making, you may be interested in the ‘Six Thinking Hats’ tool as well. (That’s right, there is a tool section now.)
