2006 Software Development Test-Driven Development 
James Shore
JANUARY 11, 2019
I've been writing about agile software development for nearly 20 years, and most of it is available on this blog. Dependency Injection Demystified - 22 Mar, 2006. The Art of Agile Development (Book) - 2008. Continuous Integration on a Dollar a Day - 27 Feb, 2006. Test-driven development in a nutshell.
James Shore
JANUARY 11, 2019
I've been writing about agile software development for nearly 20 years, and most of it is available on this blog. Dependency Injection Demystified - 22 Mar, 2006. The Art of Agile Development (Book) - 2008. Continuous Integration on a Dollar a Day - 27 Feb, 2006. Test-driven development in a nutshell.
James Shore
JUNE 2, 2021
After that point, the software team supported the other engineering disciplines while continuing to do software enhancements. Van Schooenderwoert 2006]. These folks had everything stacked against them—except their coach and her approach to software development. Test-Driven Development.
James Shore
DECEMBER 4, 2020
1 See, for example, [Van Schooenderwoert 2006], [Mah 2006], and [Anderson 2006]. In addition to the structure of development, XP includes advanced technical practices that lead to excellence. The most well-known practice is test-driven development, which helps programmers write code that does exactly what they intend.
James Shore
NOVEMBER 12, 2020
Modern software development takes a lot of skills. Rooney 2006] experienced that problem, with regrettable results: We weren’t sure what our priorities were. Until then, development on an Agile team looks similar to development on any other team. Test Driven Development. Artistic skills.
James Shore
JUNE 7, 2021
It’s a joint look back at your development system for the purpose of learning and improving. As such, an effective analysis will involve the five stages of a retrospective: [Derby and Larsen 2006]. 3 The “appreciations” activity is based on [Derby and Larsen 2006] (pp. Close the retrospective.
James Shore
OCTOBER 27, 2020
Coffin 2006] describes an experience with two nearly identical teams: one that didn’t include users’ perspective and one that did. In particular, they need experience with test-driven development, refactoring, and evolutionary design. They often stem from outdated views of software development.
Expert insights. Personalized for you.
60 
Let's personalize your content