Cross-Project Timing Correlation(3.4.10)

When two separate projects both experience issue spikes at the same time, consistently, it may not be a coincidence. Shared deployment pipelines, shared infrastructure components, or shared dependencies can cause correlated failures across multiple projects simultaneously.

This visual quantifies the timing correlation between project pairs — so you can see which pairs of projects spike together and decide where a shared driver is worth investigating.

What you can conclude

• A high correlation (above 0.7) between two projects means their weekly incident counts moved together. Shared infrastructure, a shared release process, and portfolio-wide swings in activity that lift every project at once can all produce this; which one applies is a question the coefficient alone cannot answer.
• Investigating highly correlated project pairs together (rather than separately) may reveal a shared root cause that individual project-level analysis would miss.
• A low correlation across all project pairs indicates that incidents are occurring independently — project-level root causes are more likely than shared infrastructure failures.

How this chart works

Correlation matrix showing the Pearson correlation coefficient of weekly issue creation counts between each pair of projects. Higher values indicate more synchronized incident timing.