Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

James Newkirk

dblp:66/6896 · DBLP profile ↗
← Back
2ranked-venue papers
1as first author
0since 2021 · last 2003
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 2 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Empirical software engineering · 67% Requirements engineering and software design · 33%

Topics — the 3 heaviest of 3, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Empirical software engineering
agile software development
0.012002
Introduction to agile processes and extreme programming · ICSE 2002
Empirical software engineering › agile software development
extreme programming
0.012002
Introduction to agile processes and extreme programming · ICSE 2002
Requirements engineering and software design
software process
0.012002
Introduction to agile processes and extreme programming · ICSE 2002
YearPublicationVenuePosition
2003 Test Driven Development (TDD)
Steven Fraser 0001, Kent L. Beck, Bill Caputo, Tim Mackinnon, James Newkirk, Charlie Poole
XP5
2002 Introduction to agile processes and extreme programming
abstract
Extreme Programming is one of the most discussed subjects in the software development community. But what makes XP extreme? And how does it fit into the New World of agile methodologies? This tutorial will establish the underpinnings of agile methodology and explain why you might want to try one. Then we will see how XP uses a set of practices to build an effective software development team that produces quality software in a predictable and repeatable manner.
James Newkirk
ICSE1