BA Technique #18: Document Analysis

Reviewing and analysing existing documents, such as policies, procedures, or business requirements, to extract relevant information

Erivan de Sena Ramos

--

Photo by DCP on Unsplash

What’s shaking, BAs? We’re back with another thrilling Business Analysis technique from The BABOK Guide v3. Hold on tight as we embark on an exciting adventure through the realm of Document Analysis, as we explore how this technique supports extracting valuable insights and uncovering hidden information to fuel our analysis and drive informed decision-making. Let’s get hands-on with it!

What is this technique about?

Originating as an academic research method, Document Analysis involves reviewing materials to enhance understanding and develop empirical knowledge. Researchers commonly analyze existing literature and incorporate relevant information into their reports.

In Business Analysis, Document Analysis plays a crucial role in examining and analyzing various business documents, such as reports, policies, contracts, and financial statements. It helps Business Analysts gain insights, identify patterns, extract valuable information to support decision-making, identify business requirements, and understand the current state of the organization. Through Document Analysis, business analysts can uncover critical details, assess risks, and contribute to the development of effective strategies and solutions.

How to apply this technique?

To effectively apply Document Analysis, you can follow these suggested steps:

  1. Identify Relevant Documents — Identify the documents for the business analysis initiative. Gather various documents, including project documentation, policies, guidelines, and existing business artifacts.
  2. Review and Analyse — Conduct a detailed review of the selected documents to extract pertinent information. Additionally, identify key stakeholders and subject matter experts who can provide insights and clarifications. Analyse the content of the papers, paying attention to patterns, dependencies, and critical information.
  3. Document Understanding and Summarisation — Summarise the essential findings and…

--

--

Erivan de Sena Ramos

Business Analysis & Requirements Engineering enthusiast. Information Systems & Software Engineering specialist. MBA in PM & HR. CBAP, PMP, CSM, ITIL & COBIT