Hi everyone! I passed my PMP Exam!

This is my second PMP course. The first one I did with a company called BrainSensei and their practice tests covered materials that were not in the course. Needless to say, I wasn't happy. I'm hoping this will get me over the hump when I take my exam in January. At least I have a good understanding of most concepts heading into this training. Very much looking forward to getting over this hurdle! Dan

It's probably because I spaced out a bit while Andrew was explaining, but I would have mixed this up in a job interview or on the job 😵. The explanation is from Gemini: Agile is an overarching philosophy, while Scrum and Kanban are specific frameworks used to put that philosophy into practice. It is a very common misconception to equate Scrum with Agile, or to view Kanban as just a visual board. In reality, Kanban is a complete, standalone project management system with its own strict rules and principles. Understanding the Hierarchy To clear up the confusion, think of the relationship like this: - Agile is the mindset. It is a set of values and principles defined in the Agile Manifesto (like prioritizing individuals over processes and responding to change over following a plan). You cannot "do" Agile; you can only be Agile. - Scrum and Kanban are the tools. They are concrete frameworks that give teams specific processes, roles, and rules to actually implement that Agile mindset. Why Kanban is More Than an "Information Radiator" An information radiator is simply any visual tool—like a chart on a wall—that displays project data. While Kanban uses a visual board (which acts as an information radiator), Kanban itself is a comprehensive management system governed by specific mechanics: - WIP Limits (Work-In-Progress): This is the core engine of Kanban. The system strictly limits how many tasks can be in a specific column (e.g., "In Progress") at one time. If the limit is 3, you cannot start a 4th task until one is moved to "Done." This forces teams to fix bottlenecks rather than just starting new work. - Pull System: Work is never "pushed" onto team members by a manager. Instead, team members "pull" the next highest-priority task into their workflow only when they have the capacity under the WIP limit. - Explicit Process Policies: Kanban requires the team to explicitly define rules for how work moves from stage to stage (e.g., a strict definition of what "Ready for QA" means), ensuring systemic consistency.

The newest YouTube video created by Andrew Ramdayal, with a special emphasis on Case Study questions: https://youtu.be/Bu_gSFuB1Ck?si=8bS2GhpadE408NA0

Alright guys, tomorrow is my exam date. I am very nervous