An anti pattern is a frequently used, but largely ineffective solution to a problem. The term was originally used to refer to a pattern gone wrong. As Scrum practitioners, we all know that Scrum has events, artifacts, roles and rules. If the core principles, foundation ideas or the agile manifesto is 'tweaked' hoping they would provide benefits because teams are not seeing immediate results, this may result in an anti pattern. This in turn may become an ineffective solution to a problem
The founders and co-founders are right, in frame-works like Scrum are founded on empirical process control or empiricism and teams need to follow certain rules to be successful! In this interactive session, we will identify the anti patterns that some teams have developed and formed bad habits that made it difficult for them to go back to those fundamentals.
We will discuss why the core principles are very important to the success of Scrum Teams and talk about specific anti patterns in terms of events, artifacts, roles and rules. Rules may be important, however is it important to apply the basic principles that may help us to do the right thing in any situation without resorting to rules? I want to share my experience of working with agile teams for the past 10 years and talk about real-life examples that I have seen in my experience. More importantly, the participants will identify and discuss the antipatterns they have observed in their daily life.
