Hi Jeroen,
Thanks for your feedback. When I engage with teams tasked with creating new features and with maintaining the product, I often suggest to use Scrum to develop the new features, and a linear, Kanban-based process to manage the maintenance work. I find it more challenging when a team creates a brand-new product and has to take care of maintenance and support work at the same time. My preference is to allow the team to focus on the new product and release its members from the maintenance duties.
Does this help?
]]>This post works for teams who only work on product innovation. I have seen a number of teams that work both on product innovation and customer projects (mostly smaller companies). This mixes Stage 1 & 2 and can get some conflict sometimes.
]]>