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 8: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 11: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

Samuel02
Samuel02
With the advent of modern-day cloud infrastructure, many business-critical applications like databases, ERPs, Marketing applications have all moved to the cloud. With this, most of the business-critical data now reside in the cloud. Now that all the business data resides on the cloud, companies need a data warehouse that can seamlessly store the da...
0 Responses
BPM_online
BPM_online
Bpm'online, a global business software company leading in the space of low-code, process automation, and CRM, will be soon announcing their new company name. The new name will be launched in the sky via a breathtaking skydiving performance involving 160 bpm’online employees, including the CEO. The new name of bpm’online is to be fo...
0 Responses
Heta Raval
Heta Raval
In a current scenario, when you are eliciting software service-based requirements then, you may be able to derive requirements in certain varieties. In the beginning, they can be just functional or non-functional requirements. But when you come across many other requirements as time goes, you can conclude requirements into several categories and wi...
0 Responses




Latest Articles

What’s Missing from Agile?
Oct 20, 2019
0 Comments
John Seddon launches an attack on the value of Agile as practiced and charts a better way to analyse and design for improvement, making information te...
Copyright 2006-2019 by Modern Analyst Media LLC