15. © Douglas Bray

17. * - paraphrased

22. WaterfallScrum / Agile Requirements docsJust-in-time, informal requirements Occasional “customer” involvementFrequent “customer” involvement Start-to-finish Project PlanProduct Backlog. Plan for Sprint. Details are sketchy beyond that. Priorities shift based on new data. Tasks are assignedAssigned tasks are a bottleneck Potentially large team sizeTeams of 3 – 9 people Multiple phases, eventual deliveryWorking software each Sprint / Iteration Resistant to changeChange is expected Contract says what we build, deliverContract is a lot closer to T&E

29. “Too complex to plan.”

110. http://www.bbc.co.uk/programmes/b01hl293

116. http://www.benday.comhttp://www.benday.com | benday@benday.combenday@benday.com