Beginner's Guide to Kanban for IT Project Managers 

Thanks for feedback! Will do:)

Thanks for your feedback, Yomi! Much appreciated.

You're very welcome!

Thank you very much. Sascha!

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.

Hi Alexander, Thanks for writing. Noted! I have plans for Jira video for beginners. CI/CD is also in pipeline.

Glad it was helpful! Thanks for feedback. It means a lot to me.

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 ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-KjUAVFrqOVs.html But i plan to create a beginner’s guide somewhere soon.

Nice! Thank for the feedback.

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

It's on my account. I didn't share it...

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