Team Performance Science Guide · Part VII · evidence chain
Performance Science Library
Every evidence pill in Performix traces back through this library. Source papers and books are ingested by the Research-to-Model Engine; constructs, validated measures, and survey items are derived from them and weighted by evidence strength.
196 sources
818 findings
915 constructs
525 survey items
last update 2026-07-08
BOOK
Forsgren, N., Humble, J., & Kim, G. (2018). Accelerate: The Science of Lean Software and DevOps. IT Revolution Press.
Ingested 2026-06-13 · 56 findings extracted · 76 constructs derived
James Bessen's 2017 study underscores the role of strategic technology use in enhancing revenue and productivity, eclipsing traditional advancement methods.
preliminary
Constructs derived (4)
ACCELERATECAPABILITY
FOCUS ON CAPABILITIES, NOT MATURITYCAPABILITY
EVIDENCE-BASED TRANSFORMATIONS FOCUS ON KEY CAPABILITIESCAPABILITY
THE VALUE OF ADOPTING DEVOPSCAPABILITY
Research findings reveal high performers achieve 46 times more frequent deployments, 440 times faster lead times, and 170 times faster recovery from downtimes.
preliminary
Recent Forrester and Gartner studies indicate a substantial gap in the practice of essential technology transformation capabilities in organizations, particularly among executive assessments of DevOps maturity versus practitioner insights.
preliminary
The book will detail 24 key capabilities that have been empirically validated as critical for driving improvements in software delivery performance, applicable to diverse organizational contexts.
preliminary
Reinertsen's emphasis on the 'fuzzy front end' of product lead time (2009).
preliminary
Statistical data analysis techniques such as cluster analysis to categorize software delivery performance across multiple cohorts.
preliminary
Quantitative measures of organizational performance previously validated by Widener (2007) and Cavalluzzo & Ittner (2004).
preliminary
Longitudinal data showing characteristics of high, medium, and low performers in software delivery from 2016 and 2017, including metrics like deployment frequency, lead time, and change failure rates.
preliminary
Discussions around the implications of high utilization leading to disproportionately long lead times, supported by mathematical queue theory principles.
preliminary
Westrum’s model classifies organizational cultures based on their characteristics, such as cooperation levels and approaches to failure, suggesting that generative cultures improve information flow and decision-making.
preliminary
The use of Likert scales to measure perceptions of culture provides a statistically robust method for gathering and analyzing data.
preliminary
Empirical research links a generative organizational culture with enhanced software delivery performance and employee satisfaction.
preliminary
Google’s extensive research into high-performing teams reveals that the quality of collaboration and interaction outweighs individual traits in determining team effectiveness—a finding consistent with Westrum’s insights.
preliminary
The chapter references research conducted over multiple years (2014-2016) that quantitatively analyzes the key capabilities contributing to successful continuous delivery practices.
preliminary
Specific inquiries measured capabilities such as version control consistency and implementation of automated testing, revealing their statistically significant correlations with enhanced software delivery performance.
preliminary
The authors cite tools like Likert-type questions for gathering data and facilitating thorough statistical analysis of participant responses across numerous organizations.
preliminary
Notably, results highlight that teams utilizing continuous delivery report reduced instances of unplanned work, indicative of greater efficiency and quality in software development processes.
preliminary
The chapter cites extensive research findings, including survey results from 2017 that correlate architecture design with performance outcomes.
preliminary
It references Melvin Conway's insights from 1968 on how organizational structures dictate system designs, offering a historical underpinning to the narrative.
preliminary
The authors note specific case analysis, revealing that high-performing teams frequently operate in loosely coupled environments that limit dependencies on external teams.
preliminary
Performance metrics highlighting how deploys per developer vary significantly across performance tiers substantiate the claims of improving productivity with thoughtful architectural decisions.
preliminary
James Wickett’s 2014 staffing ratio of infosec personnel relative to development staff highlights systemic weaknesses.
preliminary
The Federal Information Security Management Act of 2002 (FISMA) and the Risk Management Framework (RMF) exemplify traditional challenges faced in governmental software delivery.
preliminary
The efficacy of cloud.gov as a platform enabling rapid deployment and compliance showcases a real-world application of integrated security measures.
preliminary
Research findings indicate that high-performing organizations expend 50% less time remediating security issues than those with less robust practices.
preliminary
The chapter references research indicating that practices like limiting WIP and using visual displays positively correlate with increased software delivery performance.
preliminary
Empirical data illustrates that teams employing peer-based change management outperformed those reliant upon external approval bodies—highlighting a significant correlation with lead times and deployment frequency.
preliminary
The discussion of Lean principles draws on how these methodologies have historically benefited manufacturing environments such as Toyota, which effectively transitioned into software practices.
preliminary
Figures included in the chapter provide visual evidence of the relationship between Lean practices and their impacts on burnout and team generativity, supported by Westrum’s model of organizational culture.
preliminary
Product Development
preliminary
Making Work Sustainable
preliminary
Employee Satisfaction, Identity, and Engagement
preliminary
The chapter draws on extensive research, including a pivotal 2004 study by Rafferty and Griffin, to illustrate the correlation between transformational leadership qualities and software delivery performance.
preliminary
Notably, the findings indicate that high-performing teams report superior leadership characteristics when contrasted with low-performing teams.
preliminary
Organizations with robust transformational leaders experience improved employee Net Promoter Scores, indicative of higher satisfaction and engagement levels within the workforce.
preliminary
The research draws upon primary data collected through a robust survey methodology, encompassing a four-year timeline of technological evolution and impact.
preliminary
Statistical methods used in the studies include multiple linear regression and partial least squares regression, designed to identify significant relationships within organizational performance data.
preliminary
Specific examples highlight the importance of proper sampling methods in reaching conclusions representative of larger populations, emphasizing findings like those reported by Forrester and IDC.
preliminary
The chapter references a 2008 study by East et al. as a benchmark to contrast the effectiveness of single-question surveys with more comprehensive measures.
preliminary
It discusses Dr. Ron Westrum's 2004 typology for understanding organizational culture, providing a theoretical backbone to the chapter's argument.
preliminary
Statistical concepts like reliability testing and validity are elaborated with an emphasis on their necessity for quality assurance in survey measures.
preliminary
Concrete examples, such as President Trump’s 2017 survey, are used to illustrate the consequences of poorly structured surveys on data interpretation.
preliminary
The chapter refers to extensive research conducted for the State of DevOps Reports, which involved over 23,000 respondents, underscoring the robustness of the data collected.
preliminary
The authors illustrate the potential pitfalls of system data with practical examples, like performance misinterpretations at IBM, validating the need for direct user insights.
preliminary
Statistical methods and psychometric techniques are referenced as foundational practices that increase the reliability and validity of survey data.
preliminary
It highlights research from authoritative sources, including Google’s studies on team dynamics and performance outcomes that link psychological safety with productivity.
preliminary
The chapter discusses the structured research methodology initiated in 2014, which focused on DevOps practices and trends.
preliminary
It outlines the challenges of utilizing probability sampling due to the absence of a defined population list for DevOps professionals.
preliminary
The authors reference their established mailing lists and databases, including those of industry experts like Gene Kim and Jez Humble, as sources for participant recruitment.
preliminary
The methodology also highlights the importance of reaching underrepresented groups, ensuring diverse voices within the software development community are heard.
preliminary
The authors underscore an iterative approach to research, involving community feedback and subject matter expert engagement to refine findings continuously.
preliminary
Existing literature is referenced as a means to draw insights and confirm findings across other relevant domains, enhancing the depth and applicability of their research.
preliminary
The chapter cites research linking effective leadership with increased organizational performance, emphasizing the measurable impacts on profitability, productivity, and customer satisfaction.
preliminary
Real-world examples from ING Netherlands illustrate successful Lean management practices, transforming an IT department into a vital strategic contributor.
preliminary
The mention of specific tools (Obeya rooms, daily stand-ups) showcases effective practices that promote engagement and high performance.
preliminary
Feedback loops through continuous improvement and team empowerment significantly contribute to business outcomes, as backed by qualitative insights from ING's transformative journey.
preliminary