Please note: This is a beta version of the new dblp website.
You can find the classic dblp view of this page here.
You can find the classic dblp view of this page here.
Laurie A. Williams
Laurie Williams
2010 – today
- 2013
[j37]Yonghee Shin, Laurie Williams: Can traditional fault prediction models be used for vulnerability prediction? Empirical Software Engineering 18(1): 25-59 (2013)
[j36]Andrew Austin, Casper Holmgreen, Laurie Williams: A comparison of the efficiency and effectiveness of vulnerability discovery techniques. Information & Software Technology 55(7): 1279-1288 (2013)- 2012
[j35]
[j34]Jason Tyler King, Ben H. Smith, Laurie Williams: Audit Mechanisms in Electronic Health Record Systems: Protected Health Information May Remain Vulnerable to Undetected Misuse. IJCMAM 3(2): 23-42 (2012)
[j33]Andrew Meneely, Ben H. Smith, Laurie Williams: Validating software metrics: A spectrum of philosophies. ACM Trans. Softw. Eng. Methodol. 21(4): 24 (2012)
[c99]Jason Tyler King, Ben H. Smith, Laurie A. Williams: Modifying without a trace: general audit guidelines are inadequate for open-source electronic health record audit mechanisms. IHI 2012: 305-314
[c98]Kumi Jinzenji, Takashi Hoshino, Laurie Williams, Kenji Takahashi: Metric-Based Quality Evaluations for Iterative Software Development Approaches Like Agile. ISSRE Workshops 2012: 54-63
[c97]John Slankas, Laurie Williams: Classifying Natural Language Sentences for Policy. POLICY 2012: 33-36
[c96]Maria Riaz, Laurie Williams: Security requirements patterns: understanding the science behind the art of pattern writing. RePa 2012: 29-34
[c95]- 2011
[j32]Sarah Smith Heckman, Laurie A. Williams: A systematic literature review of actionable alert identification techniques for automated static code analysis. Information & Software Technology 53(4): 363-387 (2011)
[j31]Yonghee Shin, Andrew Meneely, Laurie Williams, Jason A. Osborne: Evaluating Complexity, Code Churn, and Developer Activity Metrics as Indicators of Software Vulnerabilities. IEEE Trans. Software Eng. 37(6): 772-787 (2011)
[c94]Andrew Austin, Laurie Williams: One Technique is Not Enough: A Comparison of Vulnerability Discovery Techniques. ESEM 2011: 97-106
[c93]Laurie Williams, Gabe Brown, Adam Meltzer, Nachiappan Nagappan: Scrum + Engineering Practices: Experiences of Three Microsoft Teams. ESEM 2011: 463-471
[c92]Andrew Meneely, Laurie Williams: Socio-technical developer networks: should we trust our measurements? ICSE 2011: 281-290
[c91]Ben H. Smith, Laurie Williams: Using SQL Hotspots in a Prioritization Heuristic for Detecting All Types of Web Application Vulnerabilities. ICST 2011: 220-229
[c90]Thomas Zimmermann, Nachiappan Nagappan, Kim Herzig, Rahul Premraj, Laurie Williams: An Empirical Study on the Relation between Dependency Neighborhoods and Failures. ICST 2011: 347-356
[c89]
[c88]Jessica Young Schmidt, Annie I. Antón, Laurie Williams, Paul N. Otto: The role of data use agreements in specifying legally compliant software requirements. RELAW 2011: 1-4
[c87]Andrew Meneely, Pete Rotella, Laurie Williams: Does adding manpower also affect quality?: an empirical, longitudinal analysis. SIGSOFT FSE 2011: 81-90- 2010
[j30]Laurie Williams: Agile Software Development Methodologies and Practices. Advances in Computers 80: 1-44 (2010)
[j29]Laurie Williams: Guest editorial: Special issue on software reliability engineering. Empirical Software Engineering 15(4): 321-322 (2010)
[j28]Laurie Williams, Andrew Meneely, Grant Shipley: Protection Poker: The New Software Security "Game";. IEEE Security & Privacy 8(3): 14-20 (2010)
[c86]Laurie Williams, Kenny Rubin, Mike Cohn: Driving Process Improvement via Comparative Agility Assessment. AGILE 2010: 3-10
[c85]Andrew Meneely, Laurie A. Williams: Strengthening the empirical analysis of the relationship between Linus' Law and software security. ESEM 2010
[c84]Ben H. Smith, Laurie Williams, Andrew Austin: Idea: Using System Level Testing for Revealing SQL Injection-Related Error Message Information Leaks. ESSoS 2010: 192-200
[c83]Raza Abbas Syed, Brian Robinson, Laurie A. Williams: Does Hardware Configuration and Processor Load Impact Software Fault Observability? ICST 2010: 285-294
[c82]Thomas Zimmermann, Nachiappan Nagappan, Laurie A. Williams: Searching for a Needle in a Haystack: Predicting Security Vulnerabilities for Windows Vista. ICST 2010: 421-428
[r1]
2000 – 2009
- 2009
[j27]Ben H. Smith, Laurie Williams: On guiding the augmentation of an automated test suite via mutation analysis. Empirical Software Engineering 14(3): 341-369 (2009)
[j26]Stephen Thomas, Laurie Williams, Tao Xie: On automated prepared statement generation to remove SQL injection vulnerabilities. Information & Software Technology 51(3): 589-598 (2009)
[j25]Ben H. Smith, Laurie Williams: Should software testers use mutation analysis to augment a test set? Journal of Systems and Software 82(11): 1819-1832 (2009)
[j24]
[c81]Andrew Meneely, Laurie A. Williams: Secure open source collaboration: an empirical study of linus' law. ACM Conference on Computer and Communications Security 2009: 453-462
[c80]Laurie Williams, Michael Gegick, Andrew Meneely: Protection Poker: Structuring Software Security Risk Assessment and Knowledge Transfer. ESSoS 2009: 122-134
[c79]Michael Gegick, Pete Rotella, Laurie Williams: Toward Non-security Failures as a Predictor of Security Faults and Failures. ESSoS 2009: 135-149
[c78]Sarah Smith Heckman, Laurie A. Williams: A Model Building Process for Identifying Actionable Static Analysis Alerts. ICST 2009: 161-170
[c77]Michael Gegick, Pete Rotella, Laurie A. Williams: Predicting Attack-prone Components. ICST 2009: 181-190
[c76]Laurie Williams, Gunnar Kudrjavets, Nachiappan Nagappan: On the Effectiveness of Unit Test Automation at Microsoft. ISSRE 2009: 81-89
[c75]Andrew Meneely, Laurie Williams: On preparing students for distributed software development with a synchronous, collaborative development platform. SIGCSE 2009: 529-533- 2008
[j23]Nachiappan Nagappan, E. Michael Maximilien, Thirumalesh Bhat, Laurie Williams: Realizing quality improvement through test driven development: results and experiences of four industrial teams. Empirical Software Engineering 13(3): 289-302 (2008)
[c74]Laurie A. Williams, D. Scott McCrickard, Lucas Layman, Khaled Hussein: Eleven Guidelines for Implementing Pair Programming in the Classroom. AGILE 2008: 445-452
[c73]Michael Gegick, Laurie Williams, Jason A. Osborne, Mladen A. Vouk: Prioritizing software security fortification throughcode-level metrics. QoP 2008: 31-38
[c72]
[c71]Sarah Smith Heckman, Laurie Williams: On establishing a benchmark for evaluating static analysis alert prioritization and classification techniques. ESEM 2008: 41-50
[c70]Yonghee Shin, Laurie Williams: An empirical model to predict security vulnerabilities using code complexity metrics. ESEM 2008: 315-317
[c69]Ben H. Smith, Yonghee Shin, Laurie Williams: Proposing SQL statement coverage metrics. SESS 2008: 49-56
[c68]Lucas Layman, Laurie A. Williams, Robert St. Amant: MimEc: intelligent user notification of faults in the eclipse IDE. CHASE 2008: 73-76
[c67]Mark Sherriff, Laurie Williams: Empirical Software Change Impact Analysis using Singular Value Decomposition. ICST 2008: 268-277
[c66]Michael Gegick, Laurie Williams: Ranking Attack-Prone Components with a Predictive Model. ISSRE 2008: 315-316
[c65]Andrew Meneely, Laurie Williams, Edward F. Gehringer: ROSE: a repository of education-friendly open-source projects. ITiCSE 2008: 7-11
[c64]Steven Fraser, Djenana Campara, Robert Gleichauf, Harriet Pearson, Peter Swire, Laurie Williams: Privacy and security: what are you doing to keep the community safe? OOPSLA Companion 2008: 801-804
[c63]Chih-Wei Ho, Laurie Williams, Brian Robinson: Examining the Relationships between Performance Requirements and "Not a Problem" Defect Reports. RE 2008: 135-144
[c62]Andrew Meneely, Laurie Williams, Will Snipes, Jason A. Osborne: Predicting failures with developer networks and social network analysis. SIGSOFT FSE 2008: 13-23
[p1]Laurie A. Williams, Mladen A. Vouk: Agile Software Development. Wiley Encyclopedia of Computer Science and Engineering 2008
[e2]Hossein Saiedian, Laurie A. Williams (Eds.): Proceedings 21st Conference on Software Engineering Education and Training, CSEET 2008, 14-17 April 2008, Charleston, South Carolina, USA. IEEE Computer Society 2008, ISBN 978-0-7695-3144-1- 2007
[j22]Michael Gegick, Laurie Williams: On the design of more secure software-intensive systems by use of attack patterns. Information & Software Technology 49(4): 381-397 (2007)
[j21]Laurie Williams: Lessons learned from seven years of pair programming at North Carolina State University. SIGCSE Bulletin 39(4): 79-83 (2007)
[j20]Michael J. Johnson, Chih-Wei Ho, E. Michael Maximilien, Laurie Williams: Incorporating Performance Testing in Test-Driven Development. IEEE Software 24(3): 67-73 (2007)
[c61]Julio Cesar Sanchez, Laurie A. Williams, E. Michael Maximilien: On the Sustained Use of a Test-Driven Development Practice at IBM. AGILE 2007: 5-14
[c60]Mark Sherriff, Sarah Smith Heckman, Mike Lake, Laurie A. Williams: Identifying fault-prone files using static analysis alerts through singular value decomposition. CASCON 2007: 276-279
[c59]Laurie Williams, Lucas Layman: Lab Partners: If They're Good Enough for the Natural Sciences, Why Aren't They Good Enough for Us? CSEE&T 2007: 72-82
[c58]Lucas Layman, Laurie Williams, Robert St. Amant: Toward Reducing Fault Fix Time: Understanding Developer Behavior for the Design of Automated Fault Detection Tools. ESEM 2007: 176-185
[c57]Laurie Williams, Lucas Layman, Kelli M. Slaten, Sarah B. Berenson, Carolyn B. Seaman: On the Impact of a Collaborative Pedagogy on African American Millennial Students in Software Engineering. ICSE 2007: 677-687
[c56]Mark Sherriff, Mike Lake, Laurie Williams: Prioritization of Regression Tests using Singular Value Decomposition with Empirical Change Records. ISSRE 2007: 81-90
[c55]Nachiappan Nagappan, Laurie Williams, Mladen A. Vouk, Jason A. Osborne: Using In-Process Testing Metrics to Estimate Post-Release Field Quality. ISSRE 2007: 209-214
[c54]Jiang Zheng, Laurie Williams, Brian Robinson: Pallino: automation to support regression test selection for cots-based applications. ASE 2007: 224-233
[c53]Chih-Wei Ho, Laurie Williams, Annie I. Antón: Improving Performance Requirements Specifications from Field Failure Reports. RE 2007: 79-88
[c52]Lucas Layman, Laurie A. Williams, Kelli M. Slaten: Note to self: make assignments meaningful. SIGCSE 2007: 459-463
[c51]Mark Sherriff, Sarah Smith Heckman, J. Michael Lake, Laurie A. Williams: Using groupings of static analysis alerts to identify files likely to contain field failures. ESEC/SIGSOFT FSE 2007: 565-568
[c50]Mark Sherriff, Sarah Smith Heckman, J. Michael Lake, Laurie A. Williams: Using groupings of static analysis alerts to identify files likely to contain field failures. ESEC/SIGSOFT FSE (Companion) 2007: 565-568
[c49]Chih-Wei Ho, Laurie Williams: Developing software performance with the performance refinement and evolution model. WOSP 2007: 133-136- 2006
[j19]Laurie Williams: Debunking the Nerd Stereotype with Pair Programming. IEEE Computer 39(5): 83-85 (2006)
[j18]Lucas Layman, Laurie Williams, Daniela Damian, Hynek Bures: Essential communication practices for Extreme Programming in a global software development team. Information & Software Technology 48(9): 781-794 (2006)
[j17]Lucas Layman, Laurie Williams, Lynn Cunningham: Motivations and measurements in an agile case study. Journal of Systems Architecture 52(11): 654-667 (2006)
[j16]Mario Garzia, John P. Hudepohl, Will Snipes, Michael R. Lyu, John D. Musa, Carol Smidts, Laurie Williams: How should software reliability engineering (SRE) be taught? ACM SIGSOFT Software Engineering Notes 31(4): 1-5 (2006)
[j15]Jiang Zheng, Laurie A. Williams, Nachiappan Nagappan, Will Snipes, John P. Hudepohl, Mladen A. Vouk: On the Value of Static Analysis for Fault Detection in Software. IEEE Trans. Software Eng. 32(4): 240-253 (2006)
[c48]Chih-Wei Ho, Michael J. Johnson, Laurie Williams, E. Michael Maximilien: On Agile Performance Requirements Specification and Testing. AGILE 2006: 47-52
[c47]Laurie Williams, Lucas Layman, Jason A. Osborne, Neha Katira: Examining the Compatibility of Student Pair Programmers. AGILE 2006: 411-420
[c46]Laurie Williams: Structuring Families of Industrial Case Studies. Empirical Software Engineering Issues 2006: 134
[c45]Lutz Prechelt, Laurie Williams: Industry-Research Collaboration Working Group Results . Empirical Software Engineering Issues 2006: 153-157
[c44]Laurie Williams, Hakan Erdogmus, Richard W. Selby: Roadmapping Working Group 4 Results. Empirical Software Engineering Issues 2006: 181-183
[c43]Jiang Zheng, Brian Robinson, Laurie Williams, Karen Smiley: A Lightweight Process for Change Identification and Regression Test Selection in Using COTS Components. ICCBSS 2006: 137-143
[c42]Jiang Zheng, Brian Robinson, Laurie Williams, Karen Smiley: Applying regression test selection for COTS-based applications. ICSE 2006: 512-522
[c41]Mark Sherriff, Laurie Williams: DevCOP: A Software Certificate Management System for Eclipse. ISSRE 2006: 375-384
[c40]Lucas Layman, Travis Cornwell, Laurie A. Williams: Personality types, learning styles, and an agile approach to software engineering education. SIGCSE 2006: 428-432- 2005
[j14]Michael Gegick, Laurie Williams: Matching attack patterns to security vulnerabilities in software-intensive system designs. ACM SIGSOFT Software Engineering Notes 30(4): 1-7 (2005)
[j13]Nachiappan Nagappan, Laurie Williams, Mladen A. Vouk, Jason A. Osborne: Early estimation of software quality using in-process testing metrics: a controlled case study. ACM SIGSOFT Software Engineering Notes 30(4): 1-7 (2005)
[j12]Mark Sherriff, Nachiappan Nagappan, Laurie Williams, Mladen A. Vouk: Early estimation of defect density using an in-process Haskell metrics model. ACM SIGSOFT Software Engineering Notes 30(4): 1-6 (2005)
[j11]Hema Srikanth, Laurie Williams: On the economics of requirements-based test case prioritization. ACM SIGSOFT Software Engineering Notes 30(4): 1-3 (2005)
[j10]Laurie Williams, Lucas Layman, Pekka Abrahamsson: On establishing the essential components of a technology-dependent framework: a strawman framework for industrial case study-based research. ACM SIGSOFT Software Engineering Notes 30(4): 1-5 (2005)
[j9]Jiang Zheng, Brian Robinson, Laurie Williams, Karen Smiley: A process for identifying changes when source code is not available. ACM SIGSOFT Software Engineering Notes 30(4): 1-4 (2005)
[c39]Kelli M. Slaten, Sarah B. Berenson, Laurie Williams, Lucas Layman, Maria A. Droujkova: Undergraduate Student Perceptions of Pair Programming and Agile Software Methodologies: Verifying a Model of Social Interaction. AGILE 2005: 323-330
[c38]Mark Sherriff, Nachiappan Nagappan, Laurie A. Williams, Mladen A. Vouk: Early estimation of defect density using an in-process Haskell metrics model. A-MOST 2005
[c37]Neha Katira, Laurie A. Williams, Jason A. Osborne: Towards increasing the compatibility of student pair programmers. ICSE 2005: 625-626
[c36]Hema Srikanth, Laurie Williams, Jason A. Osborne: System test case prioritization of new and regression test cases. ISESE 2005: 64-73
[c35]John D. Musa, Laurie A. Williams: How Should Software Reliability Engineering Be Taught? ISSRE 2005: 3
[c34]Laurie A. Williams: Teaching an Active-Participation University Course in Software Reliability and Testing. ISSRE 2005: 5
[c33]Nachiappan Nagappan, Laurie A. Williams, Jason A. Osborne, Mladen A. Vouk, Pekka Abrahamsson: Providing Test Quality Feedback Using Static Source Code and Automatic Test Suite Metrics. ISSRE 2005: 85-94
[c32]Jiang Zheng, Brian Robinson, Laurie A. Williams, Karen Smiley: An Initial Study of a Lightweight Process for Change Identification and Regression Test Selection When Source Code Is Not Available. ISSRE 2005: 225-234- 2004
[j8]Boby George, Laurie A. Williams: A structured experiment of test-driven development. Information & Software Technology 46(5): 337-342 (2004)
[j7]Sarah B. Berenson, Kelli M. Slaten, Laurie Williams, Chih-Wei Ho: Voices of women in a software engineering course: reflections on collaboration. ACM Journal of Educational Resources in Computing 4(1) (2004)
[j6]Laurie Williams: On the need for a process for making reliable quality comparisons with industrial data. ACM SIGSOFT Software Engineering Notes 29(5): 1-4 (2004)
[c31]Laurie A. Williams, Anuja Shukla, Annie I. Antón: An Initial Exploration of the Relationship Between Pair Programming and Brooks' Law. Agile Development Conference 2004: 11-20
[c30]Lucas Layman, Laurie A. Williams, Lynn Cunningham: Exploring Extreme Programming in Context: An Industrial Case Study. Agile Development Conference 2004: 32-41
[c29]Hema Srikanth, Laurie A. Williams, Eric Wiebe, Carol Miller, Suzanne Balik: On Pair Rotation in the Computer Science Course. CSEE&T 2004: 144-149
[c28]Chih-Wei Ho, Somik Raha, Edward F. Gehringer, Laurie Williams: Sangam: a distributed pair programming plug-in for Eclipse. ETX 2004: 73-77
[c27]Aldo Dagnino, Karen Smiley, Hema Srikanth, Annie I. Antón, Laurie A. Williams: Experiences in applying agile software development practices in new product development. IASTED Conf. on Software Engineering and Applications 2004: 501-506
[c26]Martin Davidsson, Jiang Zheng, Nachiappan Nagappan, Laurie A. Williams, Mladen A. Vouk: GERT: An Empirical Reliability Estimation and Testing Feedback Tool. ISSRE 2004: 269-280
[c25]Nachiappan Nagappan, Laurie A. Williams, John P. Hudepohl, Will Snipes, Mladen A. Vouk: Preliminary Results On Using Static Analysis Tools For Software Inspection. ISSRE 2004: 429-439
[c24]Neha Katira, Laurie A. Williams, Eric Wiebe, Carol Miller, Suzanne Balik, Edward F. Gehringer: On understanding compatibility of student pair programmers. SIGCSE 2004: 7-11
[c23]Joe Bergin, James Caristi, Yael Dubinsky, Orit Hazzan, Laurie A. Williams: Teaching software development methods: the case of extreme programming. SIGCSE 2004: 448-449- 2003
[j5]Laurie A. Williams, Alistair Cockburn: Guest Editors' Introduction: Agile Software Development: It's about Feedback and Change. IEEE Computer 36(6): 39-43 (2003)
[j4]Laurie A. Williams: Guest Editor's Introduction: The XP Programmer--The Few-Minutes Programmer. IEEE Software 20(3): 16-20 (2003)
[c22]E. Michael Maximilien, Laurie A. Williams: Assessing Test-Driven Development at IBM. ICSE 2003: 564-569
[c21]Laurie A. Williams, Charlie McDowell, Nachiappan Nagappan, Julian Fernald, Linda L. Werner: Building Pair Programming Knowledge through a Family of Experiments. ISESE 2003: 143-153
[c20]Laurie A. Williams, E. Michael Maximilien, Mladen A. Vouk: Test-Driven Development as a Defect-Reduction Practice. ISSRE 2003: 34-48
[c19]Nachiappan Nagappan, Laurie A. Williams, Mladen A. Vouk: "Good enough" software reliability estimation plug-in for Eclipse. OOPSLA Workshop on Eclipse Technology eXchange 2003: 30-34
[c18]Boby George, Laurie A. Williams: An Initial Investigation of Test Driven Development in Industry. SAC 2003: 1135-1139
[c17]Prashant Baheti, Laurie A. Williams, Aldo Dagnino, Andrew Cordes: On Identifying Deficiencies in a Knowledge Management System. SEKE 2003: 385-392
[c16]Nachiappan Nagappan, Laurie A. Williams, Miriam Ferzli, Eric Wiebe, Kai Yang, Carol Miller, Suzanne Balik: Improving the CS1 experience with pair programming. SIGCSE 2003: 359-362
[c15]P. David Stotts, Laurie A. Williams, Nachiappan Nagappan, Prashant Baheti, Dennis Jen, Anne Jackson: Virtual Teaming: Experiments and Experiences with Distributed Pair Programming. XP/Agile Universe 2003: 129-141
[c14]Nachiappan Nagappan, Laurie A. Williams, Eric Wiebe, Carol Miller, Suzanne Balik, Miriam Ferzli, Julie Petlick: Pair Learning: With an Eye Toward Future Success. XP/Agile Universe 2003: 185-198
[c13]Grigori Melnik, Laurie A. Williams, Adam Geras: International Workshop on Empirical Evaluation of Agile Methods ("The Data Workshop"). XP/Agile Universe 2003: 211- 2002
[j3]Jürgen Börstler, David A. Carrington, Gregory W. Hislop, Susan K. Lisack, Keith Olson, Laurie A. Williams: Teaching the PSP: Challenges and Lessons Learned. IEEE Software 19(5): 42-48 (2002)
[c12]Anuja Shukla, Laurie A. Williams: Adapting Extreme Programming for a Core Software Engineering Course. CSEE&T 2002: 184-191
[c11]Laurie A. Williams, Michael J. Lutz, Gregory W. Hislop, Michael McCracken, Nancy R. Mead, J. Fernando Naveda: Workshop 3: Integrating Agile Practices into Software Engineering Courses. CSEE&T 2002: 263-264
[c10]Mikael Lindvall, Victor R. Basili, Barry W. Boehm, Patricia Costa, Kathleen Coleman Dangle, Forrest Shull, Roseanne Tesoriero Tvedt, Laurie A. Williams, Marvin V. Zelkowitz: Empirical Findings in Agile Methods. XP/Agile Universe 2002: 197-207
[c9]Laurie A. Williams, Robert R. Kessler: Pair Programming: Experience the Difference. XP/Agile Universe 2002: 271-272
[c8]
[c7]Grigori Melnik, Laurie A. Williams, Adam Geras: Empirical Evaluation of Agile Processes. XP/Agile Universe 2002: 286
[e1]Don Wells, Laurie A. Williams (Eds.): Extreme Programming and Agile Methods - XP/Agile Universe 2002, Second XP Universe and First Agile Universe Conference Chicago, IL, USA, August 4-7, 2002, Proceedings. Lecture Notes in Computer Science 2418, Springer 2002, ISBN 3-540-44024-0- 2001
[c6]Laurie A. Williams: Integrating Pair Programming into a Software Development Process. CSEE&T 2001: 27-
[c5]Ryan A. Carter, Annie I. Antón, Laurie A. Williams, Aldo Dagnino: Evolving Beyond Requirements Creep: A Risk-Based Evolutionary Prototyping Model. RE 2001: 94-101
[c4]Laurie A. Williams, Richard L. Upchurch: In support of student pair-programming. SIGCSE 2001: 327-331
[c3]Carolee Stewart-Gardiner, David G. Kay, Joyce Currie Little, Joseph D. Chase, John Fendrich, Laurie A. Williams, Ursula Wolz: Collaboration vs plagiarism in computer science programming courses. SIGCSE 2001: 406-407- 2000
[j2]Laurie A. Williams, Robert R. Kessler: All I Really Need to Know About Pair Programming I Learned in Kindergarten. Commun. ACM 43(5): 108-114 (2000)
[j1]Laurie A. Williams, Robert R. Kessler, Ward Cunningham, Ron Jeffries: Strengthening the Case for Pair Programming. IEEE Software 17(4): 19-25 (2000)
[c2]Laurie A. Williams, Robert R. Kessler: The Effects of "Pair-Pressure" and "Pair-Learning" on Software Engineering Education. CSEE&T 2000: 59-65
[c1]Steven Fraser, Kent Beck, Ward Cunningham, Ron Crocker, Martin Fowler, Linda Rising, Laurie Williams: Hacker or hero? - extreme programming today (panel session). OOPSLA Addendum 2000: 5-7
Coauthor Index
data released under the ODC-BY 1.0 license. See also our legal information page
last updated on 2013-05-21 00:07 CEST by the dblp team



