Dependency map between requirements

There exist functional dependencies between requirements, either from the same projects or from other project initiatives, and this will lead to reprioritizing requirements. We need to identify cross-functionality dependencies and prioritize requirements to align them by understanding dependencies between processes, systems, and teams.

You can identify requirements dependencies by reviewing or creating end-to-end process flows, function and system diagrams, and conceptual flows.

In this example, let us assume we have requirements from A to J, as listed in Figure 3.4, with priority values from 1 to 10. We stack-ranked them in our first iteration and in the second iteration, we used the dependency mapping technique and discovered that two specific requirements are linked together and need to be implemented at the same time; if not, neither will work:

Figure 3.4 – Requirement prioritization options

Let us analyze...