Forums for the Business Analyst

  Modern Analyst Forums  Business and Sy...  Data Analysis f...  Data migration user story writting
Previous Previous
Next Next
New Post 4/22/2019 11:59 PM
User is offline Ash 02
2 posts
No Ranking

Data migration user story writting 

I have recently started working as a BA, my role is to capture user stories related to data migration from legacy to new. 
I need help with some sample user stories for data migration. 

For example if abc screen data from legacy system is migrated and as new system user i want to view the transferred data on xyz screen. 

Note: the purpose right now is to view the migrated data. so i am confuse with how to write what benefit the user story will add.

Thanks in Advance!!


New Post 8/2/2019 3:19 AM
User is offline Stewart F
109 posts
7th Level Poster

Re: Data migration user story writting 

Hi Ash, 

As part of your tasks carried out so far, have you mapped what data will go where? For example, the 'Client Address' field in Legacy system will map to 'Primary Client Address' field in New system.

This data mapping will be crucial to the success of your task. Developers etc will need to know where all the data goes. You could write a User Story for each and every field, and without knowing how many of them there are its a little hard to advise, but I would complete a table in Excel or something similar. Have one column which states what the Legacy field is called, another stating what its format is (is it alpha characters only for example), the next column says what the maximum character length is in legacy system. The do the same column, but for the new system.

You will need to make sure that the new system fields at least match the old fields, otherwise yo wont be able to move the data over (you'll get errors all over the place). You may need to speak to stakeholders to find out how long they want fields and what sort of data is to be entered into the fields (just alpha, alpha & Numeric etc.).

Then, once that exercise is complete I would speak to the developer who is doing the data migration, and see how he/she wants to split the User Stories out. Do they want just one User Story, or multiple? Create the User Stories as advised by your Developer and make sure you attach the Mapping table to it, so that the Developer can relate to it. 

Previous Previous
Next Next
  Modern Analyst Forums  Business and Sy...  Data Analysis f...  Data migration user story writting

Community Blog - Latest Posts

Is Agile a reason to avoid documentation? I bet this question shows up again and again while working with product requirements. On one side, we have got long specifications, complicated diagrams, mystical technical design, too many prototypes and pretty obvious for engineers user guides (do we really need so much?). On the other side, can we actual...
The cloud-native application development has helped enterprises all around the globe reduce time-to-market, enhance performance, and develop agility and flexibility. Several enterprises are achieving these results by migrating their systems or traditional monolithic applications to the cloud. But to gain from the real benefits of cloud technology, ...
So you’ve found the perfect time and place to study and you’re ready to finally get some work done. You’ve pulled out your laptop, your textbook, and your notes, and four different highlighters. After five minutes of reading your textbook, you start zoning out and thinking about puppies. Then, you go on Tumblr and look at cut...


Upcoming Live Webinars


Copyright 2006-2021 by Modern Analyst Media LLC