Eeeh it really depends on your software release cycle too.
Kanban is great for hosted/cloud web apps/offerings. You can push changes right away that affect all of your customers and given that it's on your side of the business (and don't have to worry about 10 different implementations on different platforms like on-prem). Good testing coverage is great. Major points if you use Git tools to manage your current release version.
Scrum is great for on-prem offerings (meaning you download a software to install). You get more time to test/integrate between releases and you can commit to certain deliverables. Scrum can also work for cloud offerings too.
I have a team that I manage that uses Kanban and another that uses Scrum, the first one works mostly in a cloud setting and its great, we pretty much push live constantly. The other team has set timelines for deliverables (such as we need this by the end of the month for a deal, or before a conference). I can see my portfolio and check if we're on track for the releases (on both ends).
I do say, in the Kanban one given that we pretty much push live almost everyday our test coverage has to be top notch and usually my testers are more worked than Scrum testers. Scrum allows for proper planning and other departments love it (such as marketing) because I can tell them when they'll get certain features so they can plan around it, however Scrum is a nightmare integration testing(given that not everybody merges back up the tree daily).
In all, your program managers are the ones that need to be on top of shit. Properly plan and break down your stories; measure velocity and complexity, be on top of your blocks, keep your stakeholders in the loop. Don't hesitate to say no.
Kanban is great for hosted/cloud web apps/offerings. You can push changes right away that affect all of your customers and given that it's on your side of the business (and don't have to worry about 10 different implementations on different platforms like on-prem). Good testing coverage is great. Major points if you use Git tools to manage your current release version.
Scrum is great for on-prem offerings (meaning you download a software to install). You get more time to test/integrate between releases and you can commit to certain deliverables. Scrum can also work for cloud offerings too.
I have a team that I manage that uses Kanban and another that uses Scrum, the first one works mostly in a cloud setting and its great, we pretty much push live constantly. The other team has set timelines for deliverables (such as we need this by the end of the month for a deal, or before a conference). I can see my portfolio and check if we're on track for the releases (on both ends).
I do say, in the Kanban one given that we pretty much push live almost everyday our test coverage has to be top notch and usually my testers are more worked than Scrum testers. Scrum allows for proper planning and other departments love it (such as marketing) because I can tell them when they'll get certain features so they can plan around it, however Scrum is a nightmare integration testing(given that not everybody merges back up the tree daily).
In all, your program managers are the ones that need to be on top of shit. Properly plan and break down your stories; measure velocity and complexity, be on top of your blocks, keep your stakeholders in the loop. Don't hesitate to say no.
