Extraordinary year: 50 project management stories (version 2nd)

Extraordinary year: 50 project management stories (version 2nd)
Basic Information
Press: People's post and telecommunications Press
ISBN: 9787115294579
Mounting time:
Published on: February 1, October 2012
Version: 0
Category: Computer> Software Engineering and software methodology> Software Project Management
Computer> E-commerce and computer culture> Integration

More about, extraordinary year: project management story 50 (version 2nd)
Introduction
Books
Computer books
An extraordinary year: project management story 50: Version 2nd based on over 30 years of experience in project management, the author refines the issues worth attention in the project management process into 50 stories, in addition, each story is followed by a summary of project management lessons. The story is well explained and the lessons learned are thoroughly summarized. This book is lively and lively. It allows readers to easily improve their management capabilities through representative and targeted project stories.
Extraordinary year: project management story 50: Version 2nd applies to project managers, project management consultants, and other levels of management personnel.
Directory
Extraordinary year: project management story 50: Version 2nd
New Year begins 1
Chapter 3 understanding the features of a Project 3
Chapter 7 should have clear and responsible initiators 7
Chapter 4 report the status of all projects 11
Chapter 1 Follow deadline 15
Chapter 18 use certain project management guidelines 18
Chapter 21 first defines and plans work 21
Chapter 25 do not "micro-Plan" or micro-management work plan 25
Chapter 29 employ a diverse Project Team
Chapter 3 What is in scope and what is out of scope requires multiple Definitions 32
Chapter 36 use the three major documents
Chapter 5 scope of use change management 39
Chapter 4 measure data collection 42
Chapter 4 regular performance feedback 45
Chapter 4 ensure that problem management is the responsibility of everyone 48
Chapter 4 short meetings should not be long, and key points should be the key 52
Chapter 5 identifying the root cause of the problem 55
Chapter 5 Status of items verified through Quality Assurance 58
Chapter 62 cancel projects that have lost business support 62
Chapter 5 use risk management to discover potential problems 65
Chapter 2 Quality Management focuses on processes rather than people 68
Chapter 1 do not apply estimated emergency reserves to scope Change 71
Chapter 4 preparing a communication plan for complex projects 74
Chapter 7 project size adjustment process 77
Chapter 1 plan 80 even if the project has already started
Chapter 3 identifying key paths and their impact on the deadline 83
Chapter 1 Change Hypothesis to modify estimation 86
Chapter 4 do not forget face-to-face communication in the project 90
Chapter 3 make quality a concept and a continuous process 93
Chapter 6 submit small changes to the project sponsor in batches for approval 96
Chapter 4 Proactive supplier management project 99
Chapter 4 identifying inherent risks of the project 31st
Chapter 4 major scope changes of investigation should be approved by the initiator first 32nd
Chapter 1 ensures that the cost of collecting metric data does not exceed 33rd of the value
Chapter 1 multiple Estimation Methods 34th
Chapter 4 keeping the latest schedule 35th
Chapter 5 use problem management select the best 36th from a bad alternative
Chapter 1 collection of measurement data that can bring fundamental improvements 37th
Chapter 4 options for risk assessment in the risk plan 38th
Chapter 4 management customer expectations 39th
Chapter 4 tracking overall progress using milestones 40th
Chapter 4 Early error capture 41st
Chapter 2 scope changes shall be approved by the initiator 42nd
Chapter 5 proactively accelerating the project progress by 43rd
Chapter 4 Use a work breakdown structure to identify all jobs 44th
Chapter 2 prepare status reports from the reader's perspective 45th
Chapter 4 risk plans should be updated throughout the project 46th
Chapter 4 the content delivered shall not exceed 47th of users' requirements
Chapter 4 each activity should have a person in charge 48th
Chapter 4 follow the deadline to prevent project loss 49th
Chapter 5 agree on the project metric data in advance 50th
Annual Review 169

Source of this book: China Interactive publishing network