First, thank you for posting such videos. Q3- 17:45 Doesn't the first meeting right after project is approved called kick-off meeting - the one we use to prepare charter, and to set vision and objectives of the project? Please help.
Hi Nischal, kickoff meeting is subjective. Some call the meeting immediately after initiation as kick off, and some call it the meeting where execution is kicked off . But it is not used to prepare the charter. Kick off will happen afterwards.
Hi, on a general level, project manager is supposed to be aware of everything that happens and ultimately accountable for project success... But at the task level the accountability will be delegated and it will vary.
Thanks for these wonderful explanation, and it would add more value where at the end of each task you discuss the methods, modules and artifacts related to it.
Thanks Qudratullah .. nice suggestion.. We have covered those in our video on process, people, and business domain, where we explain all the 35 tasks... Having said that, will try to add a quick review of the topics... Esp for process domain tasks...
Thank you, I have viewed those videos and they are so informative, just suggested that I would be good to have some of the explanation here as well. Much appreciated
A project manager is assigned to a new operations support project and during the knowledge transfer has noticed that the customer is using expired software for a few applications. The expired software is no longer being supported from its vendor and hence potential security issues may arise. How can these issues be addressed without impacting the transition? A)Plan for migrating the applications from legacy to new software in a rip and replace mode. B )Used the vendor knowledge database and invest in supporting and fixing all security issues that may arise as several team members hold a PhD in security. C) Inform the customer that your team will not support the applications on expired software and request the customer to migrate them to new version and hand it over after that. D ) Call for a Steering Committee meeting with respective stakeholders and take the risk acceptance sign off from them and proceed with the transition.
Hi, the question is a bit too technical for PMP... However, not considering the technical aspects... Option B is where you are involving people in finding out the solution hence appears the best. A talks about very specific actions/solution, which we don't know whether it will work or not. C and D appear not a good choice. It's not a part of project manager's mindset to say "we won't work untill ... " or work just with a document sign off despite knowing the risk.
@@edzest Hi my choice was also B . This question is from pmi study hall question of the day . The answer they gave was D . So I put here as I did not understand why D
@@edzest Solution: D. Call for a Steering Committee meeting with respective stakeholders and take the risk acceptance sign off from them and proceed with the transition. Calling for the Steering Committee meeting to take the risk acceptance sign off is the correct option to avoid any impact to the transition. Plan for migration the application from legacy to new software is incorrect as it will impact the transition of the current project. Invest in supporting and fixing all security issues is also incorrect as it will impact the transition timeline. Informing the customer that no support will be done on the expired software and getting them to migrate to new version is also incorrect as that doesn't help in transitioning the project. This question and rationale were developed in reference to: Project Governance: The Essentials (2011) Rod Beecham/IT Governance Publishing/CHAPTER 2: A PROJECT PRIMER/ [Item The Steering Committee The Project Manager drafts the project specification. It will be a large document and will take time to prepare. When the Project Manager is satisfied that the specification is complete, it should be examined by your organization’s Internal Auditor or Risk Manager, who will determine whether the costings, schedule and risk assessment are sufficiently robust. If they are, the project specification will then be presented to the Project Steering Committee for approval.]"
@@1786argha you are right, the explanation is not. Because by taking a sign-off, project managers ensure that no one blames them (saving my back, mentality) , but how do they resolve the issue? A problem doesn't go away by signing a document. 😊
@@edzest if pmi is looking for saving my back answers . No doubt I didn’t clear in my first attempt. Next attempt on 8th June… I am terrified 🤯 watching your videos and subscribed to pmi study hall
First, thank you for posting such videos.
Q3- 17:45
Doesn't the first meeting right after project is approved called kick-off meeting - the one we use to prepare charter, and to set vision and objectives of the project?
Please help.
Hi Nischal, kickoff meeting is subjective.
Some call the meeting immediately after initiation as kick off, and some call it the meeting where execution is kicked off .
But it is not used to prepare the charter. Kick off will happen afterwards.
Thank you so much Amit for uploading these informative videos. I passed my PMP exam and your UA-cam channel helped me a lot 🙏🙏
That is so good to know. Congratulations! 🎉🎉🎉
Isn’t project manager accountable for all tasks in a project in reference to example you gave on RACI chart
Hi, on a general level, project manager is supposed to be aware of everything that happens and ultimately accountable for project success... But at the task level the accountability will be delegated and it will vary.
@@edzest ok , got it so no need to mention individually in RACI . It’s more of understood
@@1786argha it's more like general accountability for the overall project level... While RACI is at individual task level
Thanks for these wonderful explanation, and it would add more value where at the end of each task you discuss the methods, modules and artifacts related to it.
Thanks Qudratullah .. nice suggestion..
We have covered those in our video on process, people, and business domain, where we explain all the 35 tasks...
Having said that, will try to add a quick review of the topics... Esp for process domain tasks...
Thank you, I have viewed those videos and they are so informative, just suggested that I would be good to have some of the explanation here as well.
Much appreciated
@@qudratullahqudrat1456 I understand your point, will do that. Thank you.😊
A project manager is assigned to a new operations support project and during the knowledge transfer has noticed that the customer is using expired software for a few applications. The expired software is no longer being supported from its vendor and hence potential security issues may arise.
How can these issues be addressed without impacting the transition?
A)Plan for migrating the applications from legacy to new software in a rip and replace mode.
B )Used the vendor knowledge database and invest in supporting and fixing all security issues that may arise as several team members hold a PhD in security.
C) Inform the customer that your team will not support the applications on expired software and request the customer to migrate them to new version and hand it over after that.
D ) Call for a Steering Committee meeting with respective stakeholders and take the risk acceptance sign off from them and proceed with the transition.
Hi, the question is a bit too technical for PMP...
However, not considering the technical aspects... Option B is where you are involving people in finding out the solution hence appears the best.
A talks about very specific actions/solution, which we don't know whether it will work or not.
C and D appear not a good choice. It's not a part of project manager's mindset to say "we won't work untill ... " or work just with a document sign off despite knowing the risk.
@@edzest Hi my choice was also B . This question is from pmi study hall question of the day . The answer they gave was D . So I put here as I did not understand why D
@@edzest Solution: D. Call for a Steering Committee meeting with respective stakeholders and take the risk acceptance sign off from them and proceed with the transition.
Calling for the Steering Committee meeting to take the risk acceptance sign off is the correct option to avoid any impact to the transition.
Plan for migration the application from legacy to new software is incorrect as it will impact the transition of the current project. Invest in supporting and fixing all security issues is also incorrect as it will impact the transition timeline. Informing the customer that no support will be done on the expired software and getting them to migrate to new version is also incorrect as that doesn't help in transitioning the project.
This question and rationale were developed in reference to:
Project Governance: The Essentials (2011) Rod Beecham/IT Governance Publishing/CHAPTER 2: A PROJECT PRIMER/ [Item The Steering Committee The Project Manager drafts the project specification. It will be a large document and will take time to prepare. When the Project Manager is satisfied that the specification is complete, it should be examined by your organization’s Internal Auditor or Risk Manager, who will determine whether the costings, schedule and risk assessment are sufficiently robust. If they are, the project specification will then be presented to the Project Steering Committee for approval.]"
@@1786argha you are right, the explanation is not.
Because by taking a sign-off, project managers ensure that no one blames them (saving my back, mentality) , but how do they resolve the issue? A problem doesn't go away by signing a document. 😊
@@edzest if pmi is looking for saving my back answers . No doubt I didn’t clear in my first attempt. Next attempt on 8th June… I am terrified 🤯 watching your videos and subscribed to pmi study hall
Thanks a lot Amit for your detailed explanation...!
You're welcome Bhushan. 🤗
Do let us know your feedback, if you'd want us to add anything that could make the video explanation better...