Now that we had a look at some of the different types of business analysis information that exist, it would be easy to agree that the organization of all these types of business analysis information is important.

The earlier in the project you are able to start planning how you want to organize the information the better, simply because this means you will limit the chances of misplacing information, everyone on the team will know where to find information, and you will avoid unnecessary duplication of information. 

It is, however, not always practical or realistic to know the best structure and process for organizing information from a very early stage in the project and so it is a good idea to start with a simple but robust enough organizational system to enhance and improve during those early stages of the project. You will then be in a good position to have an efficient and effective way of managing all the business analysis information when the project starts to mature and develop.

An example of a common approach when organizing business analysis information could be something like the following:

Create a document management repository with a file storage area (or folder) for the documentation for each main phase (or iteration) of the project. Then, have a sub-folder area for each main type of document. For example, there might be an area for all the analysis stage documents, which is sub-organized into "Elicitation Output," "Requirements," and "Project Meetings."