The use-case-driven integrated business requirements (IBR) document is key to the iterative development of the solution to integrate multiple technology solutions. The IBR has to be crisp enough for stakeholders to understand the business objectives for the iteration, but also detailed enough for the point solutions to develop functional design and to build on it. The IBR has to provide the following details:
1. Business requirements:
• Identify all technology solutions required for the iteration.
• Determine business requirements (think outcomes).
• Determine integrated test plan for the iteration.
2. Data requirements:
• Develop the business entity relationship diagram, illustrating the entities, entity relationships, and granularity.
• Determine data requirements and flows across the technology stack.
3. System integration
• Determine functional workflows (level 1, level 2) for the iteration.
• Determine interfaces for each solution in the stack.
AKA How to Build a Marketing Stack…