Is it appropriate to run a complex enterprise-system configuration and migration project in a similar way to a Scrum development project?

Question

I'm just starting out on the implementation of a large enterprise-wide system, which has complex requirements and many stakeholders.

The company has been through high-level evaluation and tender process and determined to purchase a highly configurable "off-the-shelf" product rather than building an entirely bespoke system. The system will replace several existing systems and will require a significant amount of data migration.

I'm thinking that the implementation of this system (which is expected to take over 2 years) could be run in a similar way to a Scrum software development project.

With the first sprints targeted at building the minimal possible functionality needed (across all functional areas), and then iteratively deepening the level of functionality according the stakeholder feedback. I think this will de-risk the project and help ensure a balance of stakeholder needs within the available time.

The user stories are still the same, it's just that to implement them we have work within the constraints of the pre-purchased system. When it comes to 'building stuff', instead of writing custom code the team will be configuring the off-the-shelf package, writing data conversion scripts and the like (and it should be a lot quicker!).

Does this sound like a sensible approach? Does the Agile approach makes sense here?

Answer 1

As AlexBottoni already mentioned SCRUM can be used because even customizing is software development.

But for your approach to do several sprints in creating basic functionality is the wrong way. Get one of the existing systems and replace it with the new solution. This should be done in only a few sprints. Select only few user stories at first to implement. When the first system is replaced get the second one. Don't try to replace everything at once because then it is more likely to fail. Even if it seems to cost more time it is worth to replace one system after another. Also then the management will see faster what will be achived.

If you take two years to replace everything the current systems will be developed further and you have a moving target...

Answer 2

Despite the use of an off-the-shelf product, this is a software development project and will have to be run accordingly (withs SCRUM, Agile and/or other methodologies).

As you said, you will have to write migrations scripts, configuration files and so on. This is software development. Anything else.

You will have to use a source code versioning system like GIT, Hg, Subversion or CVS. You will have to keep track of bugs and requested features. You will have to document what you are developing. You will have to test your system.

This is just "software development", so your approach is more than sensible. It is mandatory.

Agile development almost always make (at least some) sense. Sometime it has to be used together with others (more formal) methodologies but it is almost always a good starting point.