Is it worth working in 2-week sprints, and in a Scrum fashion for that matter, for a client migration project from a legacy system, to a system which is already live and with other clients (a white label software)?
It seems to me to be somewhat futile to try to fit tasks into 2-week sprints, since whether they’re delivered or not, no one is going to complain (since the client is already live on a legacy software). The only effect will be to move the migration date (that has been set by a project manager) to an earlier or later date, which is reviewed every 2 weeks.
I think a Kanban style is more appropriate, as the workload is known (no surprises or areas to explore) and it’s going to take however long it’s going to take to deliver the software. There’s no added functionality as it would be with incremental releases in Scrum, because the client is still on the legacy system. Can anyone provide any reasons for or against using Scrum for clients' migration from legacy products to new live products?