Post by 'Zander Collier, III' ***@gmail.com [SCRUMDEVELOPMENT]I mean, find out what precipitated their move to bring you on board to
do Scrum.
They were doing something before? Did they not do software development
before? Maybe they tried Scrum before and it didn't work?
Your original email suggested to me they're going to scrum from
something else. Find out what that something else was, what didn't
work, and what precipitated their decision to do something else.
I'm sure you'll get the usual, "Stuff wasn't getting done... Wasn't
getting done fast enough..."
Too many places I've worked have "decided to go agile" and "to use
scrum" but then never had the discipline to follow through. They
thought that by calling something that they did "agile" without actually
doing agile would somehow magically confer benefits when they had
unrealistic expectations and refused to be disciplined about how they
pursued using the process.
Maybe you can ferret that sorry of thing out...
Best,
-Zander
Journey lines? Or what do you mean, Zandler?
On Sep 29, 2015, at 8:24 PM, 'Zander Collier, III'
You might want to consider taking them through an exercise of how
they got to where they are
That might reveal a lot without them thinking that you're getting
them to reveal their concerns.
Best,
-Zander
Leading a two hour workshop tomorrow to executives at my client
about their agile transformation I am shepherding. Any
suggestions on a good and short ice breaker game? I thought
about "Pocket Manifesto " but I'm not teaching agile as much as
I'm discovering their concerns.