Remove 2006 Remove Continuous Integration Remove Test-Driven Development
article thumbnail

My Best Essays

James Shore

Dependency Injection Demystified - 22 Mar, 2006. The Art of Agile Development (Book) - 2008. Continuous Integration on a Dollar a Day - 27 Feb, 2006. An easier, cheaper (and better) way to do continuous integration. Testing Without Mocks: A Pattern Language - 27 Apr, 2018.

article thumbnail

My Best Essays

James Shore

Dependency Injection Demystified - 22 Mar, 2006. The Art of Agile Development (Book) - 2008. Continuous Integration on a Dollar a Day - 27 Feb, 2006. An easier, cheaper (and better) way to do continuous integration. Testing Without Mocks: A Pattern Language - 27 Apr, 2018.

article thumbnail

AoAD2 Practice: Refactoring

James Shore

Test-Driven Development. Technically, you can refactor at any time, but unless your IDE has provably-safe refactorings, it’s best to do it when you have a good suite of tests that are all passing. Test-Driven Development. 1 XXX replace with direct reference when Continuous Deployment is written.

article thumbnail

AoAD2 Chapter 2: Why Agile?

James Shore

1 See, for example, [Van Schooenderwoert 2006], [Mah 2006], and [Anderson 2006]. Programmers continuously integrate their code, which enables the team to release their software whenever it makes the most business sense. There’s no point in Agile for the sake of Agile. What will it take to achieve that success?

Agile 59
article thumbnail

AoAD2 Practice: Whole Team

James Shore

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. Continuous Deployment. Continuous Integration. Programming.

article thumbnail

AoAD2 Practice: Incident Analysis

James Shore

A programmer makes an off-by-one error, but their pairing partner suggests a test to catch it. A team member accidentally erases a file, but continuous integration rejects the commit. It’s a joint look back at your development system for the purpose of learning and improving. Close the retrospective.

article thumbnail

Lean Software Development: The Backstory

LeanEssays

This group has published numerous books and articles on lean thinking, lean manufacturing, and lean product development, including The Toyota Product Development System (Morgan and Liker, 2006), and Lean Product and Process Development (Ward, 2007). Put the tests into a test harness for ongoing code verification.