Schedule
	Why are things slipping?
	When schedules slip
		Add people
		Add time
		Take out some requirements
	Freehand cropping is the most important part of the project
	Metrics are "Alarming"
Test Cases
	Should we document unit tests?
		Ensures coverage
	This is an acceptance test case, not a test plan
		Plan:
			What are the major points to test?
				Test that the system can handle X images
				What is the set of images to use when testing
	The test cases don't quite match up with the storyboards
	
	1.1
		Add instructions
		Has help button
		Some images may be rotated
		"Goes to Image Preview Screen"
			Screenshots?
		Don't skip over information (including what buttons are available)
		Call this "Initial state"
	
	1.2
		Output: "6-up button is disabled"
		
	
		Call it "down and up" arrows
		Make a new cases for left-to-right scrolling
	
	1.6
		Make up some hard values
			In the steps of the task, and 
		Or there can be a "until something specific happens" case
	
	Add a "Do these things when starting the following cases" section
	
	2.1
		Take this out
		
	2.2
		Test all the buttons on the screen
		Have outputs for each
	
	Heart
		Maintains heart shape while getting bigger…
		
	Define initial states of the screens in index and reference back
	What images will be in the test case
		Different orientations
		Long file names
		Corrupted images
		Images that have the wrong extension
		Invalid extension'd images
	
	Add a "which screen am I in?" section to the initial state
	
	Define what happened to the image when moving it to the collage
		
		On top of other images
		Feathered
		Placed in the center of the collage
		At "Default Size"  (define default size)
		
Do updates over break on Tuesdays

Come up with a "Which Test Cases make this which release"