Atjaunināt sīkdatņu piekrišanu

Project Manager's Guide to Mastering Agile: Principles and Practices for an Adaptive Approach 2nd edition [Mīkstie vāki]

(Agile Project Management Academy)
  • Formāts: Paperback / softback, 608 pages, height x width x depth: 234x188x36 mm, weight: 998 g
  • Izdošanas datums: 30-Mar-2023
  • Izdevniecība: John Wiley & Sons Inc
  • ISBN-10: 1119931355
  • ISBN-13: 9781119931355
Citas grāmatas par šo tēmu:
  • Mīkstie vāki
  • Cena: 70,97 €
  • Grāmatu piegādes laiks ir 3-4 nedēļas, ja grāmata ir uz vietas izdevniecības noliktavā. Ja izdevējam nepieciešams publicēt jaunu tirāžu, grāmatas piegāde var aizkavēties.
  • Daudzums:
  • Ielikt grozā
  • Piegādes laiks - 4-6 nedēļas
  • Pievienot vēlmju sarakstam
  • Formāts: Paperback / softback, 608 pages, height x width x depth: 234x188x36 mm, weight: 998 g
  • Izdošanas datums: 30-Mar-2023
  • Izdevniecība: John Wiley & Sons Inc
  • ISBN-10: 1119931355
  • ISBN-13: 9781119931355
Citas grāmatas par šo tēmu:
"Agile project management is an iterative approach to delivering a project throughout its life cycle. Agile life cycles are composed of several iterations or incremental steps towards the completion of a project. Iterative approaches are frequently used in software development projects to promote velocity and adaptability since the benefit of iteration is that you can adjust as you go along rather than following a linear path. One of the aims or an agile or iterative approach is to release benefits throughout the process rather than only at the end. Agile projects should exhibit values and behaviors of trust, flexibility, empowerment, and collaboration"--

THE PROJECT MANAGER’S GUIDE TO MASTERING AGILE

Updated guide to Agile methodologies, with real-world case studies and valuable frameworks for project managers moving to Agile

The Project Manager’s Guide to Mastering Agile helps project managers who are faced with the challenge of adapting their project management approach to an Agile environment, showing how these approaches can work jointly to improve project outcomes in any project, with discussion topics and real-world case studies that facilitate hands-on learning. It also provides project managers with the fundamental knowledge to take a leadership role in working with companies to develop a well-integrated, enterprise-level Agile Project Management approach to fit their business.

The original edition of this book has been very successful and is used as a graduate-level textbook in several universities. This new edition builds on the success of the original edition and includes updated content from the latest PMBOK Guide, updated sections on stakeholder management, value-driven delivery, adaptive planning, and distributed project management, with an all-new chapter on Hybrid project management. It also includes new case studies on applying an Agile Hardware Development at Tesla and Project Management in a non-software environment.

Sample topics covered in The Project Manager’s Guide to Mastering Agile include:

  • Bridging the chasm in project management philosophies, impact on the project management profession, evolution of Agile and Waterfall, and learning to see Agile and traditional plan-driven project management as complementary to each other rather than competitive
  • The roots of Agile and understanding Agile at a deeper level including the Agile manifesto from 2001, adapting an Agile approach to fit a business, and Scrum overview, roles, framework, principles, and values
  • Time-boxing, Kanban, and theory of constraints, Agile estimation overview and estimation practices, and velocity and burn-down/burn-up charts
  • Scaling Agile to an enterprise level, including challenges, obstacles to overcome, implementation considerations, management practices, and enterprise-level Agile transformations

With comprehensive, accessible, and highly practical coverage of Agile, a leading project management platform, The Project Manager’s Guide to Mastering Agile is a highly valuable resource for professional project managers, students studying project management, and those studying for PMI’s Agile Certified Practitioner Certification (PMI-ACP).

