TL; DR: Getting Hired as a Scrum Master or Agile Coach
Are you considering a new Scrum Master or Agile Coach 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 getting hired as a Scrum Master 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, reach out to peers in the agile community, and analyze the event markets in the quest for your next Scrum Master job.
TL; DR: Why Agile Fails — Food for Agile Thought #428
Welcome to the 428th edition of the Food for Agile Thought newsletter, shared with 42,147 peers. This week, Adam Yuret delves into why Agile fails, analyzing how traditional power structures resist Agile’s transparency and autonomy. Ant Murphy emphasizes the importance of decision velocity for innovation and adaptability, and Derek Jones discusses the shift from Waterfall to Agile, highlighting the need for adaptability in management. Wes Kao offers strategies for effectively discussing deadlines, focusing on intellectual honesty and trust. Lastly, John Cutler advises cautiously sharing complex topics to avoid workplace tension and advocates for a Trojan Horse approach to implementing change. Also, we delve into Agile Laws: From Conway to Goodhart to Parkinson to Occam’s Razor.
Then, Marty Cagan highlights the critical need for Product Owners and Managers to move beyond mere “product management theater,” emphasizing genuine contributions. Itamar Gilad advocates for evidence-guided decision-making, cautioning against the automatic acceptance of customer feedback, and Daria Beliakova examines the product management trends of 2024, including hyper-personalization and the challenge of subscription fatigue. Moreover, Lenny Rachitsky presents insights from Geoffrey Moore on navigating the market’s chasm from early adopters to mainstream success, detailing strategic go-to-market playbooks for disruptive technologies.
Lastly, Matt O’Connell delves into Opportunity Solution Tree (OST) patterns to improve team collaboration and problem-solving without specialized tools. Willem-Jan Ageling critiques organizational silos, advocating for trust and cooperation to achieve unified success, and Nick Brown discusses advancing beyond traditional predictability measures in agile teams with Process Behavior Charts at ASOS Tech, offering a more objective assessment of team performance. Finally, Steven Sinofsky shares a personal narrative on how the launch of the Apple Macintosh in 1984 revolutionized his approach to computing, emphasizing its ease of use and transformative impact.
On many occasions, working with agile teams has amplified existing organizational, technical, and cultural challenges in many organizations. Starting to change always requires the acceptance that there is a problem that needs attention. The following article addresses some of the most prevailing impediments to achieving agility by revisiting several agile laws that are particularly relevant to any team’s effectiveness in solving customer problems.
TL; DR: Continuous Product Improvement — Food for Agile Thought #427
Welcome to the 427th edition of the Food for Agile Thought newsletter, shared with 47,634 peers. This week, Jeff Patton outlines a continuous product improvement cycle, highlighting its critical stages, and Brian Link delves into the evolving landscape of agile practices, reflecting on the recent dynamics. Heidi Helfand shares valuable strategies from her book “Dynamic Reteaming,” while Joost Minnaar advocates personal transformation as a critical element in successful organizational change. Also, we ask whether Scrum GPTs pose a challenge to Scrum Masters.
Then, Roman Pichler shares essential tips on product portfolio strategy, while Alistair Cockburn advocates using simple use cases and user stories in Agile teams. Jason Evanish guides Product Managers on helping engineers improve feature delivery estimates, and Thiago Brant explores the importance of Business Agility across all areas of your organization, pointing to useful practices and helpful frameworks.
Lastly, Alex Ewerlöf discusses the concept of ‘tech gamble’ and the importance of informed decision-making in technology development. The Consortium for Information & Software Quality™ highlights the high cost of poor software quality in the US, and Dave Snowden reflects on his early work with matrices and their alignment with complexity science. Shane Hastie’s interview with psychologist John Fisher explores the Fisher Change Curve and its applications in change management. Finally, Economist Tyler Cowen delves into the evolving role of AI, from its potential for leveling the playing field to its broader societal implications in various domains.
Fewer Jobs for Scrum Masters, and now we see the universal Scrum GPT entering the competition: Will Scrum Masters change from essential practitioners to a niche role?
The job market is currently challenging for many agile practitioners, particularly Scrum Masters. Many are looking for new opportunities, while an increasing number of organizations consider the benefits they contribute to a team’s overall success. This is not just reflected in fewer job offerings for Scrum Masters; we also observe the demand for training significantly reduced.
To make the situation worse, AI has improved significantly over the last 12 months, too. Back in November 2023, OpenAI released GPTs, a hyper-customizable version of their GPT-4-based chatbot. (Please note that you need to have access to OpenAI’s paid version of ChatGPT to use GPTs.)
Besides the exciting market opportunity for many people with specific knowledge, data, or content, the question is what implication this new technology will have on the job market for agile practitioners when their roles are partly based on “knowledge” now available from a machine?
TL; DR: Continuous Integration — Food for Agile Thought #426
Welcome to the 426th edition of the Food for Agile Thought newsletter, shared with 49,156 peers. This week, we explore Martin Fowler’s essay, advocating for Continuous Integration for team efficiency, while Martijn Oost critiques quick Agile transformations, emphasizing a tailored approach. John Cutler discusses rebuilding trust in leadership, and Chris Corrigan explores organizational life cycles with the ‘two loops model.’ Lastly, we identify the signs of a Scrum Master’s journey nearing its end, reflecting on evolving organizational dynamics.
Then, Maarten Dalmijn delves into feature development, highlighting the actual value not in the features themselves but in the opportunities they create for users. Janna Bastow contrasts the complexities of overseeing multiple products in large enterprises with the more focused task of managing a single product. Additionally, Lenny Rachitsky and Dan Hockenmaier emphasize the significance of deciphering your business’s core dynamics using a fundamental equation that encapsulates inputs, desired outputs, and their interconnections.
Finally, Jason Cohen highlights the complexities of forecast evaluation using weather prediction examples, focusing on accuracy beyond just surface-level results. Benjamin Huser-Berta explains Monte Carlo Simulations’ role in forecasting and effective planning. Mads Soegaard and another article discuss the significance of user story mapping and Job Stories in product development, enhancing UX design and aligning with user perspectives. Lastly, Howard Tiersky advocates for agile adaptation in digital transformations to meet evolving technological and customer demands.
