James Shore

JANUARY 10, 2025

We use Extreme Programming as our model of how to develop software. They also love test-driven development, pairing, continuous integration, and evolutionary design. They tend to be passionate, senior developers. This is a matter of changing organizational culture, and organizational culture isnt easy to change.

Engineering 141

Engineering Software Review Weak Development Team Agile 141

James Shore

JUNE 2, 2021

The first field test units were delivered after approximately six months into development. Van Schooenderwoert 2006]. These folks had everything stacked against them—except their coach and her approach to software development. Test-Driven Development. Test-Driven Development.

Software Review 80

Software Review Systems Review Technical Review Test-Driven Development 80

James Shore

NOVEMBER 12, 2020

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. Test Driven Development. Programming. Pair Programming.

Weak Development Team 86

Weak Development Team UI/UX Coaching Software Review 86

James Shore

MARCH 12, 2021

Test-Driven Development. Take small steps—test-driven development works well—and talk about your assumptions, short-term goals, general direction, and any relevant history of the feature or project. Test-Driven Development. Use test-driven development and take very small steps.

Programming 56

Programming Software Review Technical Review Test-Driven Development 56

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. If you can’t get the business, customer, or user expertise you need. That’s okay.

Agile 132

Agile Software Review Coaching Weak Development Team 132

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.

Analysis 72

Analysis Weak Development Team Software Review Systems Review 72

LeanEssays

JUNE 5, 2015

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.

Software Development 55

Software Development Software Review Software Development 55