You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Happy Monday Morning Everyone!
I know that Miscellaneous Monday threads are typically not work-related, but I was reading an article on LinkedIn today called "That's Not Agile..." and I wanted to talk about it with you a little today.
The TL:DR version goes a bit like this:
Teams engaging in Agile methodology have the potential to be pulled out of the framework by teams or people that are not. This leads to heaps of frustration on both sides because the people requesting the "non-agile" changes know you can do the work, and are puzzled as to why you can't/won't pivot. The people on Team Agile, on the other hand, will shout from the rooftops that there is a process and it is to be followed.
The article goes on to address some alternative responses, which could be likened to the old 'you'll catch more flies with honey than vinegar' adage. All of this seems to point to the fact that as well as being subject-matter experts and code wizards, the next step in our evolution should be developing mad Jedi mind tricks.
The most-impactful statement of the article is here:
At the root of it, it's not about saying, "that's not Agile." Each part of the process we follow has a purpose and an impact, and so we must find a way to express the real challenge, impact, or risk in another way
The biggest hurdle for me as a Jira administrator and agile-proponent is that folks on the other side of the window just don't know what sprints, backlog, scope creep, scrum, and prioritization are. We're not starting with common language. Unless we change the way that we're communicating these hurdles, in a non-hostile manner, we'll constantly be fighting fires and battling over semantics.
It's clear that our communication should be focusing more on the outcomes and pulling away from radical agility (should I trademark this?) , which is largely easier said than done when you're in the thick of it.
What I want to know today is, have you fallen to the dark side in an endless downward slide of pivot/firefighting? OR do you use your powers for good and gently explain the benefits of agile process and stick to your guns... er... lightsaber?