Are Decomposition Slices Clones?. - Keith B. Gallagher; Lucas Layman (IWPC, 2003)

Exploring Extreme Programming in Context: An Industrial Case Study. - Lucas Layman; Laurie A. Williams; Lynn Cunningham (Agile Development Conference, 2004)

Empirical investigation of the impact of extreme programming practices on software projects. - Lucas Layman (OOPSLA Companion, 2004)

Undergraduate Student Perceptions of Pair Programming and Agile Software Methodologies: Verifying a Model of Social Interaction. - Kelli M. Slaten; Sarah B. Berenson; Laurie A. Williams; Lucas Layman; Maria A. Droujkova (AGILE, 2005)

On establishing the essential components of a technology-dependent framework: a strawman framework for industrial case study-based research. - Laurie A. Williams; Lucas Layman; Pekka Abrahamsson (ACM SIGSOFT Softw. Eng. Notes, 2005)

Examining the Compatibility of Student Pair Programmers. - Laurie A. Williams; Lucas Layman; Jason A. Osborne; Neha Katira (AGILE, 2006)

Changing Students' Perceptions: An Analysis of the Supplementary Benefits of Collaborative Software Development. - Lucas Layman (CSEE&T, 2006)

Personality types, learning styles, and an agile approach to software engineering education. - Lucas Layman; Travis Cornwell; Laurie A. Williams (SIGCSE, 2006)

Essential communication practices for Extreme Programming in a global software development team. - Lucas Layman; Laurie A. Williams; Daniela E. Damian; Hynek Bures (Inf. Softw. Technol., 2006)

Motivations and measurements in an agile case study. - Lucas Layman; Laurie A. Williams; Lynn Cunningham (J. Syst. Archit., 2006)

Lab Partners: If They're Good Enough for the Natural Sciences, Why Aren't They Good Enough for Us? - Laurie A. Williams; Lucas Layman (CSEE&T, 2007)

Toward Reducing Fault Fix Time: Understanding Developer Behavior for the Design of Automated Fault Detection Tools. - Lucas Layman; Laurie A. Williams; Robert St. Amant (ESEM, 2007)

On the Impact of a Collaborative Pedagogy on African American Millennial Students in Software Engineering. - Laurie A. Williams; Lucas Layman; Kelli M. Slaten; Sarah B. Berenson; Carolyn B. Seaman (ICSE, 2007)

Note to self: make assignments meaningful. - Lucas Layman; Laurie A. Williams; Kelli M. Slaten (SIGCSE, 2007)

Eleven Guidelines for Implementing Pair Programming in the Classroom. - Laurie A. Williams; D. Scott McCrickard; Lucas Layman; Khaled Hussein (AGILE, 2008)

Iterative identification of fault-prone binaries using in-process metrics. - Lucas Layman; Gunnar Kudrjavets; Nachiappan Nagappan (ESEM, 2008)

MimEc: intelligent user notification of faults in the eclipse IDE. - Lucas Layman; Laurie A. Williams; Robert St. Amant (CHASE, 2008)

Mining software effort data: preliminary analysis of visual studio team system data. - Lucas Layman; Nachiappan Nagappan; Sam Guckenheimer; Jeff Beehler; Andrew Begel (MSR, 2008)

Coordination in large-scale software teams. - Andrew Begel; Nachiappan Nagappan; Christopher Poile; Lucas Layman (CHASE, 2009)

Obtaining valid safety data for software safety measurement and process improvement. - Victor R. Basili; Marvin V. Zelkowitz; Lucas Layman; Kathleen Coleman Dangle; Madeline Diep (ESEM, 2010)

What Do We Know about Test-Driven Development? - Forrest Shull; Grigori Melnik; Burak Turhan; Lucas Layman; Madeline Diep; Hakan Erdogmus (IEEE Softw., 2010)

How Effective Is Test-Driven Development? - Burak Turhan; Lucas Layman; Madeline Diep; Hakan Erdogmus; Forrest Shull (Making Software, 2011)

A case study of measuring process risk for early insights into software safety. - Lucas Layman; Victor R. Basili; Marvin V. Zelkowitz; Karen L. Fisher (ICSE, 2011)

Toward Baselining Software Anomalies in NASA Missions. - Lucas Layman; Marvin V. Zelkowitz; Victor R. Basili; Allen P. Nikora (ISSRE Workshops, 2012)

