Business analysis documents: Current State Analysis

This article is the first in a series describing business analysis artifacts, their purpose and internal structure

I’ll talk about these documents:

  • Current state analysis document
  • Project vision document
  • Solution vision document
  • Business requirements document
  • Business process design document
  • Use case model document
  • Use case specification document
  • System-wide requirements document
  • Solution glossary

Once I’ve described those, I’ll go on to show the relationships between the artifacts.

The picture below illustrates the information common to every artifact. The area indicated by the “Main content” arrow should be filled by the appropriate document-specific content discussed throughout this series of articles:

artifact structure

Current state analysis

Once a project has been mandated and the Project Initiation document (PID) is drafted, a business analyst can start to work on requirements gathering. In my experience the best way to tackle this task is to start from current state analysis. It helps understand the business need, primary pain points, business processes affected, the stakeholders involved in these processes, and so on.

The area of the current state analysis is illustrated below:

current state analysis area

The main purpose of the analysis is to present the “AS IS” state: the existing business context, background, business functions and existing business processes, and finally stakeholders involved in these business processes. Depending on the project nature, some components of the underlying infrastructure can be included in the document as well.

A Current State Analysis document lists the key pain points within the identified business processes and tasks within them, and highlights the areas where a change is expected.

The last section of the document is about presenting recommendations. It recaps the key findings and lists the key changes expected. Any caveats should be presented here as well.

The content structure of the Current State Analysis document is presented below:

current state analysis structure

This artifact serves as a foundation or a reference point for other artifacts produced by a business analyst. The other documents will be discussed in the following articles.

Did you know the posters from Business Analysis Illustrated are now available to purchase individually?


Did you like this post? Subscribe to the mailing list for more BA articles, posters and an occasional special offer on our products.

Fill out my online form.

6 Responses to “Business analysis documents: Current State Analysis”

  1. Is it sufficient to rely on another group, such as the software vendor, to perform the "as is" analysis, or should the business analyst use this as a guide and verify the findings?

    • Becky
  2. Thanks for the comment Becky. We think it's better not to rely on other groups because the business analyst will have deeper knowledge of the business. Their findings can be used to supplement the analysis in case anything has been missed.

  3. @Becky, I agree with Aotea Studios, Your findings might be used as a validation document to vet answers to RFP's or even RFI's…
    Also helps you to benchmark and build comparisons against software vendors who are tendering for those very same RFP's.

    • Natey
  4. The links to the diagrams are broken.

    • kdp
    • Sorry about that, fixed now.

      • Alex
  5. Hi, the links do not appear to work?

    • Sam