Verfügbarkeit: Effective project management

Effective project management: traditional, agile, extreme

Gespeichert in:

Bibliographische Detailangaben
1. Verfasser:	Wysocki, Robert K. (VerfasserIn)
Format:	Buch
Sprache:	English
Veröffentlicht:	Indianapolis, Ind. Wiley 2009
Ausgabe:	5. ed.
Schlagworte:	Projektmanagement Projektorganisation Projektplanung
Online-Zugang:	Inhaltsverzeichnis
Beschreibung:	XXXVII, 734 S. graph. Darst.
ISBN:	9780470423677

Internformat

MARC


LEADER	00000nam a2200000zc 4500
001	BV023748728
003	DE-604
005	20100525
007	t
008	090227s2009 d\|\|\| \|\|\|\| 00\|\|\| eng d
020			\|a 9780470423677 \|9 978-0-470-42367-7
035			\|a (OCoLC)603619124
035			\|a (DE-599)BVBBV023748728
040			\|a DE-604 \|b ger
041	0		\|a eng
049			\|a DE-526 \|a DE-1043 \|a DE-188 \|a DE-2070s
082	0		\|a 658.4/04
084			\|a QP 360 \|0 (DE-625)141869: \|2 rvk
100	1		\|a Wysocki, Robert K. \|e Verfasser \|4 aut
245	1	0	\|a Effective project management \|b traditional, agile, extreme \|c Robert K. Wysocki
250			\|a 5. ed.
264		1	\|a Indianapolis, Ind. \|b Wiley \|c 2009
300			\|a XXXVII, 734 S. \|b graph. Darst.
336			\|b txt \|2 rdacontent
337			\|b n \|2 rdamedia
338			\|b nc \|2 rdacarrier
650	0	7	\|a Projektmanagement \|0 (DE-588)4047441-0 \|2 gnd \|9 rswk-swf
650	0	7	\|a Projektorganisation \|0 (DE-588)4135546-5 \|2 gnd \|9 rswk-swf
650	0	7	\|a Projektplanung \|0 (DE-588)4115649-3 \|2 gnd \|9 rswk-swf
689	0	0	\|a Projektmanagement \|0 (DE-588)4047441-0 \|D s
689	0	1	\|a Projektorganisation \|0 (DE-588)4135546-5 \|D s
689	0	2	\|a Projektplanung \|0 (DE-588)4115649-3 \|D s
689	0		\|5 DE-604
856	4	2	\|m HBZ Datenaustausch \|q application/pdf \|u http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=017297803&sequence=000002&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA \|3 Inhaltsverzeichnis
999			\|a oai:aleph.bib-bvb.de:BVB01-017297803

Datensatz im Suchindex

