🔥 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?
Thank you for the 101 Kanban knowledge 1. What if QA fail, do we ask developer to fix until it is ready to deploy? But how will you prioritize the ongoing task and Fail QA task on Kanban. 2. Interested in CI/CD 🙏
You are welcome. Good questions. 1. If QA fails while a task is still on the board, then you need to make developers fix all critical defects. Again, it's a matter of DoD to specify what defects are acceptable. If you find a defect in production later, create a new ticket and prioritise it accordingly. 2. Treat defect and tasks equally. Then, priorities them as you see fit. In some cases, you can override all current work and expedite one ticket. For example if it's a super critical defect on prod.
I have a video on Jira. But it’s a bit advanced version: Is Jira Ready for IT Projects in 2023? | How to Use Jira ruclips.net/video/KjUAVFrqOVs/видео.html But i plan to create a beginner’s guide somewhere soon.
Hello Dmytro, thanks for the cristal clear explanation about Kanban. I would be interested in CI/CD videos. And of course, more Jira related topics. It would be great to have a full playlist. E.g.: going from beginers to advanced.
Hey there Dmytro, I'm a bit late to seeing this video, but as a Junior Dev being pushed into his first PM role, this video is very helpful. My only real question is how do you make all tasks "Approximately the same size"? If I have a big feature like, a analytics dashboard, how can I make tasks the same size? I could break that big feature up into UI task, database connection tasks, etc. But in a small company I wouldn't want multiple developers working on smaller parts of the same feature, I think that brings in too much confusion and requires way too much coordination. I would've just assumed that you assign that one ticket either yourself as the PM OR through triaging with your dev team. Sorry if that question is a big abstract, but I don't really understand how you can truly break somethings up, yet keep them roughly the same size as ever thing else without confusing everyone involved or breaking the kanban 'flow'. Cheers on the video, I learned a lot!
Hey, Andy, That's a good question. First of all, let's define what a big task means. As a rule of thumb, I try to keep an individual assignment no bigger than 3 days. If it's more than three days, it's better to break it into smaller tasks. There's a lot of theory why you don't want to have tasks longer than that. Now, if we talk about Kanban, approximately the same size can mean a task of 1-5 days long. If you are within these limits, you should be ok. So, do you have tasks bigger than that?
@@ITProjectManagers Thank you for the reply! The thing is that I might not really know how big the task is or how long it would take; with a small team and my level of experience it's hard to guage how long things will take. As an example though, we have a whole new feature for our app. We want to be able to hold events that any user can join. You need to allow people to create events, others to apply and then the creator of the event to choose who they wish to come to the event (think a talent show or something). There are loads of moving parts to this and what makes it harder, is that it's built on top of the already functioning app, so moving things along a normal PR/QA/release scheudle on a Kanban can be quite tricky to imagine. What I came up with was to split into two Kanbans. You have a main kanban that handles all of the day to day tasks, but then also have the Kanban for the new feature/project. That new feature/project has smaller task tickets (build the UI, create the foms, results selection pages, etc.), but also has a single ticket for the entire feature on the Main kanban. I know this is all case by case, but was just curious how proper PM's normally work through these sorts of projects happening at different times, but working in the same environment. Thanks again for the response and sorry for my long reply hahah
There are no standards here. You need to find the most efficient setup for you team through trial and error. Start with main In Progress column and set WIP to the number of contributors. Then decide in what columns you DON’T want tasks to accumulate and lower WIP for it.
![Jira - Tutorial for Beginners in 12 MINUTES ! [ FULL GUIDE 2024 ]](http://i.ytimg.com/vi/fiWaMGCMyk8/mqdefault.jpg)
![Lethal Company Music Video 🎵 "Follow The Orders" [VERSION A]](http://i.ytimg.com/vi/QeooZB4Z7RA/mqdefault.jpg)
🔥 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?
Yes. Please make a detailed video on CI/CD with the perspective of a project manager.
Thanks for feedback! Will do:)
Thank you for the 101 Kanban knowledge
1. What if QA fail, do we ask developer to fix until it is ready to deploy? But how will you prioritize the ongoing task and Fail QA task on Kanban.
2. Interested in CI/CD 🙏
You are welcome. Good questions.
1. If QA fails while a task is still on the board, then you need to make developers fix all critical defects. Again, it's a matter of DoD to specify what defects are acceptable. If you find a defect in production later, create a new ticket and prioritise it accordingly.
2. Treat defect and tasks equally. Then, priorities them as you see fit.
In some cases, you can override all current work and expedite one ticket. For example if it's a super critical defect on prod.
Can you do a JIRA tutorial?
I have a video on Jira. But it’s a bit advanced version: Is Jira Ready for IT Projects in 2023? | How to Use Jira
ruclips.net/video/KjUAVFrqOVs/видео.html
But i plan to create a beginner’s guide somewhere soon.
Great video for helping people understand the basics of kanban
Thanks for your feedback, Yomi! Much appreciated.
Hello Dmytro, thanks for the cristal clear explanation about Kanban. I would be interested in CI/CD videos. And of course, more Jira related topics. It would be great to have a full playlist. E.g.: going from beginers to advanced.
Hi Alexander,
Thanks for writing. Noted! I have plans for Jira video for beginners. CI/CD is also in pipeline.
This is excellent. Thank you.
You're very welcome!
Great explanation!
Glad it was helpful! Thanks for feedback. It means a lot to me.
Congratulations! This is a brilliant video ! You gain a follower and a strong supporter! Big THANK YOU! KR Sascha
Thank you very much. Sascha!
Hey there Dmytro, I'm a bit late to seeing this video, but as a Junior Dev being pushed into his first PM role, this video is very helpful.
My only real question is how do you make all tasks "Approximately the same size"? If I have a big feature like, a analytics dashboard, how can I make tasks the same size? I could break that big feature up into UI task, database connection tasks, etc. But in a small company I wouldn't want multiple developers working on smaller parts of the same feature, I think that brings in too much confusion and requires way too much coordination. I would've just assumed that you assign that one ticket either yourself as the PM OR through triaging with your dev team.
Sorry if that question is a big abstract, but I don't really understand how you can truly break somethings up, yet keep them roughly the same size as ever thing else without confusing everyone involved or breaking the kanban 'flow'.
Cheers on the video, I learned a lot!
Hey, Andy,
That's a good question.
First of all, let's define what a big task means. As a rule of thumb, I try to keep an individual assignment no bigger than 3 days. If it's more than three days, it's better to break it into smaller tasks. There's a lot of theory why you don't want to have tasks longer than that.
Now, if we talk about Kanban, approximately the same size can mean a task of 1-5 days long. If you are within these limits, you should be ok. So, do you have tasks bigger than that?
@@ITProjectManagers Thank you for the reply!
The thing is that I might not really know how big the task is or how long it would take; with a small team and my level of experience it's hard to guage how long things will take.
As an example though, we have a whole new feature for our app. We want to be able to hold events that any user can join. You need to allow people to create events, others to apply and then the creator of the event to choose who they wish to come to the event (think a talent show or something).
There are loads of moving parts to this and what makes it harder, is that it's built on top of the already functioning app, so moving things along a normal PR/QA/release scheudle on a Kanban can be quite tricky to imagine.
What I came up with was to split into two Kanbans. You have a main kanban that handles all of the day to day tasks, but then also have the Kanban for the new feature/project. That new feature/project has smaller task tickets (build the UI, create the foms, results selection pages, etc.), but also has a single ticket for the entire feature on the Main kanban.
I know this is all case by case, but was just curious how proper PM's normally work through these sorts of projects happening at different times, but working in the same environment.
Thanks again for the response and sorry for my long reply hahah
Hello, where can I find the Gcalc board you mentioned in the video?
It's on my account. I didn't share it...
what are the rules to set wip?😊
There are no standards here. You need to find the most efficient setup for you team through trial and error.
Start with main In Progress column and set WIP to the number of contributors. Then decide in what columns you DON’T want tasks to accumulate and lower WIP for it.
@@ITProjectManagers appreciated that. Thank yoy
🖖🏻 Agreed 💥
Nice! Thank for the feedback.
good video
Thanks for watching! I'm glad you enjoyed it!