With varying teams delivering varying pieces of an overall solution it has become increasingly difficult to recognize when a given version of an application must be delivered with another application and different version that fits in to the overall solution. This same scenario surfaces where one application of the overall solution could be delivered prior to the other application but not the other way around.
A hypothetical example could be that there are 4 applications that make up an end to end solution of which serves varying user bases. What I'm struggling with is a way to track inter/intra dependencies across the applications in a simple and digestive manner that doesn't require a wealth of brainpower throughout the day to day tasks across the teams.
I've attempted to use tooling (SpiraTeam) as well as looked at a simplistic matrix within Excel however those have yet to solution the problem. I've also thought about making use of the version numbers themselves to quickly identify impact however that became cumbersome and not maintainable.
I'm looking for perhaps a one-off solution and or previous experience that does not require an entire process/paradigm shift to make this happen. Does anyone have any experience in effectively tracking inter-dependent applications and more importantly the release cycles of the inter-dependent applications within the Enterprise?
To further elaborate, the dependencies are at varying layers within the applications. An example would be the front end of a given application, which talks to the applications back end which talks to yet another application via services. In this example the deliveries must go in parallel yet are operating independently on separate application versions. These undoubtedly spawn due to feature level deliveries however our current paradigm of versioning does not explicitly capture the feature within the version number itself making that connection more difficult. The plan is that it would be manipulated by the entire team which is in due part to the varying interdependence and each owner respectively being closest to that knowledge and interdependence. The end result is then a quick visual to identify that a given application can precede another version or maybe they have to go in parallel, etc... I have explored a simple matrix within Excel however it felt cumbersome since the version definition, versioning maintenance, etc.. happen within another tool. The problem with the tool is that it does not allow inter-connectivity across projects (applications) which would alleviate this issue at the point where I feel it should be solved.