Acknowledgments |
|
xv | |
Introduction |
|
xvii | |
|
Chapter 1 Agile Principles and the PMI-ACP Mindset |
|
|
1 | (46) |
|
Introducing the Agile Principles and Mindset Tasks |
|
|
2 | (2) |
|
Reviewing the Nine Tasks for Exam Domain I |
|
|
2 | (1) |
|
Applying the Nine Agile Principles |
|
|
3 | (1) |
|
Defining Agile Values for Projects |
|
|
4 | (2) |
|
Managing Knowledge-Work Projects |
|
|
4 | (1) |
|
Comparing Empirical Processes and Defined Processes |
|
|
5 | (1) |
|
Embracing the Agile Mindset |
|
|
6 | (3) |
|
Reviewing the Declaration of Interdependence |
|
|
6 | (1) |
|
Being Agile and Doing Agile |
|
|
7 | (1) |
|
Inverting the Triple Constraints |
|
|
7 | (1) |
|
Leading Organization Agility |
|
|
8 | (1) |
|
|
8 | (1) |
|
Reviewing the Agile Manifesto |
|
|
9 | (4) |
|
Valuing Individuals and Interactions over Processes and Tools |
|
|
10 | (1) |
|
Valuing Working Software over Comprehensive Documentation |
|
|
10 | (1) |
|
Valuing Customer Collaboration over Contract Negotiation |
|
|
11 | (1) |
|
Responding to Change over Following a Plan |
|
|
11 | (1) |
|
Embracing the 12 Principles of Agile |
|
|
12 | (1) |
|
Comparing Agile Project Approaches |
|
|
13 | (12) |
|
Reviewing the Basics of Scrum |
|
|
14 | (2) |
|
Reviewing the Scrum Ceremonies |
|
|
16 | (1) |
|
|
17 | (2) |
|
|
19 | (2) |
|
Introducing Lean Product Development |
|
|
21 | (1) |
|
|
22 | (1) |
|
Utilizing Feature-Driven Development |
|
|
23 | (1) |
|
|
24 | (1) |
|
|
25 | (3) |
|
Comparing Management and Leadership in Agile Projects |
|
|
25 | (1) |
|
|
26 | (1) |
|
|
27 | (1) |
|
Creating a Safe and Trustful Environment |
|
|
27 | (1) |
|
Encourage Emergent Leadership |
|
|
28 | (1) |
|
|
28 | (19) |
|
|
29 | (4) |
|
|
33 | (4) |
|
|
37 | (10) |
|
Chapter 2 Value-Driven Delivery in Agile Projects |
|
|
47 | (50) |
|
Introducing the Agile Principles of Value Delivery |
|
|
48 | (2) |
|
Reviewing the 14 Tasks for Exam Domain II |
|
|
48 | (2) |
|
Applying the Four Value-Driven Delivery Principles |
|
|
50 | (1) |
|
Delivering Value in Agile Projects |
|
|
50 | (2) |
|
|
51 | (1) |
|
Combating Waste in Agile Projects |
|
|
51 | (1) |
|
Defining Value in Organizations |
|
|
52 | (11) |
|
Exploring the Time Value of Money |
|
|
53 | (2) |
|
Tracking Performance with Earned Value Management |
|
|
55 | (5) |
|
|
60 | (1) |
|
Creating Key Performance Indicators |
|
|
61 | (1) |
|
Managing Risk in Agile Projects |
|
|
62 | (1) |
|
Considering Regulations as Requirements |
|
|
62 | (1) |
|
Prioritizing Requirements |
|
|
63 | (3) |
|
Using the MoSCoW Approach |
|
|
63 | (1) |
|
Prioritizing with Kano Analysis |
|
|
64 | (1) |
|
|
65 | (1) |
|
|
65 | (1) |
|
|
66 | (1) |
|
Prioritizing with a Requirements Prioritization Model |
|
|
66 | (1) |
|
Delivering Value Incrementally |
|
|
66 | (3) |
|
Considering the Cost of Change |
|
|
67 | (1) |
|
Creating the Minimal Viable Product |
|
|
68 | (1) |
|
Embracing Low-Tech/High-Touch Tools |
|
|
68 | (1) |
|
Introducing the Theory of Constraints |
|
|
69 | (3) |
|
|
70 | (1) |
|
Creating a Cumulative Flow Diagram |
|
|
70 | (1) |
|
|
71 | (1) |
|
Working with Vendors in Agile Projects |
|
|
72 | (2) |
|
Working with DSDM Contracting |
|
|
73 | (1) |
|
Using a Graduated Fixed-Price Contract |
|
|
73 | (1) |
|
Creating a Fixed-Price Work Package |
|
|
74 | (1) |
|
Validating Value in Agile Projects |
|
|
74 | (4) |
|
Implementing Continuous Integration |
|
|
75 | (1) |
|
Working with Test-Driven Development |
|
|
76 | (1) |
|
Confirming Value with Exploratory Testing |
|
|
76 | (1) |
|
Completing Usability Testing |
|
|
77 | (1) |
|
|
78 | (19) |
|
|
79 | (4) |
|
|
83 | (4) |
|
|
87 | (10) |
|
Chapter 3 Managing Stakeholder Engagement |
|
|
97 | (48) |
|
Introducing the Stakeholder Engagement Principles |
|
|
98 | (2) |
|
Reviewing the Nine Tasks for Exam Domain III |
|
|
99 | (1) |
|
Identifying and Engaging Project Stakeholders |
|
|
100 | (3) |
|
Starting at the Beginning |
|
|
101 | (1) |
|
Building Stakeholder Synergy |
|
|
101 | (1) |
|
Keeping Stakeholders Involved |
|
|
102 | (1) |
|
Leading Stakeholder Conversations |
|
|
102 | (1) |
|
Sharing the Project Vision |
|
|
103 | (2) |
|
Creating the Project Charter |
|
|
103 | (1) |
|
Defining Done in Agile Projects |
|
|
104 | (1) |
|
Modeling in Agile Projects |
|
|
105 | (5) |
|
Creating Personas for Modeling |
|
|
105 | (1) |
|
Utilizing Screen Designs and Wireframes |
|
|
106 | (2) |
|
|
108 | (1) |
|
Exploring a Use Case Diagram |
|
|
108 | (2) |
|
Managing Stakeholder Communication and Engagement |
|
|
110 | (5) |
|
Planning Project Communications |
|
|
111 | (1) |
|
Leading Face-to-Face Communications |
|
|
112 | (1) |
|
Sharing Project Knowledge |
|
|
113 | (1) |
|
Building an Information Radiator |
|
|
114 | (1) |
|
Utilizing Social Media for Agile Projects |
|
|
114 | (1) |
|
Collaborating with Stakeholders |
|
|
115 | (4) |
|
Creating Red and Green Zones |
|
|
115 | (1) |
|
Hosting a Project Workshop |
|
|
116 | (1) |
|
|
117 | (1) |
|
Playing Collaboration Games |
|
|
118 | (1) |
|
Applying Soft Skills for Agile Projects |
|
|
119 | (4) |
|
Exploring Emotional Intelligence Foundations |
|
|
120 | (1) |
|
|
121 | (1) |
|
Negotiating with Project Stakeholders |
|
|
121 | (1) |
|
|
122 | (1) |
|
Facilitating Project Meetings |
|
|
123 | (1) |
|
Making Effective Decisions |
|
|
123 | (2) |
|
Empowering the Project Team |
|
|
124 | (1) |
|
Leading Participatory Decision-Making |
|
|
125 | (1) |
|
|
125 | (20) |
|
|
126 | (6) |
|
|
132 | (4) |
|
|
136 | (9) |
|
Chapter 4 Leading Team Performance |
|
|
145 | (40) |
|
Introducing the Team Performance Exam Domain |
|
|
146 | (2) |
|
Reviewing the Nine Tasks for Exam Domain IV |
|
|
146 | (2) |
|
Valuing People over Processes |
|
|
148 | (4) |
|
Defining the Delivery Team |
|
|
149 | (1) |
|
Identifying the Role and Responsibilities of the Product Owner |
|
|
149 | (1) |
|
Defining the Team Leader Responsibilities |
|
|
150 | (1) |
|
Recognizing the Project Sponsor |
|
|
151 | (1) |
|
Forming the Agile Project Team |
|
|
152 | (4) |
|
Working with Generalizing Specialists |
|
|
153 | (1) |
|
Developing the Project Team |
|
|
153 | (1) |
|
Building a High-Performing Team |
|
|
154 | (2) |
|
Leading the Agile Project Team |
|
|
156 | (6) |
|
Motivating the Project Team |
|
|
158 | (1) |
|
Training the Project Team |
|
|
159 | (1) |
|
Coaching Project Team Members |
|
|
160 | (2) |
|
|
162 | (2) |
|
Working with Different Agile Team Locales |
|
|
162 | (1) |
|
Identifying Osmotic Communications |
|
|
163 | (1) |
|
Defining the Project Team Space |
|
|
163 | (1) |
|
|
164 | (1) |
|
Monitoring Agile Team Performance |
|
|
164 | (4) |
|
|
165 | (2) |
|
Calculating Project Team Velocity |
|
|
167 | (1) |
|
|
168 | (17) |
|
|
169 | (3) |
|
|
172 | (4) |
|
|
176 | (9) |
|
Chapter 5 Planning for Agile Projects |
|
|
185 | (44) |
|
Introducing the Adaptive Planning Domain |
|
|
186 | (2) |
|
Reviewing the Ten Tasks for Exam Domain V |
|
|
187 | (1) |
|
Building a Strong Adaptive Planning Foundation |
|
|
188 | (9) |
|
Reviewing the Key Tasks of Adaptive Planning |
|
|
189 | (1) |
|
Defining Agile and Non-Agile Planning Activities |
|
|
190 | (1) |
|
Defining the Principles of Agile Planning |
|
|
191 | (2) |
|
Working with Emergent Plans |
|
|
193 | (1) |
|
Leading Progressive Elaboration |
|
|
194 | (1) |
|
Performing Value-Based Analysis |
|
|
194 | (2) |
|
|
196 | (1) |
|
Timeboxing Meetings and Events |
|
|
197 | (2) |
|
|
198 | (1) |
|
Managing Time Constraints |
|
|
198 | (1) |
|
Working with User Stories |
|
|
199 | (4) |
|
|
200 | (1) |
|
Creating the User Story Backlog |
|
|
201 | (1) |
|
Sizing and Estimating User Stories |
|
|
201 | (2) |
|
Breaking Down the Project for Releases |
|
|
203 | (4) |
|
|
204 | (1) |
|
Using Affinity Estimating |
|
|
205 | (1) |
|
Sizing T-Shirts for User Stories |
|
|
205 | (1) |
|
Sizing Stories with the Wideband Delphi Technique |
|
|
206 | (1) |
|
Sizing with Planning Poker |
|
|
206 | (1) |
|
Creating Release and Iteration Plans |
|
|
207 | (4) |
|
|
208 | (1) |
|
Visioning Project Releases |
|
|
208 | (1) |
|
|
209 | (1) |
|
Performing Iteration Planning |
|
|
210 | (1) |
|
Hosting Daily Standup Meetings |
|
|
211 | (1) |
|
|
211 | (18) |
|
|
212 | (4) |
|
|
216 | (4) |
|
|
220 | (9) |
|
Chapter 6 Detecting and Resolving Problems |
|
|
229 | (34) |
|
Introducing the Problem Detection and Resolution Domain |
|
|
230 | (1) |
|
Reviewing the Five Tasks for Exam Domain VI |
|
|
230 | (1) |
|
Controlling Project Problems |
|
|
231 | (3) |
|
Considering the Cost of Change |
|
|
233 | (1) |
|
|
234 | (1) |
|
Creating a Safe and Open Environment |
|
|
234 | (3) |
|
Identifying Failure and Success Modes |
|
|
235 | (1) |
|
Exploring Success Strategies |
|
|
236 | (1) |
|
Detecting Problems and Defects |
|
|
237 | (5) |
|
Identifying Lead Time and Cycle Time |
|
|
238 | (2) |
|
Completing Variance Analysis |
|
|
240 | (1) |
|
Identifying Project Trends |
|
|
240 | (1) |
|
|
241 | (1) |
|
Creating a Risk-Adjusted Backlog |
|
|
242 | (4) |
|
Determining Risk Severity |
|
|
243 | (1) |
|
Creating a Risk Burndown Chart |
|
|
244 | (1) |
|
Solving Problems in Agile Projects |
|
|
245 | (1) |
|
|
246 | (17) |
|
|
247 | (3) |
|
|
250 | (4) |
|
|
254 | (9) |
|
Chapter 7 Leading Continuous Improvement |
|
|
263 | (32) |
|
Introducing the Continuous Improvement Exam Domain |
|
|
264 | (1) |
|
Reviewing the Six Tasks for Exam Domain VII |
|
|
265 | (1) |
|
Leading Continuous Improvement as a Process |
|
|
265 | (3) |
|
|
267 | (1) |
|
Completing Systems Thinking |
|
|
267 | (1) |
|
Participating in Process Analysis |
|
|
268 | (3) |
|
Techniques for Process Analysis |
|
|
269 | (1) |
|
Creating Value Stream Maps |
|
|
269 | (2) |
|
Facilitating Project Meetings |
|
|
271 | (3) |
|
Hosting a Project Pre-Mortem |
|
|
272 | (1) |
|
Leading Product Review Sessions |
|
|
273 | (1) |
|
Reviewing the Feedback Methods |
|
|
274 | (3) |
|
Examining a Product Feedback Loop |
|
|
274 | (1) |
|
Considering Reviews and Retrospectives |
|
|
275 | (1) |
|
|
275 | (1) |
|
Understanding Approved Iterations |
|
|
276 | (1) |
|
Completing Team Assessments |
|
|
277 | (2) |
|
Improving Team Performance |
|
|
277 | (2) |
|
Sharing Knowledge Among the Project Team |
|
|
279 | (1) |
|
|
279 | (16) |
|
|
280 | (2) |
|
|
282 | (4) |
|
|
286 | (9) |
|
Appendix A Critical Exam Information |
|
|
295 | (14) |
|
|
295 | (2) |
|
|
295 | (1) |
|
Practice the Testing Process |
|
|
295 | (1) |
|
|
296 | (1) |
|
Answer Every Question---Once |
|
|
296 | (1) |
|
Use the Process of Elimination |
|
|
296 | (1) |
|
|
297 | (12) |
|
Embracing the Agile Principles and Mindset |
|
|
298 | (1) |
|
Recognizing the Different Agile Flavors |
|
|
299 | (2) |
|
|
301 | (1) |
|
Measuring Project Performance |
|
|
301 | (1) |
|
Filtering Project Requirements |
|
|
301 | (2) |
|
Identifying Project Stakeholder Engagement |
|
|
303 | (1) |
|
Creating a Project Charter |
|
|
303 | (1) |
|
Communicating with Stakeholders |
|
|
303 | (1) |
|
Recognizing Self-Directed Teams |
|
|
304 | (1) |
|
Investing in User Stories |
|
|
304 | (1) |
|
|
305 | (1) |
|
Managing Problems and Defects |
|
|
305 | (1) |
|
|
305 | (1) |
|
Completing Systems Thinking |
|
|
306 | (1) |
|
|
307 | (2) |
|
Appendix B About the Digital Content |
|
|
309 | (4) |
|
|
309 | (1) |
|
Total Tester Premium Practice Exam Software |
|
|
309 | (1) |
|
Installing and Running Total Tester Premium Practice Exam Software |
|
|
310 | (1) |
|
Video Training from the Author |
|
|
310 | (1) |
|
Secure PDF Copy of the Book |
|
|
310 | (1) |
|
|
311 | (2) |
|
Total Seminars Technical Support |
|
|
311 | (1) |
|
McGraw-Hill Education Content Support |
|
|
311 | (2) |
Glossary |
|
313 | (22) |
Index |
|
335 | |