Mindset for the PMP Exam

Introduction

Assumption: All information needed to answer questions is provided.
Prioritization: Choose the best answer from seemingly correct options.
Avoid Extremes: Avoid extreme actions like project closure or escalation.
Collaboration: Aim for inclusive, collaborative solutions.
Directness: Address issues directly and find root causes.
Consultation: Engage team members for expert judgment.
Customer Role: Ensure deliverables meet customer's expectations.
Conflict Resolution: Favor project benefits over individual gains.
Estimating Techniques:
- Bottom-Up: Detailed and accurate, but time-consuming.
- Top-Down: Quick and less accurate.
Framework Identification: Recognize keywords for agile or predictive approaches.

Planning: Create and adhere to a plan; use change requests if needed.
Change Process:
- Stakeholders can raise changes.
- Document in change log.
- Assess impacts.
- Present to change control board.
- Communicate outcomes and update logs.
Risk vs. Issue:
- Risk: Future events (positive or negative).
- Issue: Events that have occurred.
Consultation: Regularly seek expert judgment from team members.
Closing Process:
- Confirm product acceptance.
- Finalize claims.
- Transition to operations.
- Measure benefits.
- Release resources.
- Final report and archiving.
Lessons Learned: Update throughout the project.
Stakeholder Communication: Understand and cater to preferences.

Servant Leadership:
- Remove blockers for the team.
- Shield from distractions.
- Promote growth and motivation.
Product Owner Coaching: Help prioritize backlog if necessary.
Vision Communication: Utilize a project charter.
Co-location: Encourage face-to-face interaction for effective communication.
Information Radiators: Use visual management tools like Kanban boards.
Psychological Safety: Promote a safe space for disagreements.
Continuous Improvement:
- Use retrospectives for reflection.
- Demonstrate completed items in sprint reviews.