🔥 There’s one skill that separates great IT Project Managers from everyone else-project tailoring. Most project managers get stuck trying to learn every new tool and process out there. They dive deep into theories but still struggle to deliver projects on time and within budget. It’s frustrating. The truth is, great project managers don’t try to do it all-they focus on tailoring simple processes and tools that work best for their team and projects. That’s what creates transparency, predictability, and results. But here’s the thing-tailoring isn’t just guessing what might work. It’s about knowing three critical components: 1) Understanding project management on a deeper level. 2) Knowing exactly what to tailor. 3) Applying it effectively in real companies with real people. That’s why I created the Professional Development Plan for IT Project Managers-to help you master project tailoring and finally become the project manager who delivers every time, no matter the challenge. ✅ Click the link below to get your development plan now and take the next step toward mastering project management. itpmschool.com/get-plan?
@deepakkumarbasnet28535 ай бұрын
Wonderful presentation and in very simple way it has been explained. Thank you...
@ITProjectManagers5 ай бұрын
You're most welcome
@AmirNassiraei5 ай бұрын
Where can I find the article you mentioned at 2:36 in the video?
@ITProjectManagers5 ай бұрын
Here you go: itpmschool.com/risk-response-strategy/
@petrucervac87674 жыл бұрын
Thanks for the tips. Your video is the first place I heard about the term "Risk Register"!
@ITProjectManagers4 жыл бұрын
You're welcome! Just curious, are you a Project Manager?
@myt6132 жыл бұрын
Very useful and informative. I just want to mention that at the time of writing the risk it's important to use metalanguage. i.e Case , Risk, Effect Like you shoed in your templates a separate column for effect. This will also help us create precise and effective risk responses to the Risk Not for the Cause, Not for the Effect.
@ITProjectManagers2 жыл бұрын
Great tip! Thanks. I would extend it even further. With the top 10-20 risks you should use descriptive language as much as possible (not the grades, categories, or percents). High-severity risks require involvement of stakeholders, they usually don’t know team’s jargon.
@hcoviedo Жыл бұрын
@6:06 did you mean Quantitative for "Monetary Risk in Dollars" ? Where as Qualitative is the scoring of low, medium, high.
@ITProjectManagers Жыл бұрын
Yes, quantitative. Mispronounced the term.
@saj15074 жыл бұрын
simply superb amazing and perfect presentation . concise and to the point .
@ITProjectManagers4 жыл бұрын
Thank you for your kind feedback. I’m glad it was helpful.
@MuslimRujhan3 жыл бұрын
Dmitriy Sir, You are outstanding, and a precious personality and mentor. each video is unique and described so well. I learned so much from each of your videos. I am really thankful to you as even you have responded to one of my email questions regarding risk management. I truly love you and love your personality dear, Sir. My sincere wishes and respect to you.
@ITProjectManagers3 жыл бұрын
So nice of you. Thank you so much for these warm feedback!
@devonnickeo87924 жыл бұрын
Getting ready to take PM test. Great info. Thanks!
@ITProjectManagers4 жыл бұрын
Good luck with the exam!
@Skylightatdusk4 жыл бұрын
Fantastic information. Well presented.
@ITProjectManagers4 жыл бұрын
Glad it was helpful!
@olenafedosieieva61914 жыл бұрын
Thanks for real life examples!
@ITProjectManagers4 жыл бұрын
You are welcome! Glad it helps.
@hcoviedo Жыл бұрын
Great video BTW, took lots of notes!
@ITProjectManagers Жыл бұрын
Glad it was helpful!
@Priya.Nish803 жыл бұрын
Your videos are amazing! Thank you so much 😊
@ITProjectManagers3 жыл бұрын
Glad you like them! Thanks for your feedback.
@arunmane76572 жыл бұрын
Your videos are more valuable. Thanks for your guidance. Request to share please a video on risk at process or production of Manufacturing company..
@ITProjectManagers Жыл бұрын
Sorry, I missed your comment. If it's still actual, please write a new one. Note: leaving this comment to keep track of open questions.
@devonnickeo87924 жыл бұрын
I love this guy
@ITProjectManagers4 жыл бұрын
Thanks:)
@devonnickeo87924 жыл бұрын
I could have saved money by simply listening to this guy
@ITProjectManagers4 жыл бұрын
Glad it’s helpful.
@ashleymatthews31343 жыл бұрын
So 3x7 = 27, got it, cheers
@ITProjectManagers3 жыл бұрын
LOL:) Nice catch. I buffered it a bit;)
@Truth972 Жыл бұрын
What about the Risk identification table that covers risk,effects and causes?
@ITProjectManagers11 ай бұрын
Please check this article: itpmschool.com/project-risk-management-plan/ It will provide you with some insights.
@محمديحيمحمد-ذ5ص10 ай бұрын
Thanks so much
@ITProjectManagers10 ай бұрын
You're welcome!
@Skylightatdusk4 жыл бұрын
Please clarify re the statuses of the risk and why they are important or can be used. The following are my suppositions. . New. A mew type of risk, named 'new' because its details are still being learned. . Planned. Applies to a positive risk or one for which you are raising or lowing the barriers to the risk. For instance, if you ask your men to work through a rain storm (perhaps because of fast approaching deadlines) even though doing so goes against what you had previously decided. . Upcoming. In Novembe, you know that Christmas in December increases the risk of electrical fires. . In progress. as per the video. The risk is happening right now. . Done. The stated response has already been applied and therefore mitigated or avoided. Consequently, the probability is lower than otherwise and the risk can be treated with much less priority. I imagine the status is useful for prioritizing the focus on a given day. Thanks
@ITProjectManagers4 жыл бұрын
Great question! I would use the following statuses: New - a risk is logged in the Risk Register but you didn’t analyze it. Planned - a risk that you analyzed and selected a response plan for it. Even if you decide to passively accept it - it’s a plan. In Progress - for risk that we work on right now or we actively monitor. Done - Risk Response was implemented. The impact is absent or you have taken it into account as Change Request or new risks. Upcoming doesn’t look as a valuable status for me. Only if you can set it automatically based on the due date.
@CVicki3 жыл бұрын
Cool video, cool presentation of materials. I wish I had such 10 years ago or so :) Great job! And thank you for educating current and future Project Managers!
@ITProjectManagers3 жыл бұрын
Glad you enjoyed it, Vika! That’s the exact approach I take when I plan a video - I wish someone explained it to me at the start of my PM career.