Sublime

To the extent that we are able to embed testing practice inside development, we have created a process that is hyper-incremental where mistakes can be rolled back if any one increment turns out to be too buggy. We’ve not only prevented a lot of customer issues, we have greatly reduced the number of dedicated testers necessary to ensure the absence

When you remove a practice, you can safely do so if you retain the value that practice was providing. As an example, dropping ideal developer days as a measure and not estimating at all may be unwise, but replacing this technique with a relative measure, such as tee-shirt sizing, is smart; it retains the value that estimation provides and brings be

Test as you go, not at the end—a bug fixed now is cheaper than one that has had a chance to propagate through a system for months. Deliver product early and often, as only by demonstrating working software to your customer can you find out what they really want.

I was the third consultant they hired, and the first not to address it as a “people issue.” What I saw was a legacy code issue. Their software was brittle and hard to work with.

She certainly will. But we’ll ask her, as a favor, to do her growing on the next project. We’ll ask her to do one time for us what she has successfully done before for others. We’ll do that for each project, ask people to defer for a bit the chance to take on a real stretch goal, and repeat, just one time, what they already know they can do success