dora-team · nathenharvey · Jul 30, 2024 · Jul 30, 2024 · Jul 30, 2024 · Jul 30, 2024
diff --git a/firebase.json b/firebase.json
@@ -101,7 +101,7 @@
                 },
                 {
                     "source": "/dora-report-2015",
-                    "destination": "/research/2017-and-earlier/2015-state-of-devops-report.pdf",
+                    "destination": "/research/2015",
                     "type": 302
                 },
                 {
@@ -211,7 +211,12 @@
                 },
                 {
                     "source": "/publications/pdf/state-of-devops-2015.pdf",
-                    "destination": "/research/2017-and-earlier/2015-state-of-devops-report.pdf",
+                    "destination": "/research/2015/2015-state-of-devops-report.pdf",
+                    "type": 301
+                },
+                {
+                    "source": "/research/2017-and-earlier/2015-state-of-devops-report.pdf",
+                    "destination": "/research/2015/2015-state-of-devops-report.pdf",
                     "type": 301
                 },
                 {

diff --git a/hugo/content/capabilities/continuous-integration/index.md b/hugo/content/capabilities/continuous-integration/index.md
@@ -33,7 +33,7 @@ into the
 [*trunk*](/capabilities/trunk-based-development),
 *main*, or *mainline*) on a regular basis. DevOps Research and Assessment
 (DORA)