Technical Debt: Showing the Way for Better Transfer of Empirical Results. - Forrest Shull; Davide Falessi; Carolyn B. Seaman; Madeline Diep; Lucas Layman (Perspectives on the Future of Software Engineering, 2013)

Debugging Revisited: Toward Understanding the Debugging Needs of Contemporary Software Developers. - Lucas Layman; Madeline Diep; Meiyappan Nagappan; Janice Singer; Robert DeLine; Gina Venolia (ESEM, 2013)

Using Amazon's Mechanical Turk for User Studies: Eight Things You Need to Know. - Lucas Layman; Gunnar Sigurdsson (ESEM, 2013)

Automated classification of NASA anomalies using natural language processing techniques. - Davide Falessi; Lucas Layman (ISSRE (Supplemental Proceedings), 2013)

Local versus Global Lessons for Defect Prediction and Effort Estimation. - Tim Menzies; Andrew Butcher; David R. Cok; Andrian Marcus; Lucas Layman; Forrest Shull; Burak Turhan; Thomas Zimmermann 001 (IEEE Trans. Software Eng., 2013)

Human factors in webserver log file analysis: a controlled experiment on investigating malicious activity. - Lucas Layman; Sylvain David Diffo; Nico Zazworka (HotSoS, 2014)

InViz: instant visualization of security attacks. - Lucas Layman; Nico Zazworka (HotSoS, 2014)

A Methodology for Exposing Risk in Achieving Emergent System Properties. - Lucas Layman; Victor R. Basili; Marvin V. Zelkowitz (ACM Trans. Softw. Eng. Methodol., 2014)

Applying Software Data Analysis in Industry Contexts. - Madeline Diep; Linda Esker; Davide Falessi; Lucas Layman; Michele A. Shaw; Forrest Shull (The Art and Science of Analyzing Software Data, 2015)

Ask the Engineers: Exploring Repertory Grids and Personal Constructs for Software Data Analysis. - Lucas Layman; Carolyn B. Seaman; Davide Falessi; Madeline Diep (CHASE@ICSE, 2015)

LACE2: Better Privacy-Preserving Data Sharing for Cross Project Defect Prediction. - Fayola Peters; Tim Menzies; Lucas Layman (ICSE (1), 2015)

Topic modeling of NASA space system problem reports: research in practice. - Lucas Layman; Allen P. Nikora; Joshua Meek; Tim Menzies (MSR, 2016)

Recommendations for Intelligent Code Reorganization. - Rahul Krishna; Tim Menzies; Lucas Layman (CoRR, 2016)

Are delayed issues harder to resolve? Revisiting cost-to-fix of defects throughout the lifecycle. - Tim Menzies; William Nichols; Forrest Shull; Lucas Layman (Empir. Softw. Eng., 2017)

Less is more: Minimizing code reorganization using XTREE. - Rahul Krishna; Tim Menzies; Lucas Layman (Inf. Softw. Technol., 2017)

How to trick the Borg: threat models against manual and automated techniques for detecting network attacks. - Carl Sabottke; Daniel Chen; Lucas Layman; Tudor Dumitras (Comput. Secur., 2019)

Toward Predicting Success and Failure in CS2: A Mixed-Method Analysis. - Lucas Layman; Yang Song 019; Curry I. Guinn (ACM Southeast Regional Conference, 2020)

Cry Wolf: Toward an Experimentation Platform and Dataset for Human Factors in Cyber Security Analysis. - William Roden; Lucas Layman (ACM Southeast Regional Conference, 2020)

Suitability of SCS1 as a Pre-CS2 Assessment Instrument: A Comparison with Short Deliberate-practice Questions. - Yang Song 019; Yunkai Xiao; Jonathan Stephens; Emma Ruesch; Sean Roginski; Lucas Layman (ACM Southeast Regional Conference, 2020)

A Controlled Experiment on the Impact of Intrusion Detection False Alarm Rate on Analyst Performance. - Lucas Layman; William Roden (CoRR, 2023)

Generative Artificial Intelligence and the Future of Software Testing. - Lucas Layman; Ron Vetter (Computer, 2024)

Topic Difficulty in a Python Data Structures Course: Student Perceptions and Performance. - Lucas Layman; Toni Pence; Sridhar Narayan (ACM Southeast Regional Conference, 2025)