how to use Scrum Agile framework for data migration projects for regulated business stakeholders
We are currently in the process of deploying data migration projects as per the request of our business stakeholders. The objective is to recreate the same tables found in two major proprietary systems, one being transactional and the other a database, within the cloud solution we have acquired. These tables are highly regulated by specific business rules, and it's crucial that all the fields and components are replicated accurately in the new cloud environment to gain approval from our stakeholders.
In our endeavor to deliver using Agile methodology within the Scrum framework, we are facing challenges in defining these tasks as Epics, stories, and other related components to align them effectively with Scrum principles. One significant issue, among others, is that until a table mirrors all the fields and attributes of its older counterpart, it won't pass the quality assurance process.
We understand that the situation may appear to resemble a Waterfall approach, but in this context, it's imperative that we utilize the Agile Scrum methodology.
I would greatly appreciate your expert insights and suggestions on how best to leverage the Agile Scrum methodology for this specific purpose.
Thank you in advance .
Scrum isn't a methodology, it's a framework for solving complex problems. Where are the risks and uncertainties in this data migration initiative? It sounds complicated rather than complex, in that people already know the many different things they will need to do. Why is it imperative that you use Scrum here?
Agree with @Ian. I'm not seeing a reason that the Scrum framework would be extremely beneficial. It seems like a fairly well understood project with some complicated requirements but not overly complex.
I will also call out this statement.
In our endeavor to deliver using Agile methodology within the Scrum framework, we are facing challenges in defining these tasks as Epics, stories, and other related components to align them effectively with Scrum principles. One significant issue, among others, is that until a table mirrors all the fields and attributes of its older counterpart, it won't pass the quality assurance process.
Everything about that sounds like you don't really understand the Scrum framework. Epics and stories are not mentioned anywhere in the Scrum Guide. Having a "quality assurance process" that will not allow for incremental delivery of value also goes against the Scrum framework. You should be able to deliver usable increments of value that meet the Definition of Done and support the Sprint Goals without having a table that is fully duplicative of the original.
Since "it's imperative that we utilize the Agile Scrum methodology" you may want to read whatever documentation you have on your "Agile Scrum methodology". If you shared it with us, we might also be able to help you out. You might also share why it is imperative that you use it. We could give you some advice on how to use the Scrum framework but I'm not sure that is what you are actually asking us to do.
@Ian Mitchell and Daniel Wilhite
Thanks both for your reply!
All I want to know is that how you are defining a data as a product? Because we all know that when we talk about an explicit product such as a video game or a Power BI dashoboard it can very well be laid out according to Scrum framework but how we can can go for the data as a product mindset(with some examples as data migration and creating data entities, etc.) if we intend to use Scrum framework to tackle it!?
Data may be a product if it represents a value stream that is worth accounting for and optimizing. Whether Scrum should or should not be used depends upon the complexity of the challenge, and the need to empirically manage risks and unknowns.
There's no imperative to use Scrum unless there is complexity to be brought under empirical process control. The data migration initiative you describe sounds complicated, and yet quite prescriptive and therefore non-complex. It might be complex however depending upon the people involved, such as stakeholders and their expectations or developer interactions. Most of the complexity we deal with actually comes down to people.
Hi Ardio, It may be worth exploring the differences between complex, complicated and clear work. Check out the Cynefin framework or Stacey matrix to learn more. Here is a video by PST Ryan Brook on complexity that might help: https://youtu.be/KvkhSlixAfg?si=67KzH8hTVEMEZ-CK.
"crucial that all the fields and components are replicated accurately"
This implies you know what to build and how to build it. The work seems Clear or perhaps Complicated. Not Complex.
Scrum is an amazing framework for complex work, but if your work isn't complex, and doesn't require adaptive solutions and empirical learning, the juice might not be worth the squeeze. There is effort and rigour required with Scrum, and its structure and rules support working empirically. If you don't need this, it may be the wrong tool for the job.
All I want to know is that how you are defining a data as a product?
In your case, data isn't a product. The two tables you are creating are the product. They are the elements that are providing the value. The data is part of the solution, just like in a video game or Power BI dashboard.
In the scenario you are describing, why do you need to use Scrum? It seems fairly obvious what needs to be done.