As an Agile Coach I want to help people learn how to be Agile so
that they can achieve the success I have seen others realize.
Acceptance criteria: People are thinking Agile and approaching their work in an Agile manner. Teams are working in an Agile environment, experiencing improvement over time and enjoying themselves.
Most of the early work with a business
transitioning to an Agile environment is facilitating training sessions where
everyone learns what Agile is and the basic outlines.
At its core Agile is a framework of
guidelines with a menu of practices. Each organization, and each team within that organization, must
start by working within those guidelines, inspect and adapt what is working and
what isn't, and then make changes as necessary; and repeat this process over
and over.
The initial interpretation of those
guidelines is critical. I have seen Project Managers take the guidelines and
simply place what they know into them. This can work, however if this person is
also acting as the Scrum Master we can expect to see a less than Agile team
result. There is a conflict of interest between the command and control aspects
of Project Management and the servant-leadership role of a Scrum Master.
Similarly, developers, testers, and
analysts must understand that they are not doing the same thing they have done
before just in the 'Agile way.' If they
are open to the opportunities Agile offers them as a part of the larger group
they can really impact what the company is doing and how.
I have seen managers profess their acceptance that things
must change and that Agile is the way they want to go, only to begin to exhibit
far more controlling tendencies once their teams are truly beginning to be
Agile.
The financial section of companies have their own processes and
require certain information; we begin to experience friction when we’re
developing product in an Agile environment but must still forecast what each resource
is doing and on what project and when before we are able to plan anything.
Agile is truly a mindset change that should result in business
model innovation. Because if the model we’re using is working, then why are we
moving to Agile? We need the innovation prospects that Agile offers.

We have a lot of fun in the workshops, you can see that in the
photos, but how do I know the teams are really learning Agile? Good question.

I also run surveys after each workshop to find out whether the
information and the way it was presented was useful and whether the attendees feel
they learned something, but that doesn't tell me how they will do when applying
it themselves.

I tell the attendees in every workshop, it will take a while to
truly assimilate the concepts and it will take trial and error and the actual
practice of being Agile for them to see whether this is going to work and how.



I know they won't all take on that challenge, but those that do
will help their teams be better at applying Agile concepts and every team that succeeds
will be the catalyst for another that is just getting started or the support
for one that is having trouble.
My user story is really an epic and I won’t be able to answer the
question of whether I am done for some time. But I will circle back from time
to time and let you know how we’re doing.