Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Structured Anal...  Where to start documenting a Legacy System
Previous Previous
 
Next Next
New Post 2/2/2020 11:23 PM
User is offline Stewart F
96 posts
7th Level Poster


Re: Where to start documenting a Legacy System 

Hi Kimbo,

Not disagreeing with you, but the point I was trying to get across is who you would need to ask to get an understanding of what the As-IS was. I would also say that if you are going to go via external 3rd party vendors, they wont care too much about your internal processes. All they will be interested in is the interfaces, which any external system will need to make sure it can integrate with. 

Whilst you are having those discussions (which take quite a while) then you can go through the internal processes, but in order to know who to ask, you first need to find out who the key stakeholders are. Those that I mentioned, The Developer and The Product Owner should have had a good idea who internally they spoke to when they first built the system, therefore you save some time by speaking to the relevant experts. Remember, the experts aren't always those in power. 

 

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Structured Anal...  Where to start documenting a Legacy System

Community Blog - Latest Posts

Gen1us2k
Gen1us2k
Most of the IT projects imply constant cooperation between the team members and customers. Although it might be often overlooked, the role and the importance of the client within the project is very crucial. Thus, it is in your interest to build a strong relationship based on trust. However, gaining trust on a single occasion is not a dealmaker &md...
0 Responses
emorphistechno
emorphistechno
Introduction In today's world, most enterprises work aggressively to achieve a higher level of business growth, which is made possible by leveraging one of the best automation technologies. One such technology is Robotic Process Automation (RPA) that plays a vital role in streamlining the customer experience in the most profitable manner.&nb...
0 Responses
Nick Stowers
Nick Stowers
Introduction   When I was introduced to scrum, the burndown chart was a tool that was highly emphasised however I feel the purpose has changed from it being a tool to predict (to a certain level) timescales for delivery to a tool that measures a team’s productivity…..in other words, the focus is on the number of points clear...
0 Responses






Latest Articles

Copyright 2006-2020 by Modern Analyst Media LLC