Mind Maps – The key to success of the detailed project plans

This article will focus on why you need detailed project plans and how to develop effectively using a simple but surprisingly successful communication tool. A disclaimer up front: This article will discuss this in terms of technical projects, such as application development, but applies to all types of projects such as the collection of boats, grills, bah-mitzvah, or whatever objective they seek to achieve.

WHY IMPORTANT TO ME?
I bet she has a routine. One to follow every day. Get up, brush teeth, pack your lunch, take your cell phone charger, kiss the wife goodbye, etc. Now how often arrive at work and realize you missed something? "Shoot … I forgot socks again." Well, that may be extreme, but you get the point.

And I'm sure that does not happen every day. But maybe once every few months? Keep in mind that it is his routine five days a week 48 weeks a year (I know you do not take vacations, but others yes.). So now imagine what could happen if you're trying to remember all the steps you need to deploy your application in production. To this end, perhaps once every three months … 6 months? What are the odds that you might forget some of the critical steps? Maybe a little higher than some forget part of your daily routine?

What is the result of forgetting to restart a server to Web applications after the liberation? Well, I suspect that his boss would be much more angry than they were looking at her ankles bare, hairy.

The bottom line is people forget things, even routine things. And the risk that someone takes a step that is crucial, but only for a project is high risk and high impact. When this happens, you need look no further than the replica near blame. God knows that his boss has all the speed dial numbers and use them when he learns of the clients are receiving from time to time "Server Down "messages.

There are other problems lurking in the dark. You can remember your routine, but because Joe does not know what to do, can not realize that has a role to play. Example. You will update the database tables during deployment. Well, the DBA does not know, so Friday night is bowling. When, in fact, should stay home and monitor the implementation of a full backup of the database.

What should I do to prevent this?
The question remains how to avoid taking the blame for another brain spasm. Well, I like to go back to a simple but effective approach to help out the entire team. It's called Mind Mapping. I do not think Vulcan mind meld … think more shale and deliciously scented markers. These are more effective due to smoke free mind, but the online collaboration software will do the trick too.

I assure you, no matter what media you choose, this tool only allows you to substantially reduce the number of "Oopsies." Also avoid "traps" and completely eliminates the "he had its processor. "

What is a mental map? Is a simple diagram that focuses the team on a single topic. Mind you (no pun) that "The project" is not an issue. That's too big. But, depending on the size of its initiative to "implementation" could be an issue. Or for projects larger "data base" may be an issue. There is some statement that is used here, but you'll do fine.

The bases are:

• You get the relevant parties together and they focus on "the issue"
• Each person calls out ideas or tasks related to the theme ""
• For each task or idea shouted the team is asked to consider the task aloud and articles related to this task, etc, until the ideas are exhausted

Again, this is the basic idea. You can make more with these and I'm sure there are variations on the theme. But it is understood the idea.

WHY does this work?
That's pretty simple. Opens channels of communication, and makes things computer chat and face each other. "Oh, well, you're going to update the tables in the database? Fortunately, good to know. We will not bowling and backup of the database." Wow. 10 seconds Conversation just avoided a huge risk.

The fact is, no matter how many times does something, no matter how much of an expert you can not remember every time. It is simply not human.

And you certainly can not know all the aspects of impacts it has on other team members. That's why tools are some important communication. I have worked with developers surprising that so make sure what they think other experts are not necessary. And I could never think that the database backup because they were sure the updates would be perfect.

RECAP
People are not perfect. We forget our socks. We do not think Joe would want to skip bowling to store a database. Unfair as it may seem your job is to ensure that we all remember our socks and make sure that Joe is lost bowling occasionally. Mind Maps are an easy and effective to do so.

About the Author

Mike Balsam is an expert in Project and Program Management having spent 9 years out of his 17 in the IT industry leading the delivery of mission critical applications for Fortune 100 companies. He specializes in application development and managing geographically dispersed teams. You may view his profile at www.linkedin.com/in/mikebalsam. He can be contacted at mikeb@consegnainc.com.

Ultimate Mind Tools FREE e-course for emotional intelligence