So okay, Microsoft Project is a super flexible tool in helping you as a project manager define your project tasks, dependencies, and resources. Quite frankly, though, the workplan you define in MS Project is only as good as the thought that goes into it. Too often I've seen savvy MS Project users completely bungle a project because, while the tool was being used appropriately, the workplan didn't make sense to the project team and didn't reflect what really needed to be done. The team consistently expressed confusion about what needed to be done by when because the project workplan wasn't reflective of the actual work which needed to be done. Great exercise in using MS Project, but poor execution of the project. Blech.
Within a few months of my open door policy, I saw my own productivity drop and my frustration level rise because I kept getting interrupted by people taking me up on my open-door policy. My open-door policy soon turned into a series of random interruptions that caused me to not get my stuff done. I came to recognize that I needed to be accessible to people but that I could control the accessibility through scheduled time. Open-door means be accessible, not come in whenever you want.
A pretty nifty feature in Microsoft Project is the ability to define a project through the use of the project guide. The project guide is a cool little wizard that walks you through setting up a project, assigning resources to the project, tracking progress, and reporting on progress. What I like about this wizard is not only the help it gives newbie project managers, but also is a great reminder of the cool MS Project capabilities for more seasoned MS Project project managers.
To get started with this cool project management software tool do the following:
So let's cut to the chase...
You may be a great consultant, one who effectively applies his or her wisdom and experience to help his or her client solve some tough business problem. That's all fine and well. When it comes to facilitation, though, it's a different ballgame and a very different approach to problem solving. I like to think of the difference as follows:
Several years back a colleague of mine (I'll call the colleague "Nellie") was managing a very high-visibility project. This project was high on the radar of key executives all the way up to the CEO of the company and any major mis-steps would send fireworks up the chain faster than lightning. This was one of those "thrill-seeker" projects; definitely high risk but also of high reward if the project was successful. Nellie was up to the challenge and willingly accepted the assignment.
Contact Lonnie about article reprints. Please specify article you wish to reprint.
See Lonnie's Amazon Author Page