Someone recently asked me a simple question, so I thought. "How do I get real world business people to adopt agile?"
I've thought about this for 3 days and it's eating me a little bit. I think we as an industry has such great impact and sourcing from the software environment that it just makes sense in that space. I don't see it happening in the product development space as much (maybe because they started a long time ago). On the other hand there are places like cites, states, government, and more "traditional" businesses that may not be even looking at agile in this space yet.
So I thought about a couple of things that I've done in the past that caused issues for me.
Don't use Buzz Words. Using buzz words or technical speak is a good way to stop a business conversation before it starts. Because of my background, I still do this one. When I discuss project management, software development, or technical infrastructure I find myself whisking off of the tongue these multi-syllabic words of wisdom as if we all just walked out of my brain after coffee. Pointless.
Don't remember your context, but understand theirs. Before leaving your office, imagine what their day has been like. The kinds of conversations your boss may be having and remember that Value and Quality are at the top of that list. Remember that their support in your effort is critical to it's success.
Avoid negatives. Try not to discuss the need to eliminate waste, but to expedite changes and shorten times to market. An eager employee or thought starter is a great thing to get buy-in, but pointing out the elephant in the room can have unintended consequences. They may know of the issues you are facing, but don't want to hear you point them all out.
Assume Objections, don't assume responses. How many times have you had an entire conversation with your boss before you even entered the office? If you are assuming the objections of another, you can prepare your conversation. If you are assuming how someone will respond, you are already limiting the conversation and can be causing the outcome you want the least. Pace yourself and allow them to understand each point you are making.
I've thought about this for 3 days and it's eating me a little bit. I think we as an industry has such great impact and sourcing from the software environment that it just makes sense in that space. I don't see it happening in the product development space as much (maybe because they started a long time ago). On the other hand there are places like cites, states, government, and more "traditional" businesses that may not be even looking at agile in this space yet.
So I thought about a couple of things that I've done in the past that caused issues for me.
Don't use Buzz Words. Using buzz words or technical speak is a good way to stop a business conversation before it starts. Because of my background, I still do this one. When I discuss project management, software development, or technical infrastructure I find myself whisking off of the tongue these multi-syllabic words of wisdom as if we all just walked out of my brain after coffee. Pointless.
Don't remember your context, but understand theirs. Before leaving your office, imagine what their day has been like. The kinds of conversations your boss may be having and remember that Value and Quality are at the top of that list. Remember that their support in your effort is critical to it's success.
Avoid negatives. Try not to discuss the need to eliminate waste, but to expedite changes and shorten times to market. An eager employee or thought starter is a great thing to get buy-in, but pointing out the elephant in the room can have unintended consequences. They may know of the issues you are facing, but don't want to hear you point them all out.
Assume Objections, don't assume responses. How many times have you had an entire conversation with your boss before you even entered the office? If you are assuming the objections of another, you can prepare your conversation. If you are assuming how someone will respond, you are already limiting the conversation and can be causing the outcome you want the least. Pace yourself and allow them to understand each point you are making.