- Historical records are exceedingly valuable (like gold) to the project manager, the team, the performing organization and even the customer.
- Project cost and schedule cannot be finalized without completing risk management.
- A project manager must work within the existing systems and
culture of a company, which is referred as enterprise environmental factors and they are inputs to many processes. - A project manager spends all his time dealing with problems is not a great project manager. A good project manager plans the project to address the problems and to prevent the problems coming.
- Percent complete is an almost meaningless number. [JS] Unfortunately there are many cases that upper management only wants a number.
- A great project manager does not hold meetings where you go around the room asking all attendees to report. Such meetings are generally, but not always, a waste of time. [JS] It is a channel for team members to clarify their concerns of the project.
- The project management plan is approved by all parties, is realistic and everyone believes it can be achieved. [JS] I think it is a good practice to make the project management plan, or at least store it at a shared place.
- If at all possible, all the work/assignment and all the stakeholders are identified before the project begins. Stakeholders are involved in the project and may help identify and manage risks. [JS] A project success is all project team member’s responsibility, not only the project manager.
- The project manager has some human resource responsibilities of which you might not be aware. [JS] Whether you have the right person and they are keen to the project, and how team members are rewarded for their work. However, a project management is always limited by the organization.
Friday, October 23, 2009
My understanding of Project Management -ism
Labels:
softwareProcess
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment