Completed
Code Katas
Class Central Classrooms beta
YouTube videos curated by Class Central.
Classroom Contents
Pair Programming, TDD and Other Impractical Things
Automatically move to the next video in the Classroom when playback concludes
- 1 Intro
- 2 coding is not as hard as collaborating
- 3 Listen to your customer
- 4 First create a project mission based on business goals..
- 5 Test Driven Development
- 6 impractical
- 7 most of the cost in software comes from feedback delay
- 8 1. All tests run and pass 2. Remove duplication 3. Remove opacity 4. Remove complexity
- 9 THE CODE IS TERRIBLE!! WE NEED ONE SPRINT TO REFACTOR
- 10 There is no refactoring without tests There is no testing without refactoring
- 11 refactoring === design
- 12 Focus on Quality over Schedule
- 13 But what causes poor Outer Quality?
- 14 Lack of automated acceptance tests Lack of customer involvement Team not focused on Project Mission Lack of Inner Quality
- 15 How do you ensure Outer Quality?
- 16 Example workshops Automate acceptance tests Have a sprint vision statement Sign off during Sprint
- 17 How do you ensure Inner Quality?
- 18 2 developers sharing a screen working on the same task
- 19 What is Pair Programming about?
- 20 Jon Jagger's Principles of Improvement
- 21 Pair programming is about improving faster
- 22 Strengthening the case for pair programming
- 23 Should pairs be kept together?
- 24 Code Katas