-[research](/research/2017-and-earlier/2015-state-of-devops-report.pdf#page=20)
+[research](/research/2015/2015-state-of-devops-report.pdf#page=20)
 (PDF) shows that teams perform better when developers merge their work into
 trunk at least daily. A set of automated tests is run both before and after the
 merge in order to validate that the changes don't introduce regression bugs. If
@@ -43,7 +43,7 @@ problem immediately.
 CI ensures that the software is always in a working state, and that developer
 branches don't diverge significantly from trunk. The benefits of CI are
 significant:
-[research](/research/2017-and-earlier/2015-state-of-devops-report.pdf#page=16)
+[research](/research/2015/2015-state-of-devops-report.pdf#page=16)
 (PDF) shows that it leads to higher deployment frequency, more stable systems,
 and higher quality software.
 
@@ -232,7 +232,7 @@ change.</td>
     [SRE Book](https://landing.google.com/sre/books/),
     in particular
     [Chapter 8 - Release Engineering](https://landing.google.com/sre/sre-book/chapters/release-engineering/).
--   Read James Shore's article 
+-   Read James Shore's article
     [CI on a dollar a day](https://www.jamesshore.com/Blog/Continuous-Integration-on-a-Dollar-a-Day.html).
 -   Watch Google's John Penix describe
     [how Google practices CI at scale](https://www.infoq.com/presentations/Continuous-Testing-Build-Cloud/).

diff --git a/hugo/content/capabilities/visual-management/index.md b/hugo/content/capabilities/visual-management/index.md
@@ -41,7 +41,7 @@ When combined with the use of
 [WIP limits](/capabilities/wip-limits)
 and using feedback from production to make business decisions, visual management
 displays can contribute to
-[higher levels of delivery performance](/research/2017-and-earlier/2015-state-of-devops-report.pdf#page=15)
+[higher levels of delivery performance](/research/2015/2015-state-of-devops-report.pdf#page=15)
 (PDF).
 
 ## Common pitfalls with visual management

diff --git a/hugo/content/publications/_index.md b/hugo/content/publications/_index.md
@@ -51,10 +51,10 @@ bannerSubtitle: "Findings from DORA's research program are made available throug
   (in partnership with Puppet)
   [Read PDF](/research/2017-and-earlier/2016-state-of-devops-report.pdf)
 
-- [![2015 State of DevOps Report](/research/2017-and-earlier/2015-state-of-devops-report.png)](/research/2017-and-earlier/2015-state-of-devops-report.pdf)
-  **[2015 State of DevOps Report](/research/2017-and-earlier/2015-state-of-devops-report.pdf)**
+- [![2015 State of DevOps Report](/research/2017-and-earlier/2015-state-of-devops-report.png)](/research/2015)
+  **[2015 State of DevOps Report](/research/2015)**
   (in partnership with Puppet)
-  [Read PDF](/research/2017-and-earlier/2015-state-of-devops-report.pdf)
+  [Download the report](/research/2015)
 
 - [![2014 State of DevOps Report](/research/2017-and-earlier/2014-state-of-devops-report.png)](/research/2017-and-earlier/2014-state-of-devops-report.pdf)
   **[2014 State of DevOps Report](/research/2017-and-earlier/2014-state-of-devops-report.pdf)**

diff --git a/...d-earlier/2015-state-of-devops-report.pdf → ...arch/2015/2015-state-of-devops-report.pdf b/...d-earlier/2015-state-of-devops-report.pdf → ...arch/2015/2015-state-of-devops-report.pdf
diff --git a/...d-earlier/2015-state-of-devops-report.png → ...arch/2015/2015-state-of-devops-report.png b/...d-earlier/2015-state-of-devops-report.png → ...arch/2015/2015-state-of-devops-report.png
diff --git a/hugo/content/research/2015/_index.md b/hugo/content/research/2015/_index.md
@@ -0,0 +1,26 @@
+---
+title: "DORA Research: 2015"
+date: 2024-07-30
+draft: false
+research_year: "2015"
+type: research_archives
+layout: single
+---
+
+[![2015 State of DevOps Report](/research/2015/2015-state-of-devops-report.png)](2015-state-of-devops-report.pdf)
+
+The 2015 State of DevOps Report presents compelling evidence for the transformative power of DevOps in the IT industry. The report emphasizes that high-performing IT organizations consistently outperform their counterparts in terms of deployment frequency, lead time, failure rates, and recovery speed. These superior results are attributed to the adoption of practices, which streamline software delivery and enhance operational efficiency.
+
+A key highlight of the report is the symbiotic relationship between lean management and continuous delivery. By integrating these principles, organizations can cultivate a culture of continuous improvement, reduce burnout, and achieve remarkable IT performance. The report also underscores the significance of application architecture in developer productivity, advocating for designs that prioritize testability and deployability.
+
+Key findings of the report include:
+
+* High-performing IT organizations deploy 30 times more frequently with 200 times shorter lead times, experience 60 times fewer failures, and recover 168 times faster than their lower-performing peers.
+* Lean management and continuous delivery practices are instrumental in creating an environment that enables faster and sustainable value delivery.
+* High performance is achievable regardless of whether applications are greenfield, brownfield, or legacy, as long as they are architected with testability and deployability in mind.
+* IT managers play a crucial role in facilitating transformations by connecting strategic business objectives with on-the-ground execution.
+* Diversity is a key factor in high-performing teams, with research indicating that teams with more women members exhibit higher collective intelligence and achieve superior business outcomes.
+* Deployment pain is a significant indicator of IT performance, with organizations experiencing painful deployments often exhibiting poorer IT performance, organizational performance, and culture.
+* Burnout can be effectively prevented through the implementation of practices that foster a supportive work environment, emphasize learning from failures, and promote a strong sense of purpose.
+
+[Download the 2015 State of DevOps Report](2015-state-of-devops-report.pdf)
diff --git a/hugo/content/research/2017-and-earlier/_index.md b/hugo/content/research/2017-and-earlier/_index.md
@@ -12,5 +12,5 @@ Prior to 2018, research was conducted in partnership with Puppet, as an extensio
 #### State of DevOps Reports published in partnership with Puppet:
 - [2017 State of DevOps Report](2017-state-of-devops-report.pdf)
 - [2016 State of DevOps Report](2016-state-of-devops-report.pdf)
-- [2015 State of DevOps Report](2015-state-of-devops-report.pdf)
+- [2015 State of DevOps Report](/research/2015)
 - [2014 State of DevOps Report](2014-state-of-devops-report.pdf)
diff --git a/hugo/static/research/content/burnout.html b/hugo/static/research/content/burnout.html
@@ -13,4 +13,4 @@
 
 <p>Our research found evidence that <a onclick="linkTo('tech-practices');">technical</a>, <a onclick="linkTo('lean-management');">lean management</a> and <a onclick="linkTo('lean-product');">product management</a> practices, along with a <a onclick="linkTo('change');">clear change process</a>, contribute to reductions in burnout.</p>
 
-<p>For an in-depth look at burnout, see the <a href="/research/2017-and-earlier/2015-state-of-devops-report.pdf" target="_blank"></a>2015 State of DevOps Report</a>.</p>
+<p>For an in-depth look at burnout, see the <a href="/research/2015/2015-state-of-devops-report.pdf" target="_blank"></a>2015 State of DevOps Report</a>.</p>
diff --git a/test/playwright/tests/research/2015/2015.spec.ts b/test/playwright/tests/research/2015/2015.spec.ts
@@ -0,0 +1,20 @@
+import { test, expect } from '@playwright/test';
+import { sidebarLinks } from '../sidebarLinks';
+
+test.beforeEach(async ({ page }) => {
+  await page.goto('/research/2015/');
+});
+
+test('2015 Research page has the correct title.', async ({ page }) => {
+  await expect(page).toHaveTitle('DORA | DORA Research: 2015');
+});
+
+test('2015 Research page has the correct header.', async ({ page }) => {
+  await expect(page.locator('h1')).toContainText('DORA Research: 2015');
+});
+
+test('2015 Research page has the correct sidebar.', async ({ page }) => {
+  for (const sidebarLink of sidebarLinks) {
+    await expect(page.getByRole('link', { name: sidebarLink, exact: true })).toBeVisible();
+  }
+});
diff --git a/test/playwright/tests/research/2017-and-earlier/2017-and-earlier-overview.spec.ts b/test/playwright/tests/research/2017-and-earlier/2017-and-earlier-overview.spec.ts
@@ -4,7 +4,7 @@ import { sidebarLinks } from '../sidebarLinks';
 export const reportsMap = {
   '2017 State of DevOps Report': '2017-state-of-devops-report.pdf',
   '2016 State of DevOps Report': '2016-state-of-devops-report.pdf',
-  '2015 State of DevOps Report': '2015-state-of-devops-report.pdf',
+  '2015 State of DevOps Report': '/research/2015',
   '2014 State of DevOps Report': '2014-state-of-devops-report.pdf'
 };
 

diff --git a/test/redirects/redirects.csv b/test/redirects/redirects.csv
@@ -35,15 +35,16 @@
 /dora-report-2018,/research/2018/dora-report,302
 /dora-report-2017,/research/2017-and-earlier/2017-state-of-devops-report.pdf,302
 /dora-report-2016,/research/2017-and-earlier/2016-state-of-devops-report.pdf,302
-/dora-report-2015,/research/2017-and-earlier/2015-state-of-devops-report.pdf,302
+/dora-report-2015,/research/2015,302
 /dora-report-2014,/research/2017-and-earlier/2014-state-of-devops-report.pdf,302
 /devops-capabilities/cultural/how-to-empower-software-delivery-teams/,/guides/how-to-empower-software-delivery-teams/,302
 /devops-capabilities/cultural/devops-culture-transform/,/guides/devops-culture-transform/,301
 /sponsor,/sponsors/,301
 /publications/pdf/state-of-devops-2014.pdf,/research/2017-and-earlier/2014-state-of-devops-report.pdf,301
-/publications/pdf/state-of-devops-2015.pdf,/research/2017-and-earlier/2015-state-of-devops-report.pdf,301
+/publications/pdf/state-of-devops-2015.pdf,/research/2015/2015-state-of-devops-report.pdf,301
 /publications/pdf/state-of-devops-2016.pdf,/research/2017-and-earlier/2016-state-of-devops-report.pdf,301
 /publications/pdf/state-of-devops-2017.pdf,/research/2017-and-earlier/2017-state-of-devops-report.pdf,301
 /publications/pdf/state-of-devops-2018.pdf,/research/2018/dora-report/2018-dora-accelerate-state-of-devops-report.pdf,301
 /publications/pdf/state-of-devops-2019.pdf,/research/2019/dora-report/2019-dora-accelerate-state-of-devops-report.pdf,301
 /publications/pdf/state-of-devops-2021.pdf,/research/2021/dora-report/2021-dora-accelerate-state-of-devops-report.pdf,301
+/research/2017-and-earlier/2015-state-of-devops-report.pdf,/research/2015/2015-state-of-devops-report.pdf,301