hello everyone today we're gonna be answering the commonly asked interview question have you
ever dealt with resistance in the past as an agile practitioner so I'm going to be giving an example
a sample that you can use and you know succeed in your interview and in addition to that I'm going
to be using a very cool technique known as the car technique um car it's an acronym that helps
guide you to ensure that you're covering all the areas as the interviewers would like to hear the
C stands for the challenge or context a stands for the action that you took and R stands for
the results if you apply this technique you will be ensuring that you are given the interviewers
what they want and that's how you'll be moved to the next phase of the interview so let's go
if I'm asked this interview question the way I'm gonna approach it is I'll say something like oh
yes I have dealt with resistance so many times a typical example that I can recall was a time when
I joined an organization and then I noticed that they were not conducting the standard
official scrum events most especially they were doing some of them but one of the most important
scrum events which is the Sprint review they were not actually doing this event and as a result
of that it seems like they never had a stopping point so team members were always feeling burnt
out customers were hardly ever satisfied because they've never had an opportunity to even see one
um working functionality that the team members have created they will only hear about it through
status update meetings but never an opportunity to see even the director of software engineering even
told me that Karen it will be the best day of my life if I had to even had the opportunity to see
one working functionality than this that this team has created instead of always hearing about it
and the funny thing is that whenever they would talk about this thing during the status update
meetings in reality when these things are being deployed to customers it hardly does what it was
intended for so customers were always frustrated team members were demotivated because they felt
like they were not appreciated despite their hard work so I asked if they are familiar with
um Sprint review events they were not familiar with it I asked if they are open to trying it
out that that their lead wasn't interested at all according to the devil it was just an additional
meeting so there are already so many meetings so the definite was super frustrated and not ready to
attempt it at all so in my understanding I seek to want to know where the depth was coming from and
then I realized that they were already overwhelmed with so many different meetings that has nothing
to do with scrum events so I see that as an opportunity and asked if they were interested in
hearing about how the scrum works and the events so they were open to that so I explained to them
the concepts of the scrum events and the purpose of this and I was able to help them separate the
scrum events from every other meetings helping them to understand that the priority for them
to be successful as a scrum team is to First ensure that they are reflecting they are taking
advantage of these events and then they can you know deal with their other meanings so with that
understanding the scrum list too wasn't interested so they still went through one more Sprint
and again as usual it seems like they were continuously going in circles never stopping
points to just stop and see what they've been doing and I even appreciate their own work so um
I still went to the devilite and asked if they are open if he's open to just try out the other team
members were open and interested to just try out this um Sprint review event and if if he doesn't
find any value in it he can always drop it they can always drop it so with the concept of with the
mindset of experimenting the devil was like okay let me give you a benefit of the doubt and try
this out so I went back I did my best to plan for that event in advance to ensure that we're getting
the most value out of it so I set up the event and we conducted a Sprint review event for the first
time ever I had marketed it and were able to have the stakeholders that we needed and during that
events they were really able to demonstrate the three Squad pillars of transparency inspection
and adaptation and they were able to get feedback from customers and right there and there they were
able to apply the feedback to the upcoming Sprint to ensure that we're creating the right product
thoughts you see and then as a result of that they were able to also see real working functionality
that was something it was so motivating the director of software engineering was so happy
and team members were happy so after that we went to the retrospective I asked if it's something
they would like to try again they definitely was the first person who said yes I would let's let's
try this one more time and see and that is how the Sprint review event became a standard to the
organization and everyone was happy so that is how I have handled resistance in the past hope
this was helpful and I would like to hear your thoughts in the comment section take care bye
[Music]