sebastianrothbucher · December 4, 2015 07:39
diff --git a/gistfile1.txt b/gistfile1.txt
 In order to kick it (based on more or less pleasant experience), you should...
 ... have few but good documents - most importantly one of them should be a VERY GOOD EXAMPLE (a walkthrough in painstaking detail: invent IDs, names, also Phone #s and so on)
 ... another one is a comprehensive list of Use Cases (and surrounding systems supporting them; acc. 2 MCQ, you need just few days 2 compile)
 ... write down what will be checked before signing off the result (aka ATDD)
 ... rock-solid and well-thought-through core classes (data model, UI structure)
 ... adjust regularly, but not always (i.e. do sprints)
	In order to kick it (based on more or less pleasant experience), you should...
	... have few but good documents - most importantly one of them should be a VERY GOOD EXAMPLE (a walkthrough in painstaking detail: invent IDs, names, also Phone #s and so on)
	... another one is a comprehensive list of Use Cases (and surrounding systems supporting them; acc. 2 MCQ, you need just few days 2 compile)
	... write down what will be checked before signing off the result (aka ATDD)
	... rock-solid and well-thought-through core classes (data model, UI structure)
	... adjust regularly, but not always (i.e. do sprints)