• Recognizing key Agile developments and definitions
• Applying the values and principles of the Agile Manifesto
• Mapping tools, techniques, knowledge, and skills to PMI’s six domains of Agile development

Focusing on business value

• Defining and prioritizing features in terms of user and stakeholder value
• Leveraging rapid feedback cycles

Ensuring progressive elaboration of requirements

• Identifying Minimally Marketable Features for release planning
• Sharpening the requirements definition by agreeing on the Definition of Done

Engaging empowered business stakeholders

• Identifying stakeholders and their concerns
• Promoting effective collaboration and participation

Communicating progress to help the organization make informed decisions

• Enabling knowledge sharing
• Building trust and managing expectations through shared success criteria

Forming cross-functional teams

• Establishing collaborative behaviors through group decision-making
• Influencing teams to design their internal work processes

Empowering teams to self-organize

• Encouraging teams to estimate and track project progress
• Creating safe environments for experimentation

Developing high-performance teams

• Raising productivity by eliminating waste
• Coaching styles that foster skill enhancement

Planning at multiple levels

• Applying rolling wave planning
• Leveraging progressive elaboration

Employing empirical planning

• Balancing priorities and team capabilities
• Coaching the team to adjust cadences based on situational awareness

Applying Agile Earned Value Measurement (EVM)

• Refining estimate ranges to reflect uncertainty
• Capturing measures of accepted work delivered in a specified time frame
• Controlling costs through quantitative measures

Recognizing and mitigating risks

• Time Boxing to focus on immediate issues
• Engaging the team proactively to identify risks and create mitigation strategies
• Ensuring impediments are resolved and stakeholder expectations are adjusted

Communicating risks and impediments

• Maintaining visibility with burndown charts, value stream mapping, and Kanban boards
• Managing features and technical issues with Backlog

Tailoring the process

• Conducting retrospectives to improve the team’s behavior
• Experimenting with new techniques and process ideas

Evaluating work efficiency

• Removing nonvalue-adding processes
• Reducing Work In Progress (WIP)

• Defining your exam preparation strategy
• Gaining insight into the exam format and process
• Applying proven tips for exam success
• Optimizing your study time and focus