Agile PMP and Agile Certified Practitioner Exam Preparation

Introduction

• Series of Agile PMP questions/Agile Certified Practitioner questions.
• Ideal for exam preparation or team knowledge checks.
• Focus on the whole team approach in Agile.

Whole Team Approach

• Key Concepts:
  • Involves everyone with necessary skills and knowledge in the team.
  • Avoids reliance on external teams for faster responses.
  • Teams should be small (3-9 people) but not limited to that size.
  • Members are often dedicated 100% to avoid productivity loss due to multitasking.
  • Members should be multi-skilled with one deep specialty (T-shaped people).
• Incorrect Statement for Whole Team Approach:
  • Teams should not be multi-skilled.

Cross-functional Teams

• Characteristics:
  • Include all necessary skills for product delivery.
  • Visual management (e.g., Kanban, burndown charts) is essential regardless of team proficiency.
  • Typically include roles such as designers, developers, testers, etc.
  • Deliver work quickly and with high quality, without external dependencies.
• Incorrect Statement:
  • Teams do not need visual management.

Agile Roles

• Main Roles in Agile Teams:
  • Product Owner
  • Cross-functional Team Members
  • Team Facilitator (e.g., Scrum Master, Team Coach)
• Facilitator Roles:
  • Remove blockers and ensure work flow.
  • Facilitate problem solving and discussion.

Problem Solving in Agile

• Scenario Handling:
  • Raise blockers during stand-ups for team to resolve.
  • Avoid removing features unless absolutely necessary.
  • Agile allows swarming to solve problems collectively.

Servant Leadership

• Importance in Agile:
  • Encourages a safe and open environment.
  • Promotes transparency and admitting mistakes.
• Incorrect Statements:
  • Knowing who to blame.
  • Counting defects accurately.

Feedback Mechanisms

• Agile Feedback Methods:
  • Sprint reviews and demos with stakeholders.
  • Regular retrospectives to reflect and improve.
• Incorrect Methods:
  • Weekly meetings.
  • Feedback only during blocks.

Agile Team Velocity

• Handling Feature Requests:
  • Show team velocity and backlog points to prioritize with stakeholders.
  • Do not add more members or alter features without proper process.

Agile Tools in Waterfall Projects

• Introduction to Agile Tools:
  • Utilize visual management tools (Kanban boards, velocity charts).
  • Integrate Agile tools in traditional projects for problem detection.

Agile Manifesto and Principles

• 12 Clarifying Principles:
  • Deliver working software frequently.
  • Business and developers must collaborate daily.
• Incorrect Principles:
  • Complete autonomy for developers.
  • Dictation from business people.

Conclusion

• Practice Agile questions to prepare for exams.
• Dedication and practice are keys to passing the exam.