Skip to content


What does a BA do?

I am often asked, “What does a Business Analyst do?”

Saying “we help business do better business” doesn’t really describe our role.

A BA can perform a wide range of tasks from day to day, project to project, and even from business to business:

  1. Identify and separate the categories of requirements categories;
  2. Determine the correct templates to use for a project;
  3. Define/refine the checklist of requirements activities, deliverables, and schedule;
  4. Create a defect checklist for all templates that lists common requirements errors;
  5. Determine assumptions and constraints;
  6. Help peers check to determine if the requirements are high quality and complete in breadth;
  7. Document all requirements-related terms, enterprise acronyms, and business domain language in an appendix to the requirements document or in a separate glossary;
  8. Assemble and educate the core requirements team, composed of key business and technical stakeholders;
  9. Gain an understanding of the needs and environments of customers, users, and stakeholders;
  10. Review or create if non-existent, the business case, project charter or similar scope definition document;
  11. Examine the business case for a list of business drivers; continually link project work to the expected benefits outlined in the business case;
  12. Understand the business vision, drivers, goals and objectives for the new/changed system;
  13. Understand and further document the scope of the project;
  14. Define the deliverables and models to be produced and begin to develop the requirements management plan;
  15. Plan for change throughout the life cycle;
  16. Customize the project complexity model to the project environment;
  17. Collaboratively determine the size/risk of the project and establish plans accordingly with the project manager and key business technology experts;
  18. Bridge the gap between the project team and the stakeholders by building creative partnerships, conducting voice-of-the-business surveys, and securing customer input by creating focus groups, business panels, and cross-functional decision teams;
  19. Explain the business value expected from the project to all stakeholders to regularly confirm the primary needs that are driving the project;
  20. Develop or refine stakeholder analysis before beginning elicitation activities;
  21. Use the stakeholder analysis to determine and manage early requirements-related tasks;
  22. Identify a champion for each user group;
  23. Make the user champion a key member of the requirements elicitation team;
  24. Establish and document ground rules for making requirements decisions and resolving conflicts;
  25. Enlist the project manager and the business and technical leads to determine the project life cycle and delivery approach to be used for the project; and
  26. Tailor and customize the requirements activities, deliverables, and reviews based on the needs of the project with everyone involved.
  27. Plus much much more…

Posted in Business Analyst, Checklist.