Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Migration from legacy to New System
Previous Previous
 
Next Next
New Post 7/12/2012 7:42 AM
User is offline Niks
8 posts
10th Level Poster


Migration from legacy to New System 

Hello,

Currently I am working on project which is a migration from Legacy System. When I joined on -board for the project, it was in transition phase.

There was a Project Manager and BA working prior on this project. But now PM aand BA has been changed and asked to fix the mistakes done by previous team.

I have been appointed as BA for the project. I dont know what direction I should follow. I have asked my PM to guide me on this matter but either he is not interested or dont have enough information. And there are some expectation from me regarding performance and delivarables. I have previous BRD with all the comments made by previous team. But on my current team nobody thinks that the previous version is in good shape.

I am very confused as to what should I do and how should I proceed in this matter.

All the expert suggestion are welcomed.

 

 
New Post 7/12/2012 10:26 AM
User is offline Tony Markos
493 posts
5th Level Poster


Re: Migration from legacy to New System 

Hi:

Your first step is to realize what the main problem is.  It probably is not a data migration (i.e., transfer) problem.   When you have a spec of the required behavior of the system (BRD as you call it), I suggest always looking at that first.   Even if a big part of your problem is data related, process requirements drive data requirements.

So what is wrong with the BRD?    Is it written so that only a techie can understand it?  Is it entirely text based?   Is it written in business english, but, disjointed?   Is there a Context Diagram that nails down the scope, or, as is often the case, the scope is very vague?

Be aware, especially if the system is complex, the issue it is not so much identifying the stand alone behavioral requirements as it is understanding the interrelationships between the requirements. In all candor, what I would do first is create some higher level data flow diagrams, with an emphasis upon using only business terminology.  And then I would walk through them with stakeholders. 

Tony

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Migration from legacy to New System

Community Blog - Latest Posts

As Business Analysts in Agile teams, we often hear about Definition of Ready (DOR) and Definition of Done (DOD). But beyond the buzzwords, these two concepts are powerful tools to drive clarity, consistency, and quality in our work. Definition of Ready ensures a user story is truly ready for development. It answers: Is this story clear, feasible...
In today's fast-paced digital world, successful projects aren't just built on great code—they're built on clarity. And that clarity often comes from one key player: the Business Analyst. At the heart of every great product or system is a need—a business goal, a customer pain point, or a regulatory requirement. But busines...
I have always loved cooking. I learned from my Grandma June and her kitchen was her sanctuary, a small, warm sunlit space filled with jars of spices, stacks of cookbooks, and the comforting smell of something always on the stove or baking in the oven. Grandma June was as great a cook as she was a teacher to me. She never followed a recipe “to...

 






 

Copyright 2006-2025 by Modern Analyst Media LLC