🔥 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?
that was great comment, it's best that the team works to agree what they believe is fair. the reason is that if you want your pay check to turn up on a day you agree, you want to make sure the company doesn't say "you should have agreed the requirement we pay you"
Hate such situations when clients or even internal stakeholders for internal project are asking: "So, this will be done?" and you can not answer, because your IT team is not giving you proper estimates. Used to work with both approaches - strong estimation of each task and gutfeeling of dev's team like "yeah, we will be able to do it in next month". Funny or not, but both actually worked. When you have strong process of estimation, involving whole team looking at proper requirements - great. It takes a lot of time, but gives you better understanding. However, if the team is experienced enough, even quick chat about some feature idea can give you rough estimation, which you just multiply by (put here figure from you experience with current team) , then add 10% more as buffer and then give some promises. Thanks for the content, Dmitro!
Thanks for sharing your insights. Totally agree. Different teams and situations call for different approaches. So, this one is default for me. And the idea is that at some point the team can follow the process themselves.
I would ask David: how can I help you with these current estimations? What info do you need from my side in order for you to proceed? And then going further into details...but to some point of course. This is how I do it with my co-workers on the projects, although I'm working in Automatics Industry.
"How can I help you?" is a powerful question. And in this case, David said he needs design from the UI team. But we can't wait for those designs. We need an approach to convince David that it's safe to provide preliminary estimates. But overall, you approach is sound as well. Thanks for participation!
I would ask why after what I have promised to the developer he don't want to give estimate. In case this kind of tasks he has never done in his life, I would ask some dev to help who has similar experience to estimate. Or maybe the reason is that they're some additional clarifications I could provide quickly enough that would help to dev give an estimate. Also would look in history of projects in the company and see if same tasks were previously done and how much did they take.
I'll try to ask the developer to give me a preliminary estimate which I will cautiously explain to the client mentioning that nothing out of this is final, I guess that should work! Or if not, then I'll watch the rest of the video to find it out.
I don't recommend doing that. You need to control expectations right from the start. Stakeholders will remember the first thing you say. After that, it's hard to change their perception...
@@ITProjectManagers Sure Dmytro, then do you rather I get on a call with the senior tech people to discuss the timelines and estimates more prominently?
@@itsmechicpalak Well, in my world, I would give the requirements to business analyst first or discuss it with the team. This way we can uncover all the requirements. Then, I would assign the estimation to the corresponding team lead.
🔥 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?
that was great comment, it's best that the team works to agree what they believe is fair. the reason is that if you want your pay check to turn up on a day you agree, you want to make sure the company doesn't say "you should have agreed the requirement we pay you"
Yes, it's always best to empower the team to provide the estimates. Then, they'll have a buy-in in all project decisions.
Hate such situations when clients or even internal stakeholders for internal project are asking: "So, this will be done?" and you can not answer, because your IT team is not giving you proper estimates. Used to work with both approaches - strong estimation of each task and gutfeeling of dev's team like "yeah, we will be able to do it in next month". Funny or not, but both actually worked.
When you have strong process of estimation, involving whole team looking at proper requirements - great. It takes a lot of time, but gives you better understanding. However, if the team is experienced enough, even quick chat about some feature idea can give you rough estimation, which you just multiply by (put here figure from you experience with current team) , then add 10% more as buffer and then give some promises.
Thanks for the content, Dmitro!
Thanks for sharing your insights. Totally agree.
Different teams and situations call for different approaches.
So, this one is default for me.
And the idea is that at some point the team can follow the process themselves.
I would ask David: how can I help you with these current estimations? What info do you need from my side in order for you to proceed?
And then going further into details...but to some point of course.
This is how I do it with my co-workers on the projects, although I'm working in Automatics Industry.
"How can I help you?" is a powerful question.
And in this case, David said he needs design from the UI team. But we can't wait for those designs.
We need an approach to convince David that it's safe to provide preliminary estimates.
But overall, you approach is sound as well.
Thanks for participation!
I would ask why after what I have promised to the developer he don't want to give estimate. In case this kind of tasks he has never done in his life, I would ask some dev to help who has similar experience to estimate. Or maybe the reason is that they're some additional clarifications I could provide quickly enough that would help to dev give an estimate. Also would look in history of projects in the company and see if same tasks were previously done and how much did they take.
Thanks for participation, Anna. You questions are spot on. Great mindset and approach.
It's a very common issue. thanks for covering👍
Thanks for watching, Kasmine! Glad it was helpful.
I'll try to ask the developer to give me a preliminary estimate which I will cautiously explain to the client mentioning that nothing out of this is final, I guess that should work! Or if not, then I'll watch the rest of the video to find it out.
I don't recommend doing that. You need to control expectations right from the start.
Stakeholders will remember the first thing you say. After that, it's hard to change their perception...
@@ITProjectManagers Sure Dmytro, then do you rather I get on a call with the senior tech people to discuss the timelines and estimates more prominently?
@@itsmechicpalak Well, in my world, I would give the requirements to business analyst first or discuss it with the team. This way we can uncover all the requirements.
Then, I would assign the estimation to the corresponding team lead.
That's a great video!
Glad you enjoyed it, Alex!
Nice job!!!
Thanks! Glad you found it useful.