Preface xvii
Acknowledgments xxiii
1 Introduction to Agile Project Management
1(24)
The Chasm in Project Management Philosophies
2(1)
What's Driving These Changes?
3(1)
The Impact on the Project Management Profession
4(2)
The Evolution of Agile and Waterfall
6(1)
Definition of Waterfall
7(1)
Definition of Agile
7(1)
Comparison of Predictive (Plan-Driven) and Adaptive (Value-Driven) Approaches
8(2)
Which Approach Is Better?
10(1)
The Evolution of the Project Management Profession
11(1)
The Early History of Project Management
12(1)
Transformation of the Project Management Profession
13(1)
What's Driving This Change, and Why Now?
14(3)
Agile Project Management Benefits
17(2)
Summary of Key Points
19(1)
Discussion Topics
20(1)
Notes
21(4)
Part 1 Fundamentals of Agile
2 Agile History and the Agile Manifesto
25(18)
Agile Early History
25(1)
Dr. Winston Royce and the Waterfall Model (1970)
26(2)
Early Iterative and Incremental Development Methods (Early 1970s)
28(1)
Further Evolution of Iterative and Incremental Development (Mid-to-Late 1970s)
28(1)
Early Agile Development Methods (1980s and 1990s)
29(1)
Agile Manifesto (2001)
30(1)
Agile Manifesto Values
30(3)
Agile Manifesto Principles
33(6)
Summary of Key Points
39(1)
Discussion Topics
40(1)
Notes
41(2)
3 Scrum Overview
43(26)
Scrum Framework
44(1)
Sprints
45(1)
Product Backlog
45(2)
Scrum Meetings
47(3)
Scrum Roles
50(1)
Product Owner Role
50(1)
Scrum Master Role
51(2)
Team Role
53(1)
Scrum Values
54(1)
Commitment and Focus
55(1)
Openness
56(1)
Respect
57(1)
Courage
58(1)
General Scrum/Agile Principles
58(1)
Variability and Uncertainty
59(1)
Prediction and Adaptation
60(1)
Validated Learning
61(1)
Work in Progress
62(1)
Progress
63(1)
Performance
64(2)
Summary of Key Points
66(1)
Discussion Topics
66(1)
Notes
67(2)
4 Agile Planning, Requirements, and Product Backlog
69(26)
Agile Planning Practices
69(1)
Planning Strategies
70(2)
Capacity-Based Planning
72(1)
Spikes
73(1)
Progressive Elaboration
74(1)
Value-Based Functional Decomposition
74(1)
Agile Requirements Practices
75(1)
The Role of a Business Analyst in an Agile Project
75(2)
"Just Barely Good Enough"
77(1)
Differentiating Wants from Needs and the "Five Whys"
77(1)
MoSCoW Technique
78(1)
User Personas and User Stories
79(1)
User Personas
79(1)
User Stories
80(2)
Epics
82(1)
Product Backlog
83(1)
What Is a Product Backlog?
83(1)
Product Backlog Grooming (Refinement)
84(2)
Summary of Key Points
86(2)
Discussion Topics
88(1)
Notes
89(6)
Part 2 Agile Project Management Overview
5 Agile Development, Quality, and Testing Practices
95(14)
Agile Software Development Practices
96(1)
Code Refactoring
96(1)
Continuous Integration
97(1)
Pair Programming
98(1)
Test-Driven Development
99(1)
Extreme Programming (XP)
100(1)
Agile Quality Management Practices
100(1)
Key Differences in Agile Quality Management Practices
100(1)
Definition of "Done"
101(1)
The Role of Quality Assurance (QA) Testing in an Agile Project
102(1)
Agile Testing Practices
103(1)
Concurrent Testing
103(1)
Acceptance Test-Driven Development
103(1)
Repeatable Tests and Automated Regression Testing
104(1)
Value-Driven and Risk-Based Testing
104(1)
Summary of Key Points
104(3)
Discussion Topics
107(2)
6 Time-Boxing, Kanban, and Theory of Constraints
109(16)
The Importance of Flow
111(1)
Small Batch Sizes
111(1)
Just-In-Time Production
111(1)
Concurrent Processing
111(1)
Time-Boxing
112(1)
Time-Boxing Advantages
112(1)
Additional Time-Boxing Productivity Advantages
113(1)
The Kanban Process
113(1)
Push and Pull Processes
114(1)
What Is a Kanban Process?
115(1)
Differences Between Scrum and Kanban
116(1)
Work-In-Process (WIP) Limits in Kanban
117(1)
Kanban Boards
118(1)
Theory of Constraints
119(3)
Summary of Key Points
122(1)
Discussion Topics
123(1)
Notes
123(2)
7 Agile Estimation
125(18)
Agile Estimation Overview
125(1)
What's Different about Agile Estimation?
125(2)
Developing an Estimation Strategy
127(1)
Management of Uncertainty
127(2)
Agile Estimation Practices
129(1)
Levels of Estimation
129(1)
Story Points
130(3)
Other Relative Sizing Techniques
133(1)
What Is Planning Poker?
134(1)
More Sophisticated Agile Estimation Techniques
134(1)
Velocity and Burn-Down/Burn-Up Charts
135(1)
Velocity
135(1)
Burn-Down Charts
135(2)
Burn-Up Charts
137(1)
Summary of Key Points
138(1)
Discussion Topics
139(2)
Notes
141(2)
8 Agile Project Management Role
143(20)
Agile Project Management Shifts in Thinking
145(1)
Emphasis on Maximizing Value Versus Control
145(2)
Emphasis on Empowerment and Self-Organization
147(1)
Limited Emphasis on Documentation
148(1)
Managing Flow Instead of Structure
149(1)
Potential Agile Project Management Roles
149(1)
Making Agile Work at a Team Level
150(1)
Hybrid Agile Project Role
151(1)
Enterprise-Level Implementation
152(3)
Using Agile Concepts in Non-Agile Projects
155(1)
Agile, Pmp®, And Pmbok®
156(1)
Prior PMBOK® Versions
156(1)
What's Different about PMBOK® Version 7?
157(2)
The Difference Between Explicit and Tacit Knowledge
159(1)
Summary of Key Points
160(1)
Discussion Topics
161(1)
Notes
161(2)
9 Agile Communications and Tools
163(12)
Agile Communications Practices
163(1)
Information Radiators
163(2)
Face-to-Face Communications
165(1)
Daily Scrum Meetings
166(1)
Distributed Teams
166(1)
Agile Project Management Tools
167(1)
Benefits of Agile Project Management Tools
168(1)
Characteristics of Enterprise-Level Agile Project Management Tools
169(3)
Summary of Key Points
172(1)
Discussion Topics
173(1)
Notes
173(2)
10 Learning to See the Big Picture
175(10)
Systems Thinking
175(1)
What Is Systems Thinking?
175(1)
How Is Systems Thinking Used in Organizations?
176(1)
Complex Adaptive Systems
177(1)
What Are Complex Adaptive Systems?
177(2)
Characteristics of Complex Adaptive Systems
179(3)
Summary of Key Points
182(1)
Discussion Topics
183(1)
Notes
184(1)
11 The Roots of Agile
185(32)
Influence of Total Quality Management (TQM)
185(1)
Cease Dependence on Inspection
186(2)
Emphasis on the Human Aspect of Quality
188(1)
The Need for Cross-functional Collaboration and Transformation
189(1)
Importance of Leadership
190(1)
Ongoing Continuous Improvement
191(1)
Influence of Lean Manufacturing
192(3)
Customer Value
195(1)
Map the Value Stream
196(1)
Pull
196(4)
Flow
200(3)
Respect for People
203(1)
Perfection
204(1)
Principles of Product Development Flow
205(3)
1 Economics
205(1)
2 Queues: Actively Manage Queues
205(1)
3 Variability: Understand and Exploit Variability
206(1)
4 Batch Size: Reduce Batch Size
206(1)
5 WIP Constraints: Apply WIP Constraints
206(1)
6 Control Flow Under Uncertainty: Cadence and Synchronization
207(1)
7 Fast Feedback: Get Feedback as Fast as Possible
207(1)
8 Decentralize Control
207(1)
Summary of Key Points
208(1)
Discussion Topics
209(1)
Notes
210(7)
Part 3 Agile Project Management Planning and Management
12 Hybrid Agile Models
217(10)
Why Would You Use a Hybrid Agile Approach?
218(1)
Fit for Purpose
218(1)
As a Transition to a Full Agile Approach
218(1)
What Are the Benefits of a Hybrid Agile Approach?
219(1)
General Benefits of a Hybrid Agile Approach
219(1)
Other Benefits of a Hybrid Agile Approach
219(1)
What's Different About a Hybrid Agile Approach?
220(1)
Key Differences from a Plan-driven (Waterfall) Approach
221(1)
Key Differences from an Agile Approach
222(1)
Choosing the Right Approach
223(1)
Most Important Factors to Consider
223(1)
Other Factors to Consider
224(1)
Summary of Key Points
224(1)
Discussion Topics
225(1)
Notes
225(2)
13 Value-Driven Delivery
227(14)
Value-Driven Delivery Overview
227(1)
What's Different about Value-Driven Delivery?
228(1)
What Are the Advantages of Value-Driven Delivery?
229(1)
Principles of Value-Driven Delivery
230(1)
Focus on Customer Needs Rather Than Solutions
231(1)
The Pareto Rule
232(1)
Customer-Value Prioritization Overview
233(1)
Levels of Prioritization
233(1)
Factors to Consider in Prioritization
234(1)
MoSCoW Prioritization
234(1)
Value-Driven Delivery Tools
235(1)
Minimum Viable Product
235(1)
Minimum Marketable Feature
235(1)
Summary of Key Points
236(2)
Discussion Topics
238(1)
Notes
239(2)
14 Adaptive Planning
241(14)
Rolling-Wave Planning
242(1)
Overview of Rolling-Wave Planning
242(2)
Comparison of Planning Approaches
244(3)
Progressive Elaboration and Multilevel Planning
247(1)
Progressive Elaboration
247(1)
Multilevel Planning
248(3)
Summary of Key Points
251(2)
Discussion Topics
253(1)
Notes
253(2)
15 Agile Planning Practices and Tools
255(16)
Product/Project Vision
255(1)
What Is a Product/Project Vision?
255(1)
Product/Project Vision Examples
256(1)
Tips for Creating a Compelling Vision
257(1)
Product Road maps
258(1)
What Are the Benefits of a Product Roadmap?
258(1)
Tips for Creating a Product Roadmap
258(2)
Exploratory
260(1)
Assessment
260(1)
Agile Functional Decomposition
261(1)
Relationship of Functional Decomposition to Agile
261(1)
Functional Decomposition Examples
262(2)
Project Charter
264(1)
Summary of Key Points
265(3)
Discussion Topics
268(1)
Notes
269(2)
15 Agile Stakeholder Management and Agile Contracts
271(30)
What Is a Stakeholder?
272(1)
Internal Stakeholders
272(1)
External Stakeholders
272(1)
Why Is Stakeholder Management Important?
273(1)
Stakeholder Management Can Be Difficult
273(1)
What Can Go Wrong?
273(1)
Common Stakeholder Management Mistakes
274(1)
Stakeholder Management Process
275(1)
Identify and Analyze Stakeholders
275(1)
Prioritize Stakeholders
276(1)
What's Different About Agile Stakeholder Management?
277(1)
Advantages of an Agile Stakeholder Management Approach
277(1)
Agile Stakeholders Have Rights and Responsibilities
278(1)
Responsibility for Stakeholder Management in an Agile Environment
278(1)
Eight Tips for Agile Stakeholder Management
278(2)
Agile Contracts
280(1)
How Would an Agile Contract Work?
280(1)
Types of Agile Contracts
280(2)
An Agile Contracting Example
282(1)
Summary of Key Points
283(1)
Discussion Topics
284(1)
Notes
285(2)
Distributed Project Management in Agile
287(1)
What Is Distributed Project Management?
287(3)
Distributed Project Management Roles
290(1)
Developer Project Management Responsibilities
291(1)
Product Owner Project Management Responsibilities
292(3)
Scrum Master Project Management Responsibilities
295(1)
Summary of Key Points
295(2)
Discussion Topics
297(1)
Note
298(3)
Part 4 Making Agile Work for a Business
18 Scaling Agile to an Enterprise Level
301(24)
Enterprise-Level Agile Challenges
302(1)
Differences in Enterprise-Level Agile Practices
302(1)
Reinterpreting Agile Manifesto Values and Principles
303(4)
Enterprise-Level Obstacles to Overcome
307(1)
Collaborative and Cross-Functional Approach
307(1)
Organizational Commitment
308(1)
Risk and Regulatory Constraints
309(1)
Enterprise-Level Implementation Considerations
310(1)
Architectural Planning and Direction
310(1)
Enterprise-Level Requirements Definition and Management
311(2)
Development Team Integration
313(1)
Release to Production
314(1)
Enterprise-Level Management Practices
315(1)
Project/Program Management Approach
316(1)
The Role of a Project Management Office (PMO)
317(2)
Project/Product Portfolio Management
319(2)
Summary of Key Points
321(2)
Discussion Topics
323(1)
Notes
323(2)
19 Scaling Agile for Multiple-Team Projects
325(8)
Scrum-of-Scrums Approach
325(2)
Large-Scale Scrum (LeSS)
327(1)
Nexus
328(1)
Scrum at Scale
329(1)
Summary of Key Points
330(1)
Discussion Topics
331(1)
Notes
331(2)
20 Adapting an Agile Approach to Fit a Business
333(22)
The Impact of Different Business Environments on Agile
334(1)
Product-Oriented Companies
334(1)
Technology-Enabled Businesses
335(1)
Project-Oriented Businesses
336(1)
Hybrid Business Model
337(1)
Adapting an Agile Approach to a Business
337(1)
Typical Levels of Management
338(1)
Overall Business Management Level
338(4)
Enterprise Product/Project Portfolio Management Level
342(2)
Product Management Level
344(1)
Project Management Level
344(1)
Corporate Culture and Values
345(1)
The Importance of Corporate Culture and Values
345(2)
Value Disciplines
347(5)
Summary of Key Points
352(1)
Discussion Topics
353(1)
Notes
353(2)
21 Enterprise-Level Agile Transformations
355(18)
Planning an Agile Transformation
355(1)
Define the Goals You Want to Achieve
355(1)
Becoming Agile Is a Journey, Not a Destination
356(1)
Develop a Culture That Is Conducive to Agile
357(2)
Manage Change
359(2)
Don't Throw the Baby Out with the Bathwater
361(1)
Tools Can Be Very Important
362(2)
Adaptive Project Governance Model
364(1)
Executive Steering Group
365(1)
Project Governance Group
366(1)
Working Group Forums
366(1)
Project Teams
366(1)
Summary of Key Points
366(2)
Discussion Topics
368(1)
Notes
369(4)
Part 5 Enterprise-Level Agile Frameworks
22 Scaled Agile Framework®
373(12)
SAFe® Competency Areas
373(4)
SAFe® Core Values
377(1)
Lean Agile Mindset in SAFe®
378(1)
SAFe® Lean Agile Principles
379(1)
SAFe® Artifacts and Supporting Capabilities
380(1)
Summary of Key Points
380(2)
Discussion Topics
382(1)
Notes
383(2)
23 Disciplined Agile Delivery (DAD®)
385(12)
DA® Life Cycles
386(1)
Life Cycle Summary
387(1)
DA® Roles
387(1)
Primary DA® Roles
387(3)
Supporting DA® Roles
390(1)
DA® Mindset
391(1)
DA® Principles
391(1)
DA® Promises
392(1)
DA® Guidelines
392(1)
DA® Tool Kit
392(1)
Summary of Key Points
393(2)
Discussion Topics
395(1)
Notes
395(2)
24 Managed Agile Development Framework
397(26)
Managed Agile Development Overview
398(1)
The Macro-Level
399(1)
The Micro-Level
399(1)
Objectives of Managed Agile Development
399(1)
Plan-Driven Benefits
399(1)
Agile Benefits
400(1)
Key Differences from a Typical Waterfall Approach
400(3)
Framework Description
403(1)
Project Organization and Work Streams
403(1)
High-Level Process Overview
403(5)
Requirements Management Approach
408(3)
Project Scheduling Approach
411(1)
Project Management Approach
411(1)
Communications Approach
412(2)
Roles and Responsibilities
414(4)
Summary of Key Points
418(4)
Discussion Topics
422(1)
25 Summary of Enterprise-Level Frameworks
423(4)
High-Level Comparison
423(1)
How These Frameworks Have Evolved
424(1)
Discussion Topics
424(3)
Part 6 Case Studies
26 "Not-So-Successful" Case Studies
427(16)
Company A
428(1)
Background
428(1)
The Approach
428(1)
What Went Wrong
428(1)
Overall Conclusions
428(2)
Company B
430(1)
Background
430(1)
The Approach
431(1)
What Went Wrong
431(1)
Overall Conclusions
432(4)
Company C
436(1)
Background
436(1)
The Approach
436(1)
What Went Wrong
436(5)
Overall Conclusions
441(1)
Discussion Topics
441(1)
Notes
441(2)
27 Case Study: Valpak
443(26)
Background
443(1)
Valpak Stakeholders
443(1)
Valpak Franchisees
444(1)
Consumers
444(1)
Merchants
444(1)
Corporate
444(1)
The Role of Technology at Valpak
445(1)
Overview
445(1)
Scaled Agile Framework Implementation
445(6)
Project Management Approach
451(1)
Tools, Communication, and Reporting
452(1)
Challenges
453(1)
Cultural and Organizational Challenges
453(4)
Technical Challenges
457(2)
Other Challenges
459(2)
Overall Summary
461(1)
Key Success Factors
461(2)
Results and Conclusions
463(1)
More Strategic Management Focus
463(1)
Management of IT Resources
464(1)
Time-to-Market
464(1)
Alignment and Collaboration
465(1)
Employee Productivity and Morale
465(1)
Delivering More Frequent Value to Customers
465(1)
Openness and Transparency
465(1)
Responsiveness and Adaptivity
465(1)
Software Quality
465(1)
Lessons Learned
466(1)
Forming Projects Around Teams
466(1)
Planning Team Capacity and Developing a Sustainable Pace
466(1)
Using Sprint Reviews and "Science Fairs"
467(1)
Discussion Topics
467(1)
Notes
467(2)
28 Case Study: Harvard Pilgrim Health Care
469(30)
Background
469(1)
Overview
470(2)
Impact of Outsourcing and Vendor Partnering
472(1)
Role of the PMO
473(1)
Project Governance
474(2)
Role of Tools
476(1)
Project Methodology Mix
476(1)
Project Portfolio Management
477(1)
Project Management Approach
478(1)
Project Methodology
478(2)
Implementation Package Development
480(1)
Implementation Package Refinement
480(1)
Project Reporting
481(1)
Contractual Relationship with Dell Services
482(1)
Challenges
483(1)
Cultural and Organizational Challenges
483(3)
Contractual Challenges
486(3)
Technical Challenges
489(2)
Other Challenges
491(2)
Key Success Factors
493(1)
Conclusions
494(1)
Lessons Learned
494(3)
Discussion Topics
497(1)
Notes
497(2)
29 Case Study: General Dynamics, UK
499(14)
Background
499(1)
Overview
500(1)
Requirements Prioritization and Management Approach
500(1)
Contract Negotiation and Payment Terms
501(1)
Planning Approach
501(1)
Personnel Management
502(1)
Communication
502(1)
Management and Leadership Approach
503(1)
Project Management Approach
503(1)
DSDM Overview
504(1)
DSDM Principles
505(2)
Challenges
507(1)
Cultural and Organizational Challenges
507(1)
Contractual Challenges
507(1)
Technical Challenges
508(1)
Overall Summary
509(1)
Key Success Factors
509(1)
Conclusions
510(2)
Lessons Learned
512(1)
Tailor the Agile Delivery Technique as Part of Early Project Planning
512(1)
Agile Techniques Can Be Applied to New Project Environments
512(1)
Discussion Topics
512(1)
Notes
512(1)
30 Agile Hardware Development
513(12)
Agile Hardware Development Overview
514(1)
Hardware Development Challenges
514(1)
The Speed of Change Is What Is Important
515(1)
How to Put This Into Practice
516(2)
How It's Done at Tesla
518(1)
The Tesla Approach
519(3)
Overall Summary
522(1)
The Trade-Off Associated with Creativity and Innovation
522(1)
Does the Tesla Agile Hardware Development Model Work for All Companies?
522(1)
Discussion Topics
523(1)
Notes
523(2)
31 Non-Software Case Studies
525(10)
Agile Home Remodeling
525(1)
Background
525(1)
Why Was This Project So Difficult?
526(1)
Project Planning and Inception
526(1)
Project Scope
526(1)
Contractor Selection
527(2)
How Did the Project Work Out?
529(1)
What Were the Results?
529(1)
Overall Conclusions and Lessons Learned
529(1)
Agile Book Publishing
530(1)
How Was the Agile Approach Different?
530(1)
Lessons Learned
531(1)
Why Do People Have Trouble with This?
532(1)
Discussion Topics
533(2)
32 Overall Summary
535(10)
Evolution of the Project Management Profession
535(1)
The Future of Project Management
535(2)
What Does It Take to Become a Good Agile Project Manager in This New Environment?
537(1)
What to Do Differently
538(2)
General Recommendations
540(5)
Appendices
Appendix A Additional Reading and Resources
545(2)
Appendix B Glossary of Terms
547(10)
Appendix C Example Project / Program Charter Template
557(6)
Appendix D Suggested Course Outline
563(8)
Index 571
Charles G. Cobb (Fort Myers, FL) is the founder of the Agile Project Management Academy, a program that has taught over 200,000 students in 174 countries worldwide and his training is offered by three major training platforms. He has been a featured speaker at many PMI Chapter events, Agile groups, universities, and PMO workshops around the world. He previously was an Adjunct Professor of Agile Project Management at Boston University.