Leanpub Header

Skip to main content

Trust Driven Development

Trust Driven Development is about the profession of building successful software. about planning for change, about process, and above all, about trust. Process is what we do to make sure that everybody on a project has a shared sense of state and of goals. Trust is what happens when we match that shared state and meet those goals.

Minimum price

$15.00

$25.00

You pay

$25.00

Author earns

$20.00
$

...Or Buy With Credits!

You can get credits monthly with a Reader Membership
PDF
EPUB
WEB
About

About

About the Book

Trust Driven Development is about the profession of building successful software. It talks about about planning for change, about process, and above all, about trust.

Process is what we do to make sure that everybody on a project has a shared sense of state and of goals. Trust is what happens when we match that shared state and meet those goals.

At some point in your software project, something will go wrong. There will be a miscommunication or a sudden change of requirements. You might even make a mistake. What happens then depends on a lot of factors, some of which are outside your control.

One factor that is in your control is whether you’ve presented yourself as worthy of your partner’s trust so that rough spots along the project path can be approached in the sprit of collaboration and not fighting over blame.

Bad process and a lack of trust cause real difficulty in projects and make developer and customer lives more painful. It can be better. This book can help.

Author

About the Author

Noel Rappin

Noel Rappin is the Director of Development at Table XI. Noel has authored multiple technical books, including "Rails 4 Test Prescriptions", "Trust-Driven Development", and "Take My Money: Accepting Payments on the Web". Follow Noel on Twitter @noelrap, and online at http://www.noelrappin.com.

Leanpub Podcast

Episode 56

An Interview with Noel Rappin

Contents

Table of Contents

A Fable About Trust

  1. Trust Driven Development
  2. Back to the Mechanic
  3. Project Zen
  4. Where to?
  5. IBefore You Start

1.What is a Project?

  1. Trust Me
  2. 1.1What is “Process”
  3. Trust Me

2.Who are the Players?

3.What do I Need Before I Start?

  1. Trust Me
  2. 3.1Sharing Knowledge
  3. Trust Me
  4. 3.2What to Share?

4.What prevents sharing?

5.What do First Meetings Look Like?

  1. 5.1Getting the initial feature list
  2. Trust Me
  3. Trust Me
  4. 5.2Workflows
  5. Trust Me

6.Initial Estimates

  1. 6.1Let’s talk about #NoEstimates
  2. 6.2Making story lists and estimates
  3. 6.3Converting the list to something resembling an estimate

7.What do Clients Need To Know?

  1. 7.1Okay, so what’s the problem…

8.Iteration Zero

  1. 8.1Setting up Environments, Continuous Integration, and Continuous Deployment
  2. Trust Me
  3. 8.2Team Agreements
  4. 8.3Spikes and Technology decisions
  5. IIIteration Heartbeat

9.Iterations

  1. 9.1What’s an iteration?
  2. 9.2Why Iterations?
  3. 9.3What happens in an iteration?
  4. 9.4How long should an iteration be?
  5. 9.5A Quick Plea About Days of the Week
  6. 9.6The Iteration Planning Meeting
  7. 9.7Iteration process smells
  8. 9.8When don’t I need iterations?
  9. 9.9When should I worry?

10.Retrospectives

  1. 10.1When
  2. 10.2Who
  3. 10.3How

11.Where Do Stories Come from?

  1. 11.1What makes a story?
  2. 11.2Lifecycle of a story

12.Estimation and Velocity

  1. 12.1The Rules
  2. 12.2Why Estimate?
  3. 12.3What are you estimating?
  4. 12.4One Plus One Equals Three, or Point Math
  5. 12.5Validating Estimates
  6. 12.6Estimation in Context, or Estimation in Conflict
  7. 12.7Should You Estimate Bugs?
  8. 12.8Why does this work?

13.Responding to Change

  1. 13.1What’s a change?
  2. Trust Me
  3. Trust Me
  4. IIIDaily Heartbeat

14.Daily Stand Up

  1. 14.1Build A Better Standup
  2. 14.2Date and Time
  3. 14.3Who attends?
  4. 14.4The Virtual Standup

15.Doing The Work

16.Pair Programming vs Code Review

  1. 16.1Effective Pairing
  2. 16.2Code Review
  3. 16.3Code standards and documentation

17.Remote Work

  1. 17.1Set up communication early
  2. 17.2Conway’s Law, Remote Teams, and You
  3. 17.3Split Sites
  4. 17.4Remote Meetings
  5. 17.5When Not To Remote

18.Release Management

  1. 18.1Code Freeze
  2. 18.2Release cutover
  3. 18.3Staging “plus”
  4. 18.4Feature block
  5. 18.5When to deploy?

19.Testing

  1. 19.1When to Deploy to Stage
  2. 19.2When to Deploy to Production

20.Bugs

  1. 20.1Building Trust Before Bugs Happen
  2. 20.2Building Trust When Bugs Happen
  3. 20.3Fixing Bugs
  4. 20.4Bug or Feature?
  5. 20.5Flavors of bugs
  6. 20.6When Bugs Get Serious
  7. IVCrunch Time

21.Crunch Time

  1. 21.1The End Game
  2. 21.2Attention Must Be Paid
  3. 21.3Deadlines
  4. 21.4End Game Review
  5. 21.5Code Freeze is never a freeze
  6. 21.6One More Thing
  7. 21.7Continuous Crunch
  8. 21.8Plan for the End

22.Responding To Problems

23.I made a mistake

  1. Trust Me

24.Professionalism in a Hostile Environment

  1. 24.1I think what you are doing is a bad idea
  2. Trust Me
  3. 24.2The project keeps changing
  4. 24.3Scope Creep
  5. 24.4The client has unreasonable time and scope expectations
  6. 24.5I way underestimated this feature/project
  7. 24.6People on this project are not executing
  8. 24.7I don’t have agency, the team is too big
  9. 24.8I’m having personal issues with the client
  10. 24.9The client hates what they said they wanted

25.End of Life

Colophon

Acknowledgements

Changelog

The Leanpub 60 Day 100% Happiness Guarantee

Within 60 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.

Now, this is technically risky for us, since you'll have the book or course files either way. But we're so confident in our products and services, and in our authors and readers, that we're happy to offer a full money back guarantee for everything we sell.

You can only find out how good something is by trying it, and because of our 100% money back guarantee there's literally no risk to do so!

So, there's no reason not to click the Add to Cart button, is there?

See full terms...

Earn $8 on a $10 Purchase, and $16 on a $20 Purchase

We pay 80% royalties on purchases of $7.99 or more, and 80% royalties minus a 50 cent flat fee on purchases between $0.99 and $7.98. You earn $8 on a $10 sale, and $16 on a $20 sale. So, if we sell 5000 non-refunded copies of your book for $20, you'll earn $80,000.

(Yes, some authors have already earned much more than that on Leanpub.)

In fact, authors have earned over $14 million writing, publishing and selling on Leanpub.

Learn more about writing on Leanpub

Free Updates. DRM Free.

If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).

Most Leanpub books are available in PDF (for computers) and EPUB (for phones, tablets and Kindle). The formats that a book includes are shown at the top right corner of this page.

Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.

Learn more about Leanpub's ebook formats and where to read them

Write and Publish on Leanpub

You can use Leanpub to easily write, publish and sell in-progress and completed ebooks and online courses!

Leanpub is a powerful platform for serious authors, combining a simple, elegant writing and publishing workflow with a store focused on selling in-progress ebooks.

Leanpub is a magical typewriter for authors: just write in plain text, and to publish your ebook, just click a button. (Or, if you are producing your ebook your own way, you can even upload your own PDF and/or EPUB files and then publish with one click!) It really is that easy.

Learn more about writing on Leanpub