You should iterate sequentially on a focused chunk of work at a time.
When software behaves unexpectedly, it should be easy to understand what is causing the problem.
Data should be held in one location, duplicates of that data should be by reference only.
Always plan for a way to switch your work off
Capture your understandings separately to the team and then come together to align
Act on unalignment rapidly to ensure happy teams
When creating something, it is better to understand the picture - at a high level - instead of focusing on the thing you need to create immediately.
The greater the number of people who can work on a problem, the higher the probability of an optimal solution.
Adam Craven & russmiles
