Brilliant bit of explanation Dmitriy , it really sets up the exact conversation skills required to deal the external stakeholders initially. Please do keep posting such kinda scenario..it really helps onboarding PMs to reach a comfortable stage...
Thanks so much, Dmytro, you are great - so pragmatic and clear - and the llama lady was a really refreshing element :) we are more than happy to see and learn more from you :)
00:03 As a project manager, setting boundaries and goals at the start is crucial. 01:14 Asking critical questions for project charter 02:16 Understanding the context and purpose of the project 03:19 Discussing project scope and initial plans 04:21 Key questions to uncover project constraints 05:25 Always ask about constraints and dependencies 06:37 Clarifying detailed project requirements is essential 07:44 Smooth transition from meeting to project setup
Also how to deal with clients who order something innovative which requires Research and development, and both of the sides don't know what the result be, but the client still pays despite of the result. Something that technically might be not feasible. But still worth researching, which requires developer's time. Thank you in advance!
In this case, you need two things. One a times and materials contract, to ensure that the client pays for the efforts people put into the research no matter what the outcome is. Second, a well written project charter that clearly explains the boundaries of the project and main approaches you plan to take for the R&D. The idea is to give some control over the process to the clients and make them responsible to decide whether they want to burn more money based on current results.
Hi Dmitriy, thank you for the videos. Do you have a video for composing detailed technical specification document ( if it's called like that, in russian I meant Техническое задание). Thank you in advance!
Hello, No, I don't have a video specifically on that topic. And the reason is that it's not a PM's job to do that. It's something a business analyst does. On the other hand, in most cases, we try to keep to User Stories and try to empower the team to develop a technical solution. At most, you can create a high-level architecture document.
@@ITProjectManagers Thank you for the reply. Then how we worked in our IT company was wrong )) Today, at last I got your book. Hope it will boost my knowledge in PM.
👉Discover How to Land a Senior IT Project Manager Job…
…so You Can Finally Get the Fulfillment and Recognition You Deserve
itpmschool.com/workshop/
Brilliant bit of explanation Dmitriy , it really sets up the exact conversation skills required to deal the external stakeholders initially. Please do keep posting such kinda scenario..it really helps onboarding PMs to reach a comfortable stage...
Thanks for your feedback!
Thanks a lot for wonderful mock session Dmitriy !! Your videos are very motivating for aspiring project managers !! Please keep doing more of them
Thank you, I will. And thanks for feedback. It means a lot to me.
Thanks so much, Dmytro, you are great - so pragmatic and clear - and the llama lady was a really refreshing element :) we are more than happy to see and learn more from you :)
Wonderful! More videos to come in 2024:)
Thank you, Dmitry, @IT Project Managers, I need to relisten again. Super helpful.
Glad it was helpful, Rita! Next video is on Tuesday. So, stay tuned.
00:03 As a project manager, setting boundaries and goals at the start is crucial.
01:14 Asking critical questions for project charter
02:16 Understanding the context and purpose of the project
03:19 Discussing project scope and initial plans
04:21 Key questions to uncover project constraints
05:25 Always ask about constraints and dependencies
06:37 Clarifying detailed project requirements is essential
07:44 Smooth transition from meeting to project setup
Great notes. Thanks:)
😂😂 Had me laughing so hard I needed to rewind a few times. Nice job
Glad you enjoyed it.:)
Also how to deal with clients who order something innovative which requires Research and development, and both of the sides don't know what the result be, but the client still pays despite of the result. Something that technically might be not feasible. But still worth researching, which requires developer's time. Thank you in advance!
In this case, you need two things. One a times and materials contract, to ensure that the client pays for the efforts people put into the research no matter what the outcome is. Second, a well written project charter that clearly explains the boundaries of the project and main approaches you plan to take for the R&D. The idea is to give some control over the process to the clients and make them responsible to decide whether they want to burn more money based on current results.
@@ITProjectManagers Thanks!
First question should be to understand the detailed requirements from the client.
No, not at this stage. They probably don't have all the answers yet.
I recommend that you watch the video on project charter.
Hi Dmitriy, thank you for the videos. Do you have a video for composing detailed technical specification document ( if it's called like that, in russian I meant Техническое задание). Thank you in advance!
Hello,
No, I don't have a video specifically on that topic. And the reason is that it's not a PM's job to do that. It's something a business analyst does. On the other hand, in most cases, we try to keep to User Stories and try to empower the team to develop a technical solution. At most, you can create a high-level architecture document.
@@ITProjectManagers Thank you for the reply. Then how we worked in our IT company was wrong )) Today, at last I got your book. Hope it will boost my knowledge in PM.
To client: can you please provide us the brief about the project and how this product benefited to your company
Nice. Thanks for participating!
No risk, only opportunities 🤣
Hey, how did you find this video?:) It's not yet published.
I've sent a wrong link! This is a third video, and the second is here: ruclips.net/video/mvc8c4HXWrU/видео.html