If there is one thing I hate at work, it is being caught by surprise on one of my projects. As a Project Manager, I should not be surprised by anything that comes up in my Status Meetings. To avoid getting side-swiped by any news, I do my best to keep an eye on all aspects of my projects, at least on a high level.
Status meetings have a tendency to get a bad reputation. Many can feel that spending anywhere from a half-hour to an hour just talking about project status when there is *real* work to be done is a major waste of time. Many times, project teams work individually or in silos that keep them isolated [...]
‘Project plans’ as utilized in a business function, are used as a communications tool and a form of checklist of tasks. Keeping that in mind, the best place to start with creating your plan is to start with the high level deliverables of your project, and then break each of those deliverables down into the tasks that it will take to get them completed. I tend to treat this part of my project plan as my ‘brain dump’. I put in the high-level deliverables, then ask ‘then what?’
As a Project Manager, it is going to be necessary to pave the way through obstacles that come up as the project progresses. Some say that this is the main responsibility of a Project Manager, and I tend to agree. It is up to the Project Manager to ensure that obstacles are dealt with and mitigated before they affect the project team and the project itself. Generally, there are three different kinds of obstacles that projects face: Technical, Political, and Emotional.
Think about a person that you would follow regardless of where they were going. What makes them a leader worth following? In terms of the business world, a leader doesn’t necessarily make decisions, and a leader doesn’t necessarily have the highest ranking title. A true leader is someone that has earned the trust and respect of their team; and as a result, that team will follow that person in whatever direction they take.