This book takes the Pmbok knowledge system as the framework, systematically introduces the five process groups of project management and 10 areas of knowledge, highlighting the particularity of the software industry, covering psychology, management, organizational behavior and software engineering.
Analyze the characteristics of software project, return to the essence of management, answer management is what, why learn management, how to learn how to manage, how to manage the basic problems. Through success stories, case studies, problem speculation, team games, autonomous tasks, classroom interaction and many other forms, the practice of "left brain planning, right brain management", the inspiration and training of thinking, guide students to independent thinking, self-exploration, understanding the basic idea of project management, Basic principles, core issues and the way. Tightly around the "people" the most active factor, in-depth analysis of the essence of the management of the mind, the balance of the project management of the road, a gathering of well-known IT companies at home and abroad and information construction leading industry mature practices, into the author's years of experience in project management practices and lessons, hoping to make later less detours, less wall, More smoothly integrate into the project team, complete team delivery tasks, and thus develop the basic ability to manage software projects.
This book can be used as a college computer, software engineering and related professional, junior and postgraduate project management course materials, but also for the information work related personnel training or work reference.
* Project management, Quality development and pre-career guidance in one, inspire training thinking, promote the maturity of the mind, cultivate the spirit of cooperation, improve professional quality. * Uphold the concept of "giving the fish" and "giving it to fishes", integrating the management ideas of East and west, emphasizing the unity of knowledge and work, and applying it. * Gather well-known IT companies and advanced information technology industry mature practices, integration of the author's IT industry experience and lessons for more than 20 years. * To clarify the error of "ordinary one soldier does not need to learn management", pointing out the importance of learning point management to long-term career development and complete life. * Comprehensively introduce PMI project management knowledge System, analyze the particularity of software industry, and point out the key elements of software project success. * Instill process management ideas, explore project practice myths, refine project management experience, enhance job objectives, and improve team execution. * From the perspective of psychology, management and organizational behavior, this paper expounds how to manage the most important and active elements of project management-"people". * Guide readers to know themselves, know others, learn to weigh the goals, learn to control themselves, the management of the superior, the management of subordinates, the management of the same level, tube good external. * Success stories, case studies, problem-thinking, team games, autonomous tasks, classroom interaction in a variety of forms, the practice of "left brain planning, right brain management."
The 1th Chapter is sailing 1
1.1 which port is your ship heading to? 11.1.1 wrote the Mission statement 11.1.2 the goal of life 21.1.3 self-cognition and orientation 31.1.4 the pursuit of comprehensive success 41.1.5 growth Trilogy 6
1.2 Marching in the river of time 71.2.15-day Schedule How to arrange 71.2.2 Mr. Zhao three stories 81.2.3 cherish your time the bank 91.2.4 how much time can grasp 111.2.5 murder time of the murderer 131.2.628 Law, the first 141.2.7 to find the time of the owner 161.2.8 Method of Time Management 18
1.3 anchor from our classroomWhat does 1.3.1 School teach you? 211.3.2 Course to your supplies 221.3.3 have you to participate more wonderful 231.3.4 don't take yourself as a student 241.3.5 prepare for the journey 251.3.6 let's go. 27
Chapter 2nd Introduction to Project Management
2.1 Why Study Management2.1.1 Steward and 282.1.2 from technology to management 292.1.3 do the right thing first, and then do the five dimensions of 292.1.4 management 322.1.5 the role and skills of the most popular manager 332.1.6 manager 352.1.7 The management force of a common soldier 372.1. 8 Methods of Learning Management 38
2.2 What is ProjectFeatures of the 2.2.1 Project 392.2.2 project Triangle 402.2.3 Project and operational activities 422.2.4 software Project 43
2.3 Project management is incomplete in the United States2.3.1 Louis 10 Dungeon 462.3.2 Project implementation of the misunderstanding 482.3.3 project management of the balanced way 492.3.4 embarrassing project manager 512.3.5 cat and Mouse story 522.3.6 project management How to manage 532.3.7 project success or failure standard 542.3.8 West Days to learn who contributed the most 542.3.9 development of project Management 55
2.4 People month myth story2.4.1 Tar pits 572.4.2 software industry no silver bullet 582.4.3 Brooks Law 59
Classroom Discussion Tips
thinking after class
The 3rd chapter of Project Process management
3.1 Life cycle3.1.1 Product Life cycle 613.1.2 Project life cycle 63
3.2 Process-centric3.2.1 Project Process 663.2.2 process management 673.2.3 Deming Ring 68
3.3 Project Management process3.3.10 knowledge areas 693.3.25 Large process group 733.3.3 relationship between process groups 77
3.4 CMMI3.4.1 CMMI Origin 793.4.2 maturity level 803.4.3 behavioral characteristics 803.4.4 Process Visibility 823.4.5 critical process field 83
after-school thinking
The 4th chapter of Thinking decision Effect
about 4.1 Brain Division
4.2 Mind Map
4.3 six top thinking cap
4.4 Differences between East and West management
4.5 take elephant to money, cylindrical side
4.6 At the time when its a bit
4.7 Lewis Project management Law 102
4.8 SWOT Analysis 103
4.9 Dual Indicator evaluation 104
after-school thinking
The 5th chapter of the overall management of the project 106
5.1 The division must be famous 1065.1.1 needs a letter of appointment. 1075.1.2 identification of drivers and constraints the 1075.1.3 consensus-building project Charter 108
5.2 Good beginnings are half the success of 1095.2.1 Why to open the start meeting 1095.2.2 when will not open the start-up session 1115.2.3 How to open a good start-up 1135.2.4 start Conference Process 115
5.3 Pre-set not pre-set waste5.3.1 Plan and contingency 1175.3.2 plan for the production of 1195.3.3 Why do you plan 1215.3.4 plan the contents of the 1225.3.5 plan of the strategy 1235.3.6 plan the process of 1255.3.7 out of plan Mire 127
5.4 win in the execution heavy in the detail 1275.4.1 success stems from Executive Force 1275.4.2 detail decision Success 1285.4.3 focus on the principles of 1295.4.4 Statement of Leadership in 1325.4.5 perfect process system monitoring 1335.4.6 implementation key is people 1375.4.7 to own hundred hundred responsible 138
5.5 Tracking Monitoring continuous improvement 1395.5.1 Project Barometer 1405.5.2 Emoticons calendar 1415.5.3 kanban diagram 1415.5.4 burndown chart 1435.5.5 parking lot Figure 145
5.6 Configuration Management--the cornerstone of team collaboration 1455.6.1 Why do I need to configure management 1455.6.2 configuration Management Basic Concepts 1465.6.3 configuration Management Activity 148
after-school thinking
6th. Project Stakeholder Management 153
6.1 Customer First 1546.1.1, the owner is God. 1546.1.2 high-level will not compromise 1556.1.3 look for the most can rely on the 1566.1.4 goal consistent everything good negotiation 1576.1.5 grassroots rebound situation can't control 1586.1.6 enterprise information planning to obey 159
6.2 rely on the organization6.2.1 Leadership in charge of all 1606.2.2 project work by Team 161
6.3 Support for functional departments 1626.3.1 cooperation above the competition 163
6.4 Keep Alert 1646.4.1 industry mines can not step on 1646.4.2 supply risk 1656.4.3 Third party don't take it lightly 1666.4.4 respect exert influence 1676.4.5 opponents make you more mature 167
6.5 168 After the move6.5.1 Role decision responsibility 1686.5.2 the way to solve the problem 170
after-school thinking 175
The 7th chapter of Project Communication Management 176
7.1 Process of communication 1767.1.1 Station biography 1767.1.2 communication process 1787.1.3 Communication Funnel 183
7.2 Direction of communication 1857.2.1 Collective work 1857.2.2 upward communication 1867.2.3 downward communication 1897.2.4 level communication 192
7.3 key points of communication 1947.3.1 Purpose of communication 1947.3.2 communication psychological effect 1957.3.3 communication starting from heart 1977.3.4 body language 1987.3.5 Learn to listen to 2007.3.6 learn questions 2047.3.7 Informal communication 205
7.4 Communication 206 in the project7.4.1 Communication Plan 2067.4.2 Communication form 2077.4.3 meeting Communication 209
7.5 Conflict Management 212The conflict of the 7.5.1 Project 2127.5.2 coping strategy 2147.5.3 Xiao Wang's troubles 215
Classroom Discussion Tips 216
after-school thinking 221
8th Chapter Human Resources Management 222
8.1 Human Nature hypothesis and management 2228.1.1 The human nature hypothesis of the 2228.1.2 Western hypothesis of human nature and system design of 2248.1.3 226
8.2 Personality and Management 228The controversy of 8.2.1 personality certificate 2288.2.2 2308.2.3 type Nine personality 233
8.3 Organization Design 2398.3.1 Typical form of organization 2398.3.2 project team composition 244
8.4 Team Build 2478.4.1 Team Formation Law 2478.4.2 belbin Team role 2488.4.3 Human Resources Plan 2498.4.4 Human Resource Acquisition 2518.4.5 Human Resources Assessment 252
8.5 Team Collaboration 2538.5.1 Common responsibility 2538.5.2 Play your part. 2548.5.3 Project Manager's cultivation 257
8.6 Team Motivation 259Why 8.6.1 to inspire the 2598.6.2 incentive Theory 2608.6.3 Incentive Principles 2648.6.4 Incentive Method 2648.6.5 Developer Incentives 266
8.7 Performance Management 267The power of the 8.7.1 system 2678.7.2 three mice 2678.7.3 performance evaluation 2688.7.4 performance Communication 269
Classroom Discussion Tips
after-school thinking 271
The 9th chapter of Project Scope management 272
9.1 Scope Management Overview 2729.1.1 Project scope structure 2729.1.2 scope management process 273
9.2 Demand Development 2759.2.1 Demand Acquisition 2769.2.2 Demand Analysis 2809.2.3 specification 2819.2.4 requirements Verification 2829.2.5 Li the thought of making mooncakes in the mouth 283
9.3 Scope Definition 2849.3.12 thinking 2849.3.2 Two models 2849.3.3 scope specification 286
9.4 Creating a WBS 2869.4.1 what is WBS 2879.4.2 WBS form 2879.4.3 WBS decomposition 2889.4.4 WBS Dictionary 291
9.5 Range Confirmation 291
9.6 Range Control 292The reason why the 9.6.1 change is out of control 2929.6.2 the change and the invariable of the demand 2939.6.3 change in process management 2969.6.4 realities and best practices 301
Classroom Discussion Tips 302
after-school thinking 304
The 10th chapter of Project cost Management 305
10.1 software Cost 30510.1.1 cost in the eyes of investors 30610.1.2 developers Eye cost 30610.1.3 software Project person monthly cost 307
10.2 Cost Estimation 30810.2.1 timing and process 30810.2.2 scale estimation 30910.2.3 workload estimation 31410.2.4 duration estimate 31810.2.5 cost estimate 319
10.3 Cost Budget10.3.1 Cost budget Composition 32010.3.2 Cost budget method 32110.3.3 cost benchmark Plan 323
10.4 Cost Control 32310.4.1 Cost control content 32410.4.2 earned value analysis 32510.4.3 cost reduction measures 329
Classroom Discussion Tips 331
after-school thinking 332
The 11th chapter of Project Schedule management 333
11.1 Progress Planning Process 33311.1.1 Plan of the basic 33311.1.2 program process 333
11.2 Activity Definition 335
11.3 Event Sort 33611.3.1 Activity Relationship 33611.3.2 Project Network Diagram 337
11.4 Activity Estimation 33811.4.1 Workload estimation 33811.4.2 resources and duration 339
11.5 Schedule Method 34011.5.1 Key Path Method 34011.5.2 Gantt Chart 34211.5.3 plan review technology 34311.5.4 key chain Project Management 34511.5.5 Milestone 352
11.6 Progress Control 35211.6.1 Progress Monitoring 35211.6.2 Progress Compression 35311.6.3 Resource Balance 354
after-school thinking 356
The 12th chapter of Quality Management 357
12.1 Quality Management Overview 357Development of 12.1.1 Quality concept 35712.1.2 What is the development of quality 35812.1.3 Quality Management 35912.1.4 quality cost 36112.1.5 software quality 36312.1.6 software defects 365
12.2 Quality Planning 36612.2.1 quality is the planned 36612.2.2 Quality Management plan 36712.2.3 quality Organization guarantee 368
12.3 Quality Assurance 36912.3.1 QA Work 37012.3.2 QA Working mechanism 37312.3.3 QA Work error 374
12.4 Quality Control 37512.4.1 verification and Validation 37512.4.2 software review 37712.4.3 software testing 38012.4.4 quality control tools 383
12.5 Defect Management 38412.5.1 defect Management Mode 38512.5.2 defect detection and tracking 38512.5.3 defect prevention 388
Classroom Discussion Tips 391
after-school thinking 391
The 13th chapter of Project Risk Management 393
13.1 AWE Risk 39313.1.1 risk is around 39313.1.2 risk stems from self-39413.1.3 risk can be managed 39513.1.4 risk evolves 397
13.2 Risk Identification 39813.2.1 Risk identification Concept 39813.2.2 risk identification Method 39813.2.3 risk Identification Results 407
13.3 Risk Analysis 40713.3.1 Qualitative risk analysis 40713.3.2 Quantitative risk analysis 409
13.4 Planning Risk response 41313.4.1 risk decision factors 41313.4.2 prospect theory and decision-making 41513.4.3 risk coping strategies 417
13.5 Risk Monitoring 420
Classroom Discussion Tips 422
after-school thinking 423
Appendix A project ups and downs record 424A.1 behind 424a.2 drop trough 425a.3 Good news 426a.4 alliances 427a.5 Sleepless night 428a.6 should bid 429a.7 good start 432a.8 start will 433a.9 Small week report 434a.10 reward request 436a.11 Demand Storm 436a.12 snags 438a.13 internal division of Labor 439a.14 development platform 439a.15 441a.16 pull the wind Caifan 441a.17 to an old lake 442a.18 small Zhao return 442a.19 reactive and return to 443a.20 United Co-development 444a.21 Green channel 444a.22 data network 445a.23 expansion 445a.24 remote access 446a.25 Weekly weekly 447a.26 year-end summary 448a.27 contract saw 449a.28 source code where 450a.29 information model 450a.30 left 451a.31 to the new leader 452a.32 online controversy 452a.33 memorabilia 453a.34 extension thinking 453
Appendix B Project Organizational structure example 454B.1 Large-scale project construction principle 454b.2 457b.3 responsibility of large-scale project coping strategies 459 references 463
Introduction of software project management and Quality Development
