By articulating and removing agile pains (i.e., misunderstandings, conflicts and antipatterns born out of implementing agile ways of working), organisations can get more out of their investment in working agile. Agile antipatterns are sub-par solutions to challenges that arise when the intentions of working agile meet the limitations of the organisational reality. It’s the “pragmatic” shortcuts that, on the surface, seem appropriate and sensible, but in the long run can decrease the benefits of working agile.
Examples of agile antipatterns:
- #1: Product Owners only prioritise business features and not technical enablers and process improvement initiatives.
Consequence: Reduced quality of the product and no team culture of continuous improvement. - #2: Scrum Masters “do” instead of enabling the team to do.
Consequence: The team is ineffective because it doesn’t learn self-management and to grow as a team, but keeps being dependant on the Scrum Master. - #3: Dependencies are not broken, but instead coordinated through a scaling framework.
Consequence: The organisation spends a lot on events, roles and artifacts, and the value delivery of each team slows down because of the need for cross-team dependency management.
Participants will learn how to:
- spot the biggest agile antipatterns of their organisation, inspired by the creative Comic Agilé way of thinking
- identify the root causes of agile antipatterns
- come up with realistic solutions to remove the root causes
- create their own agile comic strip based on their chosen agile antipatterns
- communicate agile antipatterns to decision-makers using the format of comic strips
Also, we’ll focus on how:
- not to drown teams in meetings when going agile
- the organisation needs seasoned Scrum Masters, but end up hiring babies, and firing them again
- avoid imprisoning our Product Owners and, instead, empower them
- prevent that Agile Coaches become preaching evangelists
- see scaling agile like treating the symptoms when we should, instead, remove the dependencies that cause the need for coordinating between our teams.
- manage that Managers, on one hand, are expected to be in full control and, at the same time, expected to empower their teams to be self-managing
- realise that we cannot be agile if the architecture doesn’t support it
- …
Instructor bio
Luxshan Ratnaravi holds an M.Sc. in Software Engineering and works as an independent Agile Coach. For the last 14 years, Luxshan has held different agile roles, such as Product Owner, Release Train Engineer and Enterprise Agile Coach in companies within finance and renewable energy. He’s a seasoned agile practitioner, keynote speaker, workshop facilitator and course instructor, where his focus is on how to cut the BS and take a pragmatic approach to using agile practices to improve outcomes.
Target audience
Scrum Masters, Release Train Engineers, Agile Coaches, Product Owners, Product Managers and Agile Line/Project Managers.
Duration
7 hours including breaks
Format
Online course with break-out rooms in Zoom
Language
English
Practical Information
- Date option 1, Europe daytime: Oct 8, 9:00 AM – 4:00 PM CET
- Date option 2, Europe evening: Oct 15, 3:00 PM – 10:00 PM CET
- Date option 3, US daytime, East Coast: Nov 5, 9:00 AM – 4:00 PM EDT
- Place: Online through Zoom and Miro
- Price: 495 EUR (app. 540 USD / 3,700 DKK) ex. VAT
- For a company-specific version of this course, or for inquiries on bulk discounts, please write to us here.
Sign up
Recent Comments