Business requirements analysis is done by the business analyst (BA) in close collaboration with the product manager (PM) to have better and more well over thought solutions solving customer problems which will improve the decision making process and have a more efficient start of the development teams.

• More efficient work process from roadmap item to product
• Substantiated decision-making (why are we going to do or not do something? data driven!)
• Better elaborated/analyzed epics/features (estimation of complexity, time, required resources)
• Better predictability
• Reduce recovery costs, the more early detected (or prevented), the cheaper it is

• Determine target groups and what their needs are
• Collect, record and analyze data
  • Internal data (inventory, link, analyze)
  • External sources (inventory, link, analyze)
• Describe the current situation, are there alternatives (competitors, tax authorities)
• Describe potential target groups (current customers, but also untapped customers)
• Clarifying how epic fits within our landscape, from high level to more detail

• Documented analysis with business context, goals, needs and objectives, see template
• Elaborated and validated requirements
• Product backlog with epics - features - user stories (incl Business Requirements)
  • Worked out in the right way, not too much detail, but not too high level either