“The IT Business Analyst:

• Defines: Together with primary stakeholders the IT BA slices EPICs into features and identifies the functional interdependencies between features of an epic, resulting in a functional dependency roadmap.
• Elicitation of requirements: The IT BA engages with stakeholders (business, architecture and IT) to understand their needs, and translate them in detailed requirements deliverables. Subsequently listing out requirements, categorization and prioritization (MosCOw) and manage these accordingly. Tools can be usea like Azure DevOps Boards. Applying elicitation techniques such as user story mapping, impact mapping, epic/ feature/user story slicing.
• Analyzing: The IT BA uses data, processes, and systems to identify areas for improvement, and propose solutions. Use of quick scan template to support feasibility, and identify any alternatives.
• Documenting: documents requirements through functional requirements specifications and functional feature design, using techniques such as use-case specifications, sequence diagrams, state diagrams, etc. and using specification languages such as Gherkin.
  Modelling: The IT BA models requirements in relation to information structures, functions and behaviour of sustems. Using techniques such as: Unified Modelling Language (UML), Data Modelling, Entity-Relationship Modelling (ER), Context Modelling.
  Tests and validates: The IT BA verifies that the delivered IT-solution meets the requirements, supported by use case translation into high level test cases.
  “