Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  General  Document Management Strategies
Previous Previous
 
Next Next
New Post 11/25/2014 8:25 AM
User is offline JetCityWoman
2 posts
No Ranking


Document Management Strategies 

We use Sharepoint at my company to store all documentation but it seems disorganized to me so I'm wondering about better ways to organize it.  We build business software systems, so we have documentation for products (the systems that we sell) as well as projects (changes to the systems).  The requirements documents for our projects are all listed in one central place in Sharepoint, in alphabetical order.  We don't seem to maintain a "master" set of requirements documents at a product level, so if you want to know when a particular feature was implemented, you have to search through all of the project workspaces.

For the products I'm responsible for, I think I would like to have a workspace that contains all documents related to the product in chronological order; so the original product requirements and also all of the project documents.   I am also toying with the idea of starting and maintaining a master set of product requirements, which would be all of the project requirements combined into one document.  Is this biting off way more than I can chew?

Does anyone here work in a similar environment, and if so how do you keep things organized so that it's easier to track changes to the product over a long period of time?  The goal is to be able to look back and see when and why (x) feature was done, without having to explore the entire Sharepoint library.

 
New Post 12/1/2014 6:20 AM
User is offline JetCityWoman
2 posts
No Ranking


Re: Document Management Strategies 

Pardon replying to my own post, but I want to add an example of an issue I am encountering as an example of why I want to do this.  I'm a new analyst at this company and inheriting documentation from past analysts.  I felt that I thoroughly documented some new changes needed on one of our systems, but when the developers dug into the code they found some existing logic that wasn't mentioned in the documents that I modified.  Existing behavior that either wasn't documented (agreed to verbally? ) or is documented in some other project workspace for the same system.  If I want to find out if that logic is documented and look for other "gotchas" that I don't know about, I have to browse through more than 10 years worth of different project workspaces. 

 Has anyone here dealt with this problem before, and how did you handle it?  

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  General  Document Management Strategies

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