How to Sabotage a Scrum Master

How to Sabotage a Scrum Master: 44 Anti-Patterns From the Trenches To Avoid

One of my favorite exercises from my Professional Scrum Master classes is how to best sabotage a Scrum Master as a member of the middle management. The exercise rules are simple: You’re not allowed to use any form of illegal activity. Therefore, outsourcing the task to a bunch of outlaws is out of the question. Instead, you are only allowed to use practices that are culturally acceptable within your organization.

Read on and learn more on how to best sabotage a Scrum Master from the exercise results of more than ten PSM I and PSM II classes. (I slightly edited the suggestions for better readability.)

Guaranteed Ways of Failing With Microservices

In this article, I am going to highlight the sure-shot way of failing with Microservices and tips on avoiding them.

Using Microservices when It Is Actually Not Needed

Microservices cannot be used in every context. It is perfectly fine to not use microservices in applications that are small and can be managed easily as monolithic. Microservices come with their own sets of complexities like inter-service communication, managing different services, cascading failures if not implemented properly.

Why the Car Industry Needs to Take Lessons From Aviation to Make Autonomous Tech Safe

Before autonomous vehicles become fully autonomous, they were developing a range of driver assistance tools to help us navigate the roads safely and effectively. These tools aren’t always as straightforward as they sound, however, and various studies have illustrated how long it takes a human to regain safe control of a vehicle if they haven’t been concentrating on the road.

While these sorts of challenges are still relatively unfamiliar in a motoring context, they are very familiar in aviation, where difficulties in navigating the human/machine interface have caused numerous incidents. It’s a lesson a recent paper suggests we are not heeding.