IT项目管理26953.ppt

Why do we have a Process Risk Areas (Example) Risk Areas (Example) Product Introduction Components A Development Life Cycle – Why? The Life Cycle Process - Elements Hardware Development (Example) Hardware Inch Pebbles - Per Cycle Diagramming Exercise Critical Path Exercise Exercise Purpose Show schedule progress against plan Activities/tasks against Time Demonstrates Current Activities Advantages Good communication tool Easy to prepare and maintain Portable from Small to Large projects Disadvantages Does not easily show task inter-relationships Does not show end to end flow Reflects status of events over time Excellent for Event Driven Projects Brainstorm the problems that you face with schedules in your project environment Risk Definitions When to Manage Risk Risk Evaluation With your team brainstorm some common issues that you are faced with managing projects Barriers to Communications Lack of clear communications channels Physical/temporal (time) distance between communicators Difficulties with technical language Distracting Environmental factors Detrimental attitudes/hostility/disbelief Common Filters Language Culture Semantics - point of view Intelligence/Knowledge Message Content Ethics - lying Reputation - past Authority Organizational Status History Running Formal Reviews Running Formal Reviews Take your list of Issues from the last exercise Identify the stakeholder that created the issue What justification could that stakeholder have? Change Control Board (CCB) A formally constituted group of stakeholders responsible for approving or rejecting changes to project baselines   -Reference: PMBOK? Guide, 1996. Ch. 5 Control Systems Changes to the baseline are controlled in a structured manner Changes are identified, defined, evaluated, coordinated, and approved before implementing the change Changes to the baseline are documented Body - 55% Voice - 38% Words 7% Non-Verbal Communications 45% - Listening 30% - Talking 16% - Reading