Hello ! WE ARE EDUHUBSPOT. One of the premier institutes for providing online and classroom PMP/CAPM training. Project Management Professional (PMP) is an internationally recognized professional designation offered by the Project Management Institute (PMI). The exam is based on the PMI Project Management Body of Knowledge (PMBOK), and requirements to sit for the exam include, a bachelor's degree, at least 4,500 hours of experience leading and directing projects, and 35 hours of formal project management education.
1000+ Practice Questions 75+ Videos 900+ Slides Subscribe to our simulator now
Thanks Varun for your amazing video. I don’t even atttend any mock exam. Watched this video and tried to understand the topics. My exam was on 26th August. It feels like I was watching this video during the exam. Thank you very much brother. I passed PMP exam on first attempt ❤
I am always confused on how to distinguish between weak matrix and functional organization when it comes to scenario based questions. Is there any key word or distinguishing favtor which can help me pick the right choice? Thanks
Thanks Gautham. Once again an excellent video. Q1 >> Scenario 1: Introvert -- As the trainer is getting irritated and not answering, not open, not mingling. Scenario 2: Extrovert -- As the trainer is answering, clarifying and not only one way, wants feedback so he knows the person has well understood. Q2 >> Scenario 1: Judging -- As the team member is making upfront plans and then follows the plan accordingly. Scenario 2: Perceiving -- As the team member is not making upfront plans, spontaneously picks up the task, but yet accomplished all the work for the day.
Thanks once again for an excellent explanation. Q1 - Scenario A - Theory X Manager - As the work is routine, Shivani follows the theory X manager method and rewards the team when they perform well to keep them motivated in their daily tasks. Q1 - Scenario B - Theory Y Manager - As the work is challenging and research, Vihaan follows the theory Y manager method and self-organises the team as they are already motivated for their work. Q2 - Esteem - As Santhi has an appraisal and expects a promotion and hike, she is giving her 100%.
1.S1-O4 , Two were working one is writing code and the other is reviewing 2.S2-01- The work is done but left some debts to do 3.S3-02 Left out works , Clean up Codes to promote Agility 4.S4-03 As they developed the test code first to implement the software code to make the test pass . 4.S4-
Hi Gautham, Excellent video. I really understood now with your explanation, though I felt I understood but as you mentioned I will never forget even when I am awaken form sleep and asked. Below is my answer. WPD >> (Collecting Planned and Actual progress / data) 1) # of defects found 2) Finish dates of activities 4) # of CR completed WPI >> (Comparing Planned and Actual progress / status) 3) Deliverable status 5) Implementation status of CR WPR >> (Electronic representation of progress / WPI) 6) Status Reports representation 7) Electronic dashboard
Hi Varun, I am an aspiring to undertake the PMP certification soon. Your video(s) are indeed very helpful. I have one query here, for Question # 136 (approximate Timestamp - 5:41:45), you have marked the option "D" as the correct solution, but while explaining the options, you say option "B" as the correct option. Do you mind clarifying, please?
Very valuable video with great choice. But, only one confusion related to Q10 where Root-cause analysis in retrospective was selected as a choice. Whereas, in other EduHubSpot Q/A video, it stated by Varun that Root-Cause Analysis is not part of Retrospective. Request your kind clarification pls..
Usually you would say to document before you act but this is the first video where you say that you would act first. What governs the difference? I’m referencing question 5.
Hi Varun, Thanks for the QA, its very handy for the exam mindset, one clarification i need is about change request you have mentioned in Agile, as far as I know change request and CCB never comes in picture in Agile but only in predictive, would you please clarify this point, thank you.
Beautifully explained each and every question. This video has provided with a yardstick on how to think and answer PMP questions. Yet to take the exam and will give a shout out to you soon , Varun
Thank you for most Valuable video on Most Valuable Concept Scenario1 : The Answer is Dormancy, because the risk has been realized, In order to identify the impact of the risk, we need 3 more days, i.e., the period of time that may elapse after risk has occurred before its impact is discovered Scenario2 : The Answer is Connectivity, because team member has identified technical risk which is connected to lot other modules, i.e., one risk connected to other individual project risk Scenario3: The Answer is Proximity because the technical risk will start impacting the project within 30 days. i.e., the time within which a risk can make an impact on project objectives Scenario4: The Answer is Urgency because the risk response plan has to be completed within 20 days. i.e., time within which a risk response plan for a risk should get implemented.
Thank you so much for finding an easy path for your students as well as all those who want to clear PMP, After six months of study I found 6 ways to select the answer correctly in practice questions and through these videos, I understood that it should be our mindset
Gautham, you won’t believe it! Before my exam today, I watched this video, and the similar question came up! Thank you so much, Gautham and EduHubSpot, for the amazing content!
Hi Gautham - Excellent way of making things clear, as always. Post going through your videos, concepts remains permanently in mind. Below are the response: Scenario-1 is Pair Programming. Reason: Functionality development is together (in pair). Scenario-2 is Technical debt. Reason: For developed software code, variables not named properly and duplicate code is created, for quicker delivery. Scenario-3 is Refactoring - Reason: Code cleaning. Scenario-4 is TDD. Reason: Writing the test cases first and then testing and implementing the code accordingly, to be passed.
Scenario 1 - Mary is working with another person for the same feature, one person is the driver and Andrew is the navigator - hence pair programming Scenario2 - Mary is creating technical debt Scenario 3 - Cleaning up the debt created, hence refactoring Scenario 4 - Writing test cases first, hence TDD Thank you Gautham.
4 for 1 scenerio mary snd andrew pairing 1 for 2 scenerio Mary not given proper names its debt 2 for 3 scenerio Regactoring 3 for 4 scenerio test driven as the they wrote first test cases for each and started the implementation Thanks a Mr Gautam
Fantastic explanation with examples Gautham... its just stuck in mind. Thanks! Here is my response:👍 Scenario:01 - 04 : PAIR PROGRAMMING - Mary and Andrew are together developing the Functionality. Scenario:02 - 01: TECHNICAL DEBT - Mary has developed a software code for quicker delivery where she has created duplicate code and also not named variables properly. Scenario:03 - 02: REFACTORING - Mary's team scheduled some slack to clean the code. Scenario:04 - 03 TEST-DRIVEN DEVELOPMENT - Mary's team has written the test cases first and then they test and then implement the code pass the test.
Thank you Gautham 4. Pair Programming - Mary is Coding, Andrew is Reviewing (Scenario1) 1. Technical Debt - As there are no Proper Names and Lot of Duplicate Code (Scenario 2) 2. Refactoring - Fixing the code (KW promote Agility i.e enhancing agility) (Scenario 3) 3. TDD - Writing TCs n clean up code that fits n Retesting until satisfied. (Scenario 4)
1. Technical Debt - Scenario 02: Reason: Technical debt refers to the consequences of poor design choices made for the sake of speed, which can lead to issues in the long term, such as the creation of duplicate code and poor naming conventions. 2. Refactoring - Scenario 03 Reason: Refactoring is the process of restructuring existing computer code without changing its external behavior to improve nonfunctional attributes like readability, maintainability, and performance. 3. Test-Driven Development - Scenario 04 Reason: Test-Driven Development (TDD) is a software development process in which test cases are developed to specify and validate what the code will do. 4. Pair Programming - Scenario 01 Reason: Pair programming is an Agile software development technique in which two programmers work together at one workstation. One writes the code while the other reviews it in real-time.
