For "Old School" technologists - it's a buzz word that they are immediately cynical of. This is also true of a lot of other terminology. When I've snuck in agile practices in the past, I've used "Phases" instead of "Sprints". "Scenarios" instead of "User stories" etc.
Use terminology that the organization is comfortable with.
Use terminology that the organization is comfortable with.
A friend (Let's hypothetically call him Scott) mentioned recently that convincing the business is often the hardest part of an agile transformation. That made me realize that for a lot of the implementations I've been part of - the transformation has been driven from the grass-roots level. It's rarely senior management driving the change - it's usually a lone dev team or sometimes just one manager who decides that there is a better way to build software - and does it. It's always easier to ask for forgiveness than for permission.
So how do you help the organization or business transform, when the Dev team is already champing at the bit?
Tune in next week - Same bat-time, same bat-channel.