_version_	1804138799066775552
adam_text	Titel: Effective project management Autor: Wysocki, Robert K. Jahr: 2009 Contents Acknowledgments xi Preface to the Fifth Edition xxxix Introduction xli Part 1 Defining and Using Project Management Process Groups 1 Chapter 1 What Is a Project? 5 Defining a Project 6 Sequence of Activities 6 Unique Activities 6 Complex Activities 7 Connected Activities 7 One Goal 7 Specified Time 7 Within Budget 8 According to Specification 8 What Is a Program? 8 Establishing Temporary Program Offices 9 Establishing Permanent Program Offices 9 Understanding the Scope Triangle 9 Scope 10 Quality 10 Cost 10 Time 11 Resources 11 Envisioning the Scope Triangle as a System in Balance 12 Managing the Creeps 13 Scope Creep 13 Hope Creep 14 xiii Effort Creep 14 Feature Creep 14 Applying the Scope Triangle 15 Problem Resolution 15 Scope Change Impact Analysis 16 The Importance of Classifying Projects 16 Establishing a Rule for Classifying Projects 16 Classification by Project Characteristics 17 Classification by Project Type 18 Putting It All Together 20 Discussion Questions 20 Chapter 2 Understanding The Project Management Process Croups 21 Understanding the Fundamentals of Project Management 22 What Business Situation Is Being Addressed? 23 What Do You Need to Do? 24 What Will You Do? 25 How Will You Do It? 25 How Will You Know You Did It? 25 How Well Did You Do? 26 Denning the Five Process Groups 27 The Scoping Process Group 27 The Planning Process Group 28 The Launching Process Group 28 The Monitoring and Controlling Process Group 29 The Closing Process Group 30 Defining the Nine Knowledge Areas 30 Mapping Knowledge Areas to Process Groups 30 What the Mapping Means 30 How to Use the Mapping 31 Definition of a Project Management Life Cycle 31 Using Process Groups to Define PMLCs 32 A Look Ahead: Mapping Process Groups to Form Complex PMLCs 32 Integration Management 32 Scope Management 32 Time Management 33 Cost Management 33 Quality Management 33 Quality Planning Process 34 Quality Assurance Process 34 Quality Control Process 34 Human Resource Management 34 Projects as Motivation and Development Tools 35 Communications Management 39 Who Are the Project Stakeholders? 39 What Do They Need to Know about the Project? 39 How Should Their Needs Be Met? 40 Risk Management 40 Risk Identification 41 Risk Assessment 42 Risk Mitigation 42 Risk Monitoring 43 Procurement Management 44 Vendor Solicitation 44 Vendor Evaluation 44 Vendor Selection 45 Vendor Contracting 45 Vendor Management 46 Putting It All Together 46 Discussion Questions 47 Chapter 3 How to Scope a Project 49 Using Tools, Templates, and Processes to Scope a Project 50 Managing Client Expectations 51 Wants versus Needs 52 Conducting Conditions of Satisfaction 52 Establishing Clarity of Purpose 55 Specifying Business Outcomes 56 Conducting COS Milestone Reviews 56 Planning and Conducting the Project Scoping Meeting 56 Purpose 56 Attendees 57 Agenda 57 Deliverables 58 Gathering Requirements 58 What Are Requirements? 59 Types of Requirements 60 Functional Requirements 60 Non-Functional Requirements 60 Global Requirements 60 Product and/or Project Constraints 61 Approaches to Gathering Requirements 61 Building the Requirements Breakdown Structure 63 Using the RBS to Choose a Best-Fit PMLC Model 65 Diagramming Business Processes 67 What Is a Business Process? 68 Creating a Business Process Diagram 69 Business Process Diagram Formats 71 Context Diagrams Business Process Work Flow Diagrams 72 Prototyping Your Solution Use Cases 73 Use Case Diagrams Use Case Flow of Events 75 Validating the Business Case ° Outsourcing to Vendors and Contractors 77 Procurement Management Life Cycle Vendor Solicitation 78 Publishing a Request for Information 78 Advertising ° Renting a Targeted List 78 Asking Previous Vendors 7 Attending Trade Shows 7 Preparing and Distributing a Request for Proposal 79 Managing RFP Questions and Responses 80 Responding to Bidder Questions 80 Vendor Evaluation 81 Establishing Vendor Evaluation Criteria 81 Evaluating Responses to the RFP 83 Vendor Selection 83 Vendor Contracting 84 No Award 84 Single Award 84 Multiple Awards 84 Contract Management 85 Types of Contracts 85 Discussion Points for Negotiating the Final Contract 87 Final Contract Negotiation 87 Vendor Management 88 Expectation Setting — Getting Started 88 Monitoring Progress and Performance 89 Transitioning from Vendor to Client 90 Closing Out a Vendor Contract 91 Writing an Effective Project Overview Statement 91 Parts of the POS 93 Stating the Problem or Opportunity 94 Establishing the Project Goal 95 Defining the Project Objectives 97 Identifying Success Criteria 98 Listing Assumptions, Risks, and Obstacles 100 Attachments 102 Chapter 4 Risk Analysis 102 Financial Analyses 102 Gaining Approval to Plan the Project 104 Participants in the Approval Process 105 Approval Criteria 107 Project Approval Status 107 Putting It All Together 107 Discussion Questions 108 How to Plan a Project 109 Tools, Templates, and Processes Used to Plan a Project 111 The Importance of Planning 112 Using Application Software Packages to Plan a Project 113 Determining the Need for a Software Package? 113 Project Planning Tools 114 Sticky Notes 114 Marking Pens 115 Whiteboard 115 How Much Time Should Planning Take? 116 Running the Planning Session 116 Planning and Conducting Joint Project Planning Sessions 117 Planning the JPPS 118 Attendees 119 Facilities 122 Equipment 122 The Complete Planning Agenda 122 Deliverables 123 Conducting the JPPS 124 Building the Work Breakdown Structure 124 Uses for the WBS 126 Thought-Process Tool 127 Architectural-Design Tool 127 Planning Tool 127 Project-Status-Reporting Tool 127 Generating the WBS 128 Top-Down Approach 129 Bottom-Up Approach 130 Using the WBS for Large Projects 131 Iterative Development of the WBS 132 Six Criteria to Test for Completeness in the WBS 132 Status and Completion Are Measurable 133 The Activity Is Bounded 134 The Activity Has a Deliverable 134 Time and Cost Are Easily Estimated 134 Activity Duration Is Within Acceptable Limits 135 Work Assignments Are Independent 135 The Seventh Criteria for Judging Completeness 136 Exceptions to the Completion Criteria Rule 136 Approaches to Building the WBS 137 Noun-Type Approaches 13° Verb-Type Approaches 139 Organizational Approaches I40 Selecting the Best Approach I41 Representing the WBS 141 Estimating Estimating Duration Resource Loading versus Task Duration I4 Variation in Task Duration 148 Six Methods for Estimating Task Duration i49 Extrapolating Based on Similarity to Other Activities 149 Studying Historical Data 149 Seeking Expert Advice 150 Applying the Delphi Technique 150 Applying the Three-Point Technique 151 Applying the Wide-Band Delphi Technique 152 Estimation Life Cycles 152 Estimating Resource Requirements 153 People as Resources 154 Resource Breakdown Structure 155 Determining Resource Requirements 156 Resource Planning 157 Estimating Cost 158 Cost Budgeting 159 Cost Control 160 Constructing the Project Network Diagram 160 Envisioning a Complex Project Network Diagram 161 Benefits to Network-Based Scheduling 161 Building the Network Diagram Using the Precedence Diagramming Method 163 Dependencies 165 Constraints 167 Technical Constraints 167 Management Constraints 169 Interproject Constraints 169 Date Constraints 170 Using the Lag Variable 171 Creating an Initial Project Network Schedule 171 Critical Path 174 Near-Critical Path 176 Analyzing the Initial Project Network Diagram 176 Compressing the Schedule 177 Management Reserve 179 Planning for Project Risk: The Risk Management Life Cycle 180 Risk Identification 181 Risk Categories 181 Candidate Risk Drivers 183 Risk Assessment 183 Static Risk Assessment 184 Dynamic Risk Assessment 185 Risk Mitigation 187 Risk Monitoring and Control 187 Writing an Effective Project Proposal 188 Contents of the Project Proposal 189 Executive Summary 189 Background 189 Objective 189 Overview of the Approach to Be Taken 189 Detailed Statement of the Work 190 Time and Cost Summary 190 Appendices 190 Format of the Project Proposal 190 Gaining Approval to Launch the Project 190 Putting It All Together 191 Discussion Questions 191 Chapter 5 How to Launch a Project 195 Tools, Templates, and Processes Used to Launch a Project 196 Recruiting the Project Team 197 Core Team Members 197 When to Select the Core Team Members 198 Selection Criteria 198 Client Team 201 When to Select the Client Team 201 Selection Criteria 201 Contract Team Members 201 Implications of Adding Contract Team Members 202 Selection Criteria 202 Balancing a Team 203 Assimilating 204 Diverging 204 Accommodating 204 Converging 204 Developing a Team Deployment Strategy 205 Developing a Team Development Plan 205 Conducting the Project Kick-Off Meeting 206 Sponsor-Led Part 206 Project Manager-Led Part 206 Purpose of the Project Kick-Off Meeting 207 Attendees 207 Facilities and Equipment 208 The Working Session Agenda 208 Establishing Team Operating Rules 211 Situations that Require Team Operating Rules 211 Problem Solving 212 Decision Making 214 Conflict Resolution 217 Consensus Building 219 Brainstorming 220 Team Meetings 221 Team War Room 223 Physical Layout 223 Variations 223 Operational Uses 224 Managing Scope Changes 224 The Scope Change Management Process 224 Management Reserve 227 Scope Bank 229 Managing Team Communications 229 Establishing a Communications Model 229 Timing 230 Content 230 Choosing Effective Channels 230 Managing Communication beyond the Team 233 Managing Communications with the Sponsor 233 Upward Communication Filtering and Good News 234 Communicating with Other Stakeholders 235 Assigning Resources 235 Leveling Resources 236 Acceptably Leveled Schedule 238 Resource-Leveling Strategies 239 Utilizing Available Slack 239 Shifting the Project Finish Date 239 Smoothing 240 Alternative Methods of Scheduling Tasks 240 Further Decomposition of Tasks 240 Stretching Tasks 241 Assigning Substitute Resources 241 Cost Impact of Resource Leveling 242 Finalizing the Project Schedule 242 Writing Work Packages 244 Purpose of a Work Package 245 Format of a Work Package 245 Work Package Assignment Sheet 246 Work Package Description Report 247 Putting It All Together 247 Discussion Questions 249 Chapter 6 How to Monitor and Control a Project 251 Tools, Templates, and Processes Used to Monitor and Control a Project 252 Establishing Your Progress Reporting System 253 Types of Project Status Reports 253 Current Period Reports 254 Cumulative Reports 254 Exception Reports 254 Stoplight Reports 254 Variance Reports 255 How and What Information to Update 257 Frequency of Gathering and Reporting Project Progress 259 Variances 259 Positive Variances 259 Negative Variances 260 Applying Graphical Reporting Tools 260 Gantt Charts 260 Stoplight Reports 261 Burn Charts 261 Milestone Trend Charts 261 Earned Value Analysis 265 Integrating Milestone Trend Charts and Earned Value Analysis 270 Integrating Earned Value 271 Integrating Milestone Trend Data 271 Managing the Scope Bank 273 Building and Maintaining the Issues Log 274 Managing Project Status Meetings 275 Who Should Attend Status Meetings? 275 When Are Status Meetings Held? 276 What Is the Purpose of a Status Meeting? 276 What Is the Status Meeting Format? 276 The 15-Minute Daily Status Meeting 277 Problem Management Meetings 278 Defining a Problem Escalation Strategy 278 Project Manager-Based Strategies 279 Resource Manager-Based Strategies 279 Client-Based Strategies 279 The Escalation Strategy Hierarchy 280 Gaining Approval to Close the Project 281 Putting It All Together 281 Discussion Questions 282 Chapter 7 How to Close a Project 283 Tools, Templates, and Processes Used to Close a Project 284 Writing and Maintaining Client Acceptance Procedures 284 Closing a Project 284 Getting Client Acceptance 285 Ceremonial Acceptance 285 Formal Acceptance 285 Installing Project Deliverables 286 Phased Approach 286 Cut-Over Approach 286 Parallel Approach 286 By-Business-Unit Approach 287 Documenting the Project 287 Reference for Future Changes in Deliverables 287 Historical Record for Estimating Duration and Cost on Future Projects, Activities, and Tasks 287 Training Resource for New Project Managers 287 Input for Further Training and Development of the Project Team 288 Input for Performance Evaluation by the Functional Managers of the Project Team Members 288 Conducting the Post-Implementation Audit 289 Writing the Final Report 291 Celebrating Success 292 Putting It All Together 292 Discussion Questions 292 Part II Establishing Project Management Life Cycles and Strategies 295 Chapter 8 Project Management Landscape 297 Assessing Goal and Solution Clarity and Completeness 299 Traditional Project Management (TPM) Approaches 301 Low Complexity 302 Few Scope Change Requests 302 Well-Understood Technology Infrastructure 303 Low Risk 303 Experienced and Skilled Project Teams 303 Plan-driven TPM Projects 303 Agile Project Management (APM) Approaches 304 A Critical Problem Without a Known Solution 305 A Previously Untapped Business Opportunity 306 APM Projects Are Critical to the Organization 306 Meaningful Client Involvement Is Essential 306 APM Projects Use Small Co-located Teams 306 Extreme Project Management (xPM) Approaches 307 The xPM Project Is a Research and Development Project 307 The xPM Project Is Very High Risk 308 Emertxe Project Management (MPx) Approaches 308 A New Technology Without a Known Application 308 A Solution Out Looking for a Problem to Solve 309 Understanding the Complexity/Uncertainty Domain of Projects 309 Requirements 311 Flexibility 312 Adaptability 313 Change 313 Risk vs. the Complexity/Uncertainty Domain 314 Team Cohesiveness vs. the Complexity/Uncertainty Domain 314 Communications vs. the Complexity/Uncertainty Domain 315 Client Involvement vs. the Complexity/Uncertainty Domain 316 The Client s Comfort Zone 317 Ownership by the Client 318 Client Sign-Off 318 Specification vs. the Complexity/Uncertainty Domain 319 Change vs. the Complexity/Uncertainty Domain 320 Business Value vs. the Complexity/Uncertainty Domain 321 Additional Factors Affecting the Choice of Best-Fit PMLC Model 322 Total Cost 322 Duration 322 Market Stability 322 Technology 323 Business Climate 323 Number of Departments Affected 323 Organizational Environment 324 Team Skills and Competencies 324 Introducing Project Management Life Cycles 324 Traditional Project Management Approaches 328 Linear Project Management Life Cycle Model 328 Incremental Project Management Life Cycle Model 329 Agile Project Management Approaches 330 Iterative Project Management Life Cycle Model 331 Adaptive Project Management Life Cycle Model 332 Extreme Project Management Approach 332 Emertxe Project Management Life Cycle Model 334 Recap of PMLC Models 335 Similarities between the PMLC Models 336 Differences between the PMLC Models 336 Choosing the Best-Fit PMLC Model 336 Putting It All Together 338 Discussion Questions 338 Chapter 9 Traditional Project Management 341 What Is Traditional Project Management? 342 Linear Project Management Life Cycle 343 Definition 343 Characteristics 344 Complete and Clearly Denned Goal, Solution, Requirements, Functions, and Features 344 Few Expected Scope Change Requests 345 Routine and Repetitive Activities 345 Benefits of Using Established Templates 348 Strengths 349 Entire Project Is Scheduled at the Beginning of the Project 349 Resource Requirements Are Known from the Start 349 The Linear PMLC Model Does Not Require the Most Skilled Team Members 350 Team Members Do Not Have to Be Co-Located 350 Weaknesses 350 Does Not Accommodate Change Very Well 351 Costs Too Much 351 Takes Too Long before Any Deliverables Are Produced 351 Requires Complete and Detailed Plans 351 Must Follow a Rigid Sequence of Processes 353 Is Not Focused on Client Value 353 When to Use a Linear PMLC Model 353 Variations to the Linear PMLC Model 353 The Rapid Linear PMLC Model 354 Feature-Driven Development Linear PMLC Model 355 Considerations in Choosing a Variation 356 Adapting and Integrating the Tools, Templates, and Processes for Maximum Effectiveness 357 Incremental Project Management life Cycle 357 Definition 358 Characteristics 359 Strengths 359 Produces Business Value Early in the Project 359 Enables You to Better Schedule Scarce Resources 359 Can Accommodate Minor Scope Change Requests Between Increments 360 Offers a Product Improvement Opportunity 360 More Focused on Client Value Than the Linear PMLC Model 360 Weaknesses 360 The Team May Not Remain Intact Between Increments 361 This Model Requires Handoff Documentation Between Increments 361 The Model Must Follow a Defined Set of Processes 361 You Must Define Increments Based on Function and Feature Dependencies Rather Than Business Value 362 You Must Have More Client Involvement Than Linear PMLC Models 363 An Incremental PMLC Model Takes Longer Than the Linear PMLC Model 363 Partitioning the Functions May Be Problematic 363 When to Use an Incremental PMLC 364 Adapting and Integrating the Tools, Templates, and Processes for Maximum Effectiveness 364 Putting It All Together 365 Discussion Questions 367 Chapter 10 Using Critical Chain Project Management 369 What Is the Critical Chain? 370 Variation in Duration: Common Cause versus Special Cause 370 Statistical Validation of the Critical Chain Approach 371 The Critical Chain Project Management Approach 373 Step 1: Creating the Early Schedule Project Network Diagram 373 Step 2: Converting the Early Schedule to the Late Schedule and Adding Resources 374 Step 3: Resolving Resource Conflicts 374 Establishing Buffers 375 Denning Buffers 375 Types of Buffers 376 Project Buffers 376 Feeding Buffers 376 Resource Buffers 376 Other Buffers 376 Using Buffers 377 Managing Buffers 377 Penetration into the First Third of the Buffer 378 Penetration into the Middle Third of the Buffer 378 Penetration into the Final Third of the Buffer 378 Track Record of Critical Chain Project Management 380 Putting It All Together 381 Discussion Questions 381 Chapter 11 Agile Project Management 383 What Is Agile Project Management? 385 Implementing APM Projects 386 Fully Supported Production Versions of Partial Solutions Are Released to the End User Quarterly or Semi-Annually 386 Intermediate Versions Are Released to a Focus Group Every 2-4 Weeks 387 Co-Located APM Project Teams 387 Cross-Project Dependencies 388 Project Portfolio Management 388 Iterative Project Management Life Cycle 390 Definition of the Iterative PMLC Model 390 Most of the Solution Is Clearly Known 391 Likely to be Multiple Scope Change Requests 391 Concern about Lack of Client Involvement 392 Scoping Phase of an Iterative PMLC Model 392 Planning Phase of an Iterative PMLC Model 392 The Complete Plan for Building the Known Solution 393 The Partial Plan for the High-Priority Functions 393 Launching Phase of an Iterative PMLC Model 394 Monitoring and Controlling Phase of an Iterative PMLC Model 394 Closing Phase of an Iterative PMLC Model 395 Characteristics 395 The Solution Is Known, But Not to the Expected Depth 395 Often Uses Iconic or Simulated Prototypes to Discover the Complete Solution 395 Strengths 395 Client Reviews Current Partial Solution for Improvement 396 Can Process Scope Changes Between Iterations 396 Adaptable to Changing Business Conditions 396 Weaknesses 396 Requires a More Actively Involved Client Than TPM projects 396 Requires Co-Located Teams 397 Difficult to Implement Intermediate Solutions 397 Final Solution Cannot Be Defined at the Start of the Project 397 Types of Iterative PMLC Models 397 Prototyping PMLC Model 398 Rational Unified Process (RUP) 400 When to Use an Iterative PMLC Model 403 Intuitive to the Client 403 Easily Engages the Client 403 Immediate Feedback on the Effect of Solution Change 404 Tolerant of Assessing and Evaluating the Impact of Alternatives 404 No Fixed Deadline for Completion 404 Adaptive Project Management Life Cycle 404 Definition 404 Scoping Phase of an Adaptive PMLC Model 406 Planning Phase of an Adaptive PMLC Model 406 Launching Phase of an Adaptive PMLC Model 407 Monitoring and Controlling Phase of an Adaptive PMLC Model 407 Closing Phase of an Adaptive PMLC Model 408 Characteristics 408 Iterative Structure 409 Just-in-Time Planning 409 Critical Mission Projects 409 Thrives on Change through Learning and Discovery 409 Strengths 409 Does Not Waste Time on Non-Value-Added Work 410 Avoids All Management Issues Processing Scope Change Requests 410 Does Not Waste Time Planning Uncertainty 410 Provides Maximum Business Value Within the Given Time and Cost Constraints 410 Weaknesses of the Adaptive PMLC Model 411 Must Have Meaningful Client Involvement 411 Cannot Identify Exactly What Will Be Delivered at the End of the Project 411 Types of Adaptive PMLC Models 411 Adaptive Software Development (ASD) 412 Adaptive Project Framework 414 Client Situation 444 Goal 444 Objectives 444 Solution 444 Phase I: Needs Analysis 445 Phase II: PMM High-level Design 445 Phase HI: PMM Detailed Design and Documentation 445 Phase IV: PMM Implementation 446 Phase V: PMM Training Program 446 Business Value and Selected Success Criteria 447 Roles and Responsibilities 447 Project Schedule 448 Dynamic Systems Development Method (DSDM) 449 Scrum 450 When to Use an Adaptive PMLC Model 454 Has the Client Had Successful Adaptive Project Experience Before? 454 Will this First-Time Adaptive Project Client Be Meaningfully Involved? 455 Has the Client Appointed a Qualified Co-Project Manager? 456 Adapting and Integrating the APM Toolkit 456 Scoping the Next Iteration/Cycle 456 Planning the Next Iteration/Cycle 457 Launching the Next Iteration/Cycle 458 Monitoring and Controlling the Next Iteration/Cycle 458 Closing the Next Iteration/Cycle 459 Deciding to Conduct the Next Iteration/Cycle 459 Closing the Project 459 Putting It All Together 460 Discussion Questions 460 Chapter 12 Extreme Project Management 463 What Is Extreme Project Management? 464 Extreme Project Management Life Cycle 464 Definition 464 Characteristics 465 High Speed 465 High Change 465 High Uncertainty 466 Strengths 466 Keeps Options Open as Late as Possible 466 Offers an Early Look at a Number of Partial Solutions 466 Weaknesses 466 May Be Looking for Solutions in All the Wrong Places 467 No Guarantee That Any Business Value Will Result from the Project Deliverables 467 INSPIRE Extreme PMLC Model 467 INitiate 469 SPeculate 473 Incubate 477 REview 479 What Is Emertxe Project Management? 480 The Emertxe Project Management Life Cycle 481 When to Use an Emertxe PMLC Model 481 Research and Development Projects 481 Problem-Solution Projects 481 Using the Tools, Templates, and Processes for Maximum xPM Effectiveness 482 Scoping the Next Phase 482 Planning the Next Phase 483 Launching the Next Phase 484 Monitoring and Controlling the Next Phase 484 Closing the Phase 485 Deciding to Conduct the Next Phase 485 Closing the Project 485 Putting It All Together 485 Discussion Questions 485 Part 111 Building an Effective Project Management Infrastructure 489 Chapter 13 Establishing and Maturing a Project Support Office 491 Background of the Project Support Office 492 Defining a Project Support Office 493 Temporary or Permanent Organizational Unit 494 Portfolio of Services 494 Specific Portfolio of Projects 495 Naming the Project Support Office 496 Establishing Your PSO s Mission 497 Framing PSO Objectives 498 Exploring PSO Support Functions 498 Project Support 499 Consulting and Mentoring 499 Methods and Standards 500 Software Tools 501 Training 502 Staffing and Development 503 Project Manager Resources 504 Project Team Members 504 Selecting PSO Organizational Structures 505 Virtual versus Real 505 Proactive versus Reactive 506 Temporary versus Permanent 506 Program versus Projects 506 Enterprise versus Functional 507 Hub-and-Spoke 507 Understanding the Organizational Placement of the PSO 507 Determining When You Need a Project Support Office 509 The Standish Group Report 509 User Involvement 510 Executive Management Support 511 Clear Business Objectives 511 Agile Optimization 512 Emotional Maturity 512 Project Management Expertise 512 Financial Management 513 Skilled Resources 513 Formal Methodology 513 Tools and Infrastructure 513 Spotting Symptoms That You Need a PSO 514 Establishing a PSO 516 PSO Stages of Maturity Growth 516 Level 1: Initial 517 Level 2: Repeatable 517 Level 3: Defined 517 Level 4: Managed 518 Level 5: Optimized 518 Planning a PSO 518 ThePOS 518 Planning Steps 521 Facing the Challenges of Implementing a PSO 528 Speed and Patience 529 Leadership from the Bottom Up 529 A Systems Thinking Perspective 529 Enterprise-Wide Systems 529 Knowledge Management 529 Learning and Learned Project Organizations 530 Open Communications 530 Putting It All Together 530 Discussion Questions 530 Chapter 14 Establishing and Managing a Project Portfolio Management Process 533 Introduction to Project Portfolio Management 534 Portfolio Management Concepts 534 What Is a Portfolio Project? 534 What Is a Project Portfolio? 535 What Is Project Portfolio Management? 536 The Project Portfolio Management Life Cycle 536 ESTABLISH a Portfolio Strategy 538 Strategic Alignment Model 539 Boston Consulting Group Products/Services Matrix 541 Project Distribution Matrix 542 Growth versus Survival Model 544 Project Investment Categories Model 544 Choosing Where to Apply These Models 545 EVALUATE Project Alignment to the Portfolio Strategy 546 PRIORITIZE Projects and Hold Pending Funding Authorization 546 Forced Ranking 547 Q-Sort 548 Must-Do, Should-Do, Postpone 548 Criteria Weighting 549 Paired Comparisons Model 550 Risk/Benefit 551 SELECT a Balanced Portfolio Using the Prioritized List 553 Balancing the Portfolio 553 Strategic Alignment Model and Weighted Criteria 554 Project Distribution Matrix and Forced Ranking Model 556 Graham-Englund Selection Model and the Risk/Benefit Matrix 558 Balancing Using Partial Funding or Staffing of Projects 562 MANAGE the Active Projects 562 Project Status 563 The Role of the Project Manager 564 Reporting Portfolio Performance 564 Schedule Performance Index and Cost Performance Index 565 SPI and CPI Trend Charts 565 Spotting Out-of-Control Situations 565 Closing Projects in the Portfolio 569 Attainment of Explicit Business Value 569 Lessons Learned 570 Roles and Responsibilities of the PSO in Portfolio Management 570 Project Sponsor 570 Portfolio Manager 571 Proposal Intake and Evaluation 571 Project Prioritization 571 Selection Support to the Portfolio Manager 571 Monitoring and Reporting to the Portfolio Manager 571 Facilitate Project Review Sessions 571 Preparing Your Project for Submission to the Portfolio Management Process 572 A Revised Project Overview Statement 572 Parts of the POS 573 POS Attachments 575 A Two-Step Submission Process 576 A New Submission Process 576 Agile Project Portfolio Management 578 Putting It All Together 580 Discussion Questions 580 Chapter 15 Establishing and Managing a Continuous Process Improvement Program 583 Understanding Project Management Processes and Practices 584 The Project Management Process 585 How Was It Developed? 585 How Complete Is It? 585 How Is It Documented? 585 How Is It Supported? 586 How Is It Updated? 586 The Practice of the Project Management Process 586 Are All Project Managers Required to Use the Process? 586 Can Project Managers Substitute Other Tools, Templates, and Processes as They Deem Appropriate? 587 Is There a Way to Incorporate Best Practices into the Practice of the Project Management Process? 587 How Are Project Managers Monitored for Compliance? 587 How Are Corrective Action Steps Taken to Correct for Noncompliance? 587 How Are Project Manager Practices Monitored for Best Practices? 587 Defining Process and Practice Maturity 588 Level 1: Ad hoc or Informal 589 Level 2: Documented Processes 589 Level 3: Documented Processes That Everyone Uses 589 Level 4: Integrated into Business Processes 590 Level 5: Continuous Improvement 590 Measuring Project Management Process and Practice Maturity 591 The Process Quality Matrix and Zone Map 591 What Process Has Been Defined So Far? 595 Step 1: Define the Process 596 Step 2: Validate and Finalize the PQM 596 Step 3: Establish Correlations 596 Step 4: Establish Metrics 596 Step 5: Assess Project Managers against the PMMA 597 Step 6: Assess Maturity Levels 597 Step 7: Plot Results on the PQM Zone Map 597 Using the Continuous Process Improvement Model 597 Phase 1: Foundation 597 Develop Mission/Vision Statement 598 Identify CSFs 599 Identify Business Processes 599 Relate CSFs to Business Processes 599 Phase 2: Assessment and Analysis 599 Conduct Gap Analysis 600 Select Knowledge Area or PM Process 600 Identify Improvement Opportunities 600 Analyze Improvement Opportunities 601 Phase 3: Improvement Initiatives 601 Define the Project Scope 602 Plan Project Activities 602 Schedule Project Work 602 Monitor Project Progress 602 Phase 4: Check Results 602 Defining Roles and Responsibilities of the PSO 603 Realizing the Benefits of Implementing a CPIM 603 Applying CPIM to Business Processes 604 Characteristics of Business Processes 605 Process Effectiveness 605 Process Efficiency 606 Streamlining Tools 606 Watching Indicators of Needed Improvement 609 Documenting the As Is Business Process 609 Envisioning the To Be State 610 Defining the Gap between As Is and To Be 610 Defining a Business Process Improvement Project 610 Using Process Improvement Tools, Templates, and Processes 611 Fishbone Diagrams and Root Cause Analysis 612 Control Charts 615 Flowcharting 615 Histograms 616 Pareto Analysis 617 Run Charts 618 Scatter Diagrams 619 Force Field Analysis 620 Trigger Values 622 Putting It All Together 622 Discussion Questions 623 Basic Flow of Placing an Order 623 Part IV Managing the Realities of Projects 625 Chapter 16 Managing Distressed Projects 627 What Is a Distressed Project? 628 Why Projects Become Distressed or Fail 629 Poor, Inadequate, or No Requirements Documentation 629 Inappropriate or Insufficient Sponsorship 629 Complexity of Requirements Not Recognized 629 Unwillingness to Make Tough Decisions 630 Lag Time between Project Approval and Kick-Off 630 No Plan Revision after Significant Cuts in Resources or Time 630 Estimates Done with Little Planning or Thought 631 Overcommitment of Staff Resources 631 Inconsistent Client Sign-Off 631 No Credibility in the Baseline Plan 631 Unmanageable Project Scope 631 Managing Distressed Projects 632 Prevention Management Strategies 632 Using Tools, Templates, and Processes to Prevent Distressed Projects 632 Requirements Gathering 633 WBS Construction 634 Dynamic Risk Management Process 634 Scope Change Management Process 635 Milestone Trend Charts 636 Earned Value Analysis 637 Intervention Management Strategies 639 Analyze Current Situation: Where Are We? 639 Revise Desired Goal: Where Can We Go? 644 Evaluate Options: How Can We Get There? 647 Generate Revised Plan: How Will We Get There? 649 Roles and Responsibilities of the PSO with Respect to Distressed Projects 650 Analyzing the Current Situation 652 Revising the Desired Goal 652 Evaluating the Options 652 Generating the Revised Plan 653 Putting It All Together 653 Discussion Questions 653 Chapter 17 Managing Multiple Team Projects 655 What Is a Multiple Team Project? 655 Challenges to Managing a Multiple Team Project 657 Working with Fiercely Independent Team Cultures 658 Working with Different Team Processes 658 Accommodating Competing Priorities 659 Communicating within the Team Structure 659 Establishing a Project Management Structure 659 Establishing One Project Management Life Cycle 659 Building an Integrated Project Plan and Schedule 660 Defining a Requirements Gathering Approach 660 Establishing a Scope Change Management Process 661 Defining the Team Meeting Structure 661 Establishing Manageable Reporting Levels 661 Sharing Resources across Teams 662 Searching Out Your Second 662 Classifying Multiple Team Projects 662 Two Teams 662 Update or Enhance and Global 663 New and Global 663 Multiple Teams 663 Update or Enhance 663 Update or Enhance and Global 664 New 664 New and Global 664 Project Office Structure 664 Project Office Characteristics 665 Organize and Manage the Entire Project 666 Develop the High-Level Project Plan in Collaboration with Team Managers 666 Integrate and Coordinate the Project Plans of Each Team 666 Maintain the Overall Project Schedule 666 Monitor and Manage Resource Use 666 Prepare and Distribute Project Status Reports 666 Plan and Conduct Team Meetings 667 Process Scope Change Requests 667 Solve Problems Escalated from the Individual Project Teams 667 Negotiate and Resolve Problems between Teams 667 Project Office Strengths 667 Coordinates the Work of Several Independent Teams 667 Scales to Large Projects 668 Managed from a Single Integrated Plan 668 Integrated Resource Management Control 668 Allows Teams to Maintain Their Practices 668 Project Office Weaknesses 669 Requires Management Across Disparate Practices 669 Requires Team Members to Manage Competing Priorities 669 May Involve a Cumbersome Scope Change Management Process 669 When to Use a PO 670 Core Team Structure 670 Core Team Characteristics 670 Advise Each Team on Technical Matters 671 Provide Subject Matter Expertise on Enterprise Systems and Processes ^ Support Each Team as Requested and as Needed 673 Collaborate with and Advise the CT Manager as Requested 673 Negotiate and Help Resolve Inter-Team Problems 673 Core Team Strengths 673 Enables the CT Manager to Select CT Members 674 Provides the Best Available Advice to the CT Manager 674 Coordinates the Work of Several Teams 674 Lends Support and Credibility to the Decisions of the CT Manager 674 Assigns Core Team Members 100 Percent to This Project 674 Takes Advantage of the Most Experienced SMEs 675 Allows Teams to Retain Their Business Unit Practices 675 Core Team Weaknesses 675 May Not Scale to the Larger Projects 675 Does Not Necessarily Integrate Individual Team Plans 676 Must Manage across Disparate Practices 676 How to Deal with Divided Loyalties 676 Repeatedly Uses the Same SMEs 676 When to Use a CT 676 Super Team Structure 677 Super Team Characteristics 678 Organize and Manage the Project 679 Develop the Project Plan 680 Maintain the Overall Project Schedule 680 Monitor and Manage Resource Utilization 680 Prepare and Distribute Project Status Reports 680 Plan and Conduct Team Meetings 680 Process Scope Change Requests 680 Super Team Strengths 681 Manages from a Single Integrated Source 681 Scales to Large Projects 681 Integrates Resource Management Control 681 Standardizes on a Set of Tools, Templates, and Processes 681 Super Team Weaknesses 682 The Difficulty in Establishing Standardization 682 Team Members Have to Decide among Competing Priorities 682 When to Use an ST 682 Putting It All Together 683 Discussion Questions 684 Epilogue: Putting It All Together Finally 685 What Business Situation Is Being Addressed? 686 What Do You Need To Do? 686 Experience Acquisition 686 On-the-job Training 687 Off-the-job Training 687 Professional Activities 687 What Will You Do? 688 How Will You Do It? 688 How Will You Know You Did It? 688 How Well Did You Do? 688 Where Do You Go from Here? — A New Idea to Consider 688 The PM / BA Position Family 689 Team Member 692 Task Manager 692 Associate Manager 693 Senior Manager 694 Program Manager 695 Director 696 Using the PM/BA Landscape for Professional Development 697 What Might a Professional Development Program Look Like? 697 Experience Acquisition 698 On-the-Job Training 699 Off-the-job Training 699 Professional Activities 699 Using the PDP 700 Career Planning Using the BA/PM Landscape 701 Putting It All Together 703 Appendix A What s on the Web Site? 705 Appendix B Bibliography 707 Index 719
any_adam_object	1
author	Wysocki, Robert K.
author_facet	Wysocki, Robert K.
author_role	aut
author_sort	Wysocki, Robert K.
author_variant	r k w rk rkw
building	Verbundindex
bvnumber	BV023748728
classification_rvk	QP 360
ctrlnum	(OCoLC)603619124 (DE-599)BVBBV023748728
dewey-full	658.4/04
dewey-hundreds	600 - Technology (Applied sciences)
dewey-ones	658 - General management
dewey-raw	658.4/04
dewey-search	658.4/04
dewey-sort	3658.4 14
dewey-tens	650 - Management and auxiliary services
discipline	Wirtschaftswissenschaften
edition	5. ed.
format	Book
fullrecord	<?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>01497nam a2200385zc 4500</leader><controlfield tag="001">BV023748728</controlfield><controlfield tag="003">DE-604</controlfield><controlfield tag="005">20100525 </controlfield><controlfield tag="007">t</controlfield><controlfield tag="008">090227s2009 d\|\|\| \|\|\|\| 00\|\|\| eng d</controlfield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9780470423677</subfield><subfield code="9">978-0-470-42367-7</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(OCoLC)603619124</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)BVBBV023748728</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-604</subfield><subfield code="b">ger</subfield></datafield><datafield tag="041" ind1="0" ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="049" ind1=" " ind2=" "><subfield code="a">DE-526</subfield><subfield code="a">DE-1043</subfield><subfield code="a">DE-188</subfield><subfield code="a">DE-2070s</subfield></datafield><datafield tag="082" ind1="0" ind2=" "><subfield code="a">658.4/04</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">QP 360</subfield><subfield code="0">(DE-625)141869:</subfield><subfield code="2">rvk</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Wysocki, Robert K.</subfield><subfield code="e">Verfasser</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">Effective project management</subfield><subfield code="b">traditional, agile, extreme</subfield><subfield code="c">Robert K. Wysocki</subfield></datafield><datafield tag="250" ind1=" " ind2=" "><subfield code="a">5. ed.</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">Indianapolis, Ind.</subfield><subfield code="b">Wiley</subfield><subfield code="c">2009</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">XXXVII, 734 S.</subfield><subfield code="b">graph. Darst.</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="b">n</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="b">nc</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Projektmanagement</subfield><subfield code="0">(DE-588)4047441-0</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Projektorganisation</subfield><subfield code="0">(DE-588)4135546-5</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Projektplanung</subfield><subfield code="0">(DE-588)4115649-3</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="689" ind1="0" ind2="0"><subfield code="a">Projektmanagement</subfield><subfield code="0">(DE-588)4047441-0</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2="1"><subfield code="a">Projektorganisation</subfield><subfield code="0">(DE-588)4135546-5</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2="2"><subfield code="a">Projektplanung</subfield><subfield code="0">(DE-588)4115649-3</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2=" "><subfield code="5">DE-604</subfield></datafield><datafield tag="856" ind1="4" ind2="2"><subfield code="m">HBZ Datenaustausch</subfield><subfield code="q">application/pdf</subfield><subfield code="u">http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=017297803&sequence=000002&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA</subfield><subfield code="3">Inhaltsverzeichnis</subfield></datafield><datafield tag="999" ind1=" " ind2=" "><subfield code="a">oai:aleph.bib-bvb.de:BVB01-017297803</subfield></datafield></record></collection>
id	DE-604.BV023748728
illustrated	Illustrated
indexdate	2024-07-09T21:33:55Z
institution	BVB
isbn	9780470423677
language	English
oai_aleph_id	oai:aleph.bib-bvb.de:BVB01-017297803
oclc_num	603619124
open_access_boolean
owner	DE-526 DE-1043 DE-188 DE-2070s
owner_facet	DE-526 DE-1043 DE-188 DE-2070s
physical	XXXVII, 734 S. graph. Darst.
publishDate	2009
publishDateSearch	2009
publishDateSort	2009
publisher	Wiley
record_format	marc
spelling	Wysocki, Robert K. Verfasser aut Effective project management traditional, agile, extreme Robert K. Wysocki 5. ed. Indianapolis, Ind. Wiley 2009 XXXVII, 734 S. graph. Darst. txt rdacontent n rdamedia nc rdacarrier Projektmanagement (DE-588)4047441-0 gnd rswk-swf Projektorganisation (DE-588)4135546-5 gnd rswk-swf Projektplanung (DE-588)4115649-3 gnd rswk-swf Projektmanagement (DE-588)4047441-0 s Projektorganisation (DE-588)4135546-5 s Projektplanung (DE-588)4115649-3 s DE-604 HBZ Datenaustausch application/pdf http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=017297803&sequence=000002&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA Inhaltsverzeichnis
spellingShingle	Wysocki, Robert K. Effective project management traditional, agile, extreme Projektmanagement (DE-588)4047441-0 gnd Projektorganisation (DE-588)4135546-5 gnd Projektplanung (DE-588)4115649-3 gnd
subject_GND	(DE-588)4047441-0 (DE-588)4135546-5 (DE-588)4115649-3
title	Effective project management traditional, agile, extreme
title_auth	Effective project management traditional, agile, extreme
title_exact_search	Effective project management traditional, agile, extreme
title_full	Effective project management traditional, agile, extreme Robert K. Wysocki
title_fullStr	Effective project management traditional, agile, extreme Robert K. Wysocki
title_full_unstemmed	Effective project management traditional, agile, extreme Robert K. Wysocki
title_short	Effective project management
title_sort	effective project management traditional agile extreme
title_sub	traditional, agile, extreme
topic	Projektmanagement (DE-588)4047441-0 gnd Projektorganisation (DE-588)4135546-5 gnd Projektplanung (DE-588)4115649-3 gnd
topic_facet	Projektmanagement Projektorganisation Projektplanung
url	http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=017297803&sequence=000002&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA
work_keys_str_mv	AT wysockirobertk effectiveprojectmanagementtraditionalagileextreme

Verfügbarkeit

Es ist kein Print-Exemplar vorhanden.

Fernleihe Bestellen Achtung: Nicht im THWS-Bestand! Inhaltsverzeichnis

MARC

Datensatz im Suchindex

Es ist kein Print-Exemplar vorhanden.

Ähnliche Einträge