● Github ("Source control" + issues manually entered)
● Sentry ("Exception monitoring")
● Mails ("Resouces monitoring")
● Slack ("Specifications")
First Dev1's commit
First work on tests tooling
First Dev2's commit
First Dev3's commit
First Dev4's commit
Start rush BigClient2. Mostly no tests during this phase
First release of the MTP package. Tests: 577
Docket pull request. Tests: 588
Jenkins for MTP is alive. Tests: 452
Automatic code analysis on Jenkins. Tests: 540
Start cleaning session
End cleaning session. Tests: 471
~End rush BigClient2
● Do you use source control?
● Can you make a build in one step?
● Do you make daily builds?
● Do you have a bug database?
● Do you fix bugs before writing new code?
● Do you have an up-to-date schedule?
● Do you have a spec?
● Do programmers have quiet working conditions?
● Do you use the best tools money can buy?
● Do you have testers?
● Do new candidates write code during their interview?
● Do you do hallway usability testing?
What does a product manager do every day?
What does it mean to an engineer that the code is a mess?
What was the designer trying to achieve with that colour change?
We want to communicate the value of the product in the first 5 minutes
We want to see whether customers engage with this new feature
We want to cut down how often our engineers get paged at 3am.
We want the main features to be at most 3 clicks away
A Holistic Approach to Quality -
The big picture
The Joel Test: 12 Steps to Better Code
Let's stop talking about quality