I completely agree with this.<p>In shorthand, having been Product Manager for a number of teams at a variety of companies in several industries, I&#x27;ve found that Scrum is better for teams developing mostly new features, with relatively little maintenance; and Kanban better for teams focused primarily on maintenance, with fewer large features.<p>The rationale is really simple: for new feature launches, reporting and tracking vs. schedule is key; for maintenance, throughout is key.<p>That said, regularly missing predicted story points by more than about 10% is not the sign of a healthy team. Being bedeviled by routine bug fixes is not the sign of effective management. Both are routine issues that most highly-effective teams, whether Scurm or Kanban, deal with well.