The Chicago Process: How Braintree Develops Software
Switch branches/tags
Nothing to show
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
0000.start.html
0100.team.html
0200.engine.html
0300.product.manager.html
0400.dev.lead.html
0500.iterations.html
0600.standups.html
0700.pairing.html
0800.testing.html
0900.decisions.html
1000.silos.html
1100.summary.html
README.md
TITLE

README.md

The Chicago Process - How Braintree Develops Software

Braintree needs to be highly available and secure, while still maintaining a rapid development pace and strict backwards compatibility. In order to achieve that, we use what has become known as the "Chicago Process". This involves pairing, strict TDD, a team structure, and weekly iterations, all to empower the devs to make decisions and get work of a high quality done while avoiding siloing.

These are my slides. You can view them using SnippetSlide.