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) |
|
|
7 | (1) |
|
|
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) |
|
|
19 | (1) |
|
|
20 | (1) |
|
|
21 | (4) |
|
Part 1 Fundamentals of Agile |
|
|
|
2 Agile History and the Agile Manifesto |
|
|
25 | (18) |
|
|
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) |
|
|
30 | (1) |
|
|
30 | (3) |
|
Agile Manifesto Principles |
|
|
33 | (6) |
|
|
39 | (1) |
|
|
40 | (1) |
|
|
41 | (2) |
|
|
43 | (26) |
|
|
44 | (1) |
|
|
45 | (1) |
|
|
45 | (2) |
|
|
47 | (3) |
|
|
50 | (1) |
|
|
50 | (1) |
|
|
51 | (2) |
|
|
53 | (1) |
|
|
54 | (1) |
|
|
55 | (1) |
|
|
56 | (1) |
|
|
57 | (1) |
|
|
58 | (1) |
|
General Scrum/Agile Principles |
|
|
58 | (1) |
|
Variability and Uncertainty |
|
|
59 | (1) |
|
Prediction and Adaptation |
|
|
60 | (1) |
|
|
61 | (1) |
|
|
62 | (1) |
|
|
63 | (1) |
|
|
64 | (2) |
|
|
66 | (1) |
|
|
66 | (1) |
|
|
67 | (2) |
|
4 Agile Planning, Requirements, and Product Backlog |
|
|
69 | (26) |
|
|
69 | (1) |
|
|
70 | (2) |
|
|
72 | (1) |
|
|
73 | (1) |
|
|
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) |
|
|
78 | (1) |
|
User Personas and User Stories |
|
|
79 | (1) |
|
|
79 | (1) |
|
|
80 | (2) |
|
|
82 | (1) |
|
|
83 | (1) |
|
What Is a Product Backlog? |
|
|
83 | (1) |
|
Product Backlog Grooming (Refinement) |
|
|
84 | (2) |
|
|
86 | (2) |
|
|
88 | (1) |
|
|
89 | (6) |
|
Part 2 Agile Project Management Overview |
|
|
|
5 Agile Development, Quality, and Testing Practices |
|
|
95 | (14) |
|
Agile Software Development Practices |
|
|
96 | (1) |
|
|
96 | (1) |
|
|
97 | (1) |
|
|
98 | (1) |
|
|
99 | (1) |
|
|
100 | (1) |
|
Agile Quality Management Practices |
|
|
100 | (1) |
|
Key Differences in Agile Quality Management Practices |
|
|
100 | (1) |
|
|
101 | (1) |
|
The Role of Quality Assurance (QA) Testing in an Agile Project |
|
|
102 | (1) |
|
|
103 | (1) |
|
|
103 | (1) |
|
Acceptance Test-Driven Development |
|
|
103 | (1) |
|
Repeatable Tests and Automated Regression Testing |
|
|
104 | (1) |
|
Value-Driven and Risk-Based Testing |
|
|
104 | (1) |
|
|
104 | (3) |
|
|
107 | (2) |
|
6 Time-Boxing, Kanban, and Theory of Constraints |
|
|
109 | (16) |
|
|
111 | (1) |
|
|
111 | (1) |
|
|
111 | (1) |
|
|
111 | (1) |
|
|
112 | (1) |
|
|
112 | (1) |
|
Additional Time-Boxing Productivity Advantages |
|
|
113 | (1) |
|
|
113 | (1) |
|
|
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) |
|
|
118 | (1) |
|
|
119 | (3) |
|
|
122 | (1) |
|
|
123 | (1) |
|
|
123 | (2) |
|
|
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) |
|
|
129 | (1) |
|
|
130 | (3) |
|
Other Relative Sizing Techniques |
|
|
133 | (1) |
|
|
134 | (1) |
|
More Sophisticated Agile Estimation Techniques |
|
|
134 | (1) |
|
Velocity and Burn-Down/Burn-Up Charts |
|
|
135 | (1) |
|
|
135 | (1) |
|
|
135 | (2) |
|
|
137 | (1) |
|
|
138 | (1) |
|
|
139 | (2) |
|
|
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) |
|
|
156 | (1) |
|
|
156 | (1) |
|
What's Different about PMBOK® Version 7? |
|
|
157 | (2) |
|
The Difference Between Explicit and Tacit Knowledge |
|
|
159 | (1) |
|
|
160 | (1) |
|
|
161 | (1) |
|
|
161 | (2) |
|
9 Agile Communications and Tools |
|
|
163 | (12) |
|
Agile Communications Practices |
|
|
163 | (1) |
|
|
163 | (2) |
|
Face-to-Face Communications |
|
|
165 | (1) |
|
|
166 | (1) |
|
|
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) |
|
|
172 | (1) |
|
|
173 | (1) |
|
|
173 | (2) |
|
10 Learning to See the Big Picture |
|
|
175 | (10) |
|
|
175 | (1) |
|
What Is Systems Thinking? |
|
|
175 | (1) |
|
How Is Systems Thinking Used in Organizations? |
|
|
176 | (1) |
|
|
177 | (1) |
|
What Are Complex Adaptive Systems? |
|
|
177 | (2) |
|
Characteristics of Complex Adaptive Systems |
|
|
179 | (3) |
|
|
182 | (1) |
|
|
183 | (1) |
|
|
184 | (1) |
|
|
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) |
|
|
190 | (1) |
|
Ongoing Continuous Improvement |
|
|
191 | (1) |
|
Influence of Lean Manufacturing |
|
|
192 | (3) |
|
|
195 | (1) |
|
|
196 | (1) |
|
|
196 | (4) |
|
|
200 | (3) |
|
|
203 | (1) |
|
|
204 | (1) |
|
Principles of Product Development Flow |
|
|
205 | (3) |
|
|
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) |
|
|
207 | (1) |
|
|
208 | (1) |
|
|
209 | (1) |
|
|
210 | (7) |
|
Part 3 Agile Project Management Planning and Management |
|
|
|
|
217 | (10) |
|
Why Would You Use a Hybrid Agile Approach? |
|
|
218 | (1) |
|
|
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) |
|
|
224 | (1) |
|
|
225 | (1) |
|
|
225 | (2) |
|
|
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) |
|
|
232 | (1) |
|
Customer-Value Prioritization Overview |
|
|
233 | (1) |
|
|
233 | (1) |
|
Factors to Consider in Prioritization |
|
|
234 | (1) |
|
|
234 | (1) |
|
Value-Driven Delivery Tools |
|
|
235 | (1) |
|
|
235 | (1) |
|
Minimum Marketable Feature |
|
|
235 | (1) |
|
|
236 | (2) |
|
|
238 | (1) |
|
|
239 | (2) |
|
|
241 | (14) |
|
|
242 | (1) |
|
Overview of Rolling-Wave Planning |
|
|
242 | (2) |
|
Comparison of Planning Approaches |
|
|
244 | (3) |
|
Progressive Elaboration and Multilevel Planning |
|
|
247 | (1) |
|
|
247 | (1) |
|
|
248 | (3) |
|
|
251 | (2) |
|
|
253 | (1) |
|
|
253 | (2) |
|
15 Agile Planning Practices and Tools |
|
|
255 | (16) |
|
|
255 | (1) |
|
What Is a Product/Project Vision? |
|
|
255 | (1) |
|
Product/Project Vision Examples |
|
|
256 | (1) |
|
Tips for Creating a Compelling Vision |
|
|
257 | (1) |
|
|
258 | (1) |
|
What Are the Benefits of a Product Roadmap? |
|
|
258 | (1) |
|
Tips for Creating a Product Roadmap |
|
|
258 | (2) |
|
|
260 | (1) |
|
|
260 | (1) |
|
Agile Functional Decomposition |
|
|
261 | (1) |
|
Relationship of Functional Decomposition to Agile |
|
|
261 | (1) |
|
Functional Decomposition Examples |
|
|
262 | (2) |
|
|
264 | (1) |
|
|
265 | (3) |
|
|
268 | (1) |
|
|
269 | (2) |
|
15 Agile Stakeholder Management and Agile Contracts |
|
|
271 | (30) |
|
|
272 | (1) |
|
|
272 | (1) |
|
|
272 | (1) |
|
Why Is Stakeholder Management Important? |
|
|
273 | (1) |
|
Stakeholder Management Can Be Difficult |
|
|
273 | (1) |
|
|
273 | (1) |
|
Common Stakeholder Management Mistakes |
|
|
274 | (1) |
|
Stakeholder Management Process |
|
|
275 | (1) |
|
Identify and Analyze Stakeholders |
|
|
275 | (1) |
|
|
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) |
|
|
280 | (1) |
|
How Would an Agile Contract Work? |
|
|
280 | (1) |
|
|
280 | (2) |
|
An Agile Contracting Example |
|
|
282 | (1) |
|
|
283 | (1) |
|
|
284 | (1) |
|
|
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) |
|
|
295 | (2) |
|
|
297 | (1) |
|
|
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) |
|
|
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) |
|
|
321 | (2) |
|
|
323 | (1) |
|
|
323 | (2) |
|
19 Scaling Agile for Multiple-Team Projects |
|
|
325 | (8) |
|
|
325 | (2) |
|
|
327 | (1) |
|
|
328 | (1) |
|
|
329 | (1) |
|
|
330 | (1) |
|
|
331 | (1) |
|
|
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) |
|
|
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) |
|
|
344 | (1) |
|
|
344 | (1) |
|
Corporate Culture and Values |
|
|
345 | (1) |
|
The Importance of Corporate Culture and Values |
|
|
345 | (2) |
|
|
347 | (5) |
|
|
352 | (1) |
|
|
353 | (1) |
|
|
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) |
|
|
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) |
|
|
365 | (1) |
|
|
366 | (1) |
|
|
366 | (1) |
|
|
366 | (1) |
|
|
366 | (2) |
|
|
368 | (1) |
|
|
369 | (4) |
|
Part 5 Enterprise-Level Agile Frameworks |
|
|
|
22 Scaled Agile Framework® |
|
|
373 | (12) |
|
|
373 | (4) |
|
|
377 | (1) |
|
Lean Agile Mindset in SAFe® |
|
|
378 | (1) |
|
SAFe® Lean Agile Principles |
|
|
379 | (1) |
|
SAFe® Artifacts and Supporting Capabilities |
|
|
380 | (1) |
|
|
380 | (2) |
|
|
382 | (1) |
|
|
383 | (2) |
|
23 Disciplined Agile Delivery (DAD®) |
|
|
385 | (12) |
|
|
386 | (1) |
|
|
387 | (1) |
|
|
387 | (1) |
|
|
387 | (3) |
|
|
390 | (1) |
|
|
391 | (1) |
|
|
391 | (1) |
|
|
392 | (1) |
|
|
392 | (1) |
|
|
392 | (1) |
|
|
393 | (2) |
|
|
395 | (1) |
|
|
395 | (2) |
|
24 Managed Agile Development Framework |
|
|
397 | (26) |
|
Managed Agile Development Overview |
|
|
398 | (1) |
|
|
399 | (1) |
|
|
399 | (1) |
|
Objectives of Managed Agile Development |
|
|
399 | (1) |
|
|
399 | (1) |
|
|
400 | (1) |
|
Key Differences from a Typical Waterfall Approach |
|
|
400 | (3) |
|
|
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) |
|
|
412 | (2) |
|
Roles and Responsibilities |
|
|
414 | (4) |
|
|
418 | (4) |
|
|
422 | (1) |
|
25 Summary of Enterprise-Level Frameworks |
|
|
423 | (4) |
|
|
423 | (1) |
|
How These Frameworks Have Evolved |
|
|
424 | (1) |
|
|
424 | (3) |
|
|
|
26 "Not-So-Successful" Case Studies |
|
|
427 | (16) |
|
|
428 | (1) |
|
|
428 | (1) |
|
|
428 | (1) |
|
|
428 | (1) |
|
|
428 | (2) |
|
|
430 | (1) |
|
|
430 | (1) |
|
|
431 | (1) |
|
|
431 | (1) |
|
|
432 | (4) |
|
|
436 | (1) |
|
|
436 | (1) |
|
|
436 | (1) |
|
|
436 | (5) |
|
|
441 | (1) |
|
|
441 | (1) |
|
|
441 | (2) |
|
|
443 | (26) |
|
|
443 | (1) |
|
|
443 | (1) |
|
|
444 | (1) |
|
|
444 | (1) |
|
|
444 | (1) |
|
|
444 | (1) |
|
The Role of Technology at Valpak |
|
|
445 | (1) |
|
|
445 | (1) |
|
Scaled Agile Framework Implementation |
|
|
445 | (6) |
|
Project Management Approach |
|
|
451 | (1) |
|
Tools, Communication, and Reporting |
|
|
452 | (1) |
|
|
453 | (1) |
|
Cultural and Organizational Challenges |
|
|
453 | (4) |
|
|
457 | (2) |
|
|
459 | (2) |
|
|
461 | (1) |
|
|
461 | (2) |
|
|
463 | (1) |
|
More Strategic Management Focus |
|
|
463 | (1) |
|
Management of IT Resources |
|
|
464 | (1) |
|
|
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) |
|
|
465 | (1) |
|
|
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) |
|
|
467 | (1) |
|
|
467 | (2) |
|
28 Case Study: Harvard Pilgrim Health Care |
|
|
469 | (30) |
|
|
469 | (1) |
|
|
470 | (2) |
|
Impact of Outsourcing and Vendor Partnering |
|
|
472 | (1) |
|
|
473 | (1) |
|
|
474 | (2) |
|
|
476 | (1) |
|
|
476 | (1) |
|
Project Portfolio Management |
|
|
477 | (1) |
|
Project Management Approach |
|
|
478 | (1) |
|
|
478 | (2) |
|
Implementation Package Development |
|
|
480 | (1) |
|
Implementation Package Refinement |
|
|
480 | (1) |
|
|
481 | (1) |
|
Contractual Relationship with Dell Services |
|
|
482 | (1) |
|
|
483 | (1) |
|
Cultural and Organizational Challenges |
|
|
483 | (3) |
|
|
486 | (3) |
|
|
489 | (2) |
|
|
491 | (2) |
|
|
493 | (1) |
|
|
494 | (1) |
|
|
494 | (3) |
|
|
497 | (1) |
|
|
497 | (2) |
|
29 Case Study: General Dynamics, UK |
|
|
499 | (14) |
|
|
499 | (1) |
|
|
500 | (1) |
|
Requirements Prioritization and Management Approach |
|
|
500 | (1) |
|
Contract Negotiation and Payment Terms |
|
|
501 | (1) |
|
|
501 | (1) |
|
|
502 | (1) |
|
|
502 | (1) |
|
Management and Leadership Approach |
|
|
503 | (1) |
|
Project Management Approach |
|
|
503 | (1) |
|
|
504 | (1) |
|
|
505 | (2) |
|
|
507 | (1) |
|
Cultural and Organizational Challenges |
|
|
507 | (1) |
|
|
507 | (1) |
|
|
508 | (1) |
|
|
509 | (1) |
|
|
509 | (1) |
|
|
510 | (2) |
|
|
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) |
|
|
512 | (1) |
|
|
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) |
|
|
518 | (1) |
|
|
519 | (3) |
|
|
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) |
|
|
523 | (1) |
|
|
523 | (2) |
|
31 Non-Software Case Studies |
|
|
525 | (10) |
|
|
525 | (1) |
|
|
525 | (1) |
|
Why Was This Project So Difficult? |
|
|
526 | (1) |
|
Project Planning and Inception |
|
|
526 | (1) |
|
|
526 | (1) |
|
|
527 | (2) |
|
How Did the Project Work Out? |
|
|
529 | (1) |
|
|
529 | (1) |
|
Overall Conclusions and Lessons Learned |
|
|
529 | (1) |
|
|
530 | (1) |
|
How Was the Agile Approach Different? |
|
|
530 | (1) |
|
|
531 | (1) |
|
Why Do People Have Trouble with This? |
|
|
532 | (1) |
|
|
533 | (2) |
|
|
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) |
|
|
538 | (2) |
|
|
540 | (5) |
|
|
|
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 | |