Affinitiv - Technical Analyst

• A key element of defining system requirements includes creating data dictionaries, data flow diagrams, and other artifacts to ensure products are delivered on time and to specification. • Preparing functional requirements. A technical process analyst is also responsible for documenting functional requirements. These are the product features that engineers implement to allow users to achieve their goals. This includes clarifying the primary purpose for the product or feature and evaluating the most relevant means of implementation that both meets needs of stakeholders and development teams while providing a solution to meet the customer’s business objectives and including what the expected outcomes will be for the defined solution. Hence, a BPA’s role is documenting it clearly for both developers and stakeholders. • Formulating the main backlog. Ensuring a general outline of the project is defined within a backlog to formulate a basis of an instructive to-do list. A technical analyst ensures that all business aspects discussed earlier are reflected within the cases in the backlog. This includes examining emerging business best practices and technological developments that can help to automate and streamline processes for customers and the organization to help business units or our customers perform more efficiently. • Formulating the main backlog. • They are required to evaluate customer, employee & stakeholder needs, internal & customer workflows and business processes to be able to document and define requirements of product and feature needs. • They conduct meetings with different stakeholders and participants in various parts of operational processes, analyze the information received. • Document software implemented by development team for future reference by the development team and other internal departments. • Document decisions and the supporting reasons for the action made at each team and stakeholder meetings. • Technical Process Analysts gather information through process mapping, flow-charts, and workshops. This information can then be used to develop better process engineering or software solutions, this is also used as the basis for their documentation of solutions. • Their primary goal is to assess business requirements and make evidence-based recommendations to support process improvements and document through BRDs, User Stories, Flow Charts, and any other supporting format, the requirements to be conveyed to product and engineering teams. • Builds and maintains inclusive cross-functional partnerships directly with key stakeholders across our Product, Engineering teams. • Presents how the product's features support the business strategy and service delivery model. Provides data and recommendations for decision making to impact the product and roadmap, may update or own some of the product management documentation. • Co-ordinates with internal resources on complex research and analysis from idea generation through implementation. • They are required to be great with interpersonal and communication skills, report writing abilities, an aptitude for analyzing data, and great business acumen. • All other duties as assigned