2. Get the New Agile Attitude: Quality First! Object Mentor, Inc. Copyright  1998-2004 by Object Mentor, Inc All Rights Reserved www.objectmentor.com www.junit.orgwww.xprogramming.comfitnesse.org Robert C. Martin (Uncle Bob) unclebob@objectmentor.com

3. 2 The Traditional schedule for Quality. Waiting at the sphincter muscle. Analysis Design Implementation 1 May1 Nov1 Jul1 Sep Test

4. 3 When Quality comes at the end. It is under the most pressure. It has the least flexibility. It is a high stress tedious job. It is error prone. Quality cannot be tested in.

5. Quality is a specification role… …not a verification role!

6. 5 What is the first thing known about a project? The Management Paradox

7. 6 ! ! ! !

8. 7 The Delivery Date is Frozen

9. 8 The Spec V1 The Spec V2 The Spec V3 The Spec V3 The Spec VN.1 The Spec VN.2 The Spec is Never Frozen

10. 9 Analysis Design Implementation DFDERDDDST 1 May1 Nov1 Jul1 Sep The Waterfall Model Managing the Development of Large Software Systems Dr. Winston W. Royce — 1970

11. 10 Analysis Design Implementation What Royce really meant No dates, full feedback. Concurrent development.

12. 11 Royce’s actual diagram.

13. 12 Royce’s Observation

14. 13 Royce’s Conclusion

15. 14 Analysis Design Implementation DFDERDDDST 1 May1 Nov1 Jul1 Sep The Boss’ Big Meeting. We have a new project…

16. 15 Requirements and Failure Jarzombek Study. Failure attributed to use of waterfall. And let’s not forget the $170,000,000 spent on the FBI system.

17. 16 Over specification.

18. 17 Management requires Data Waterfall fails because it does not produce any data. Without data we cannot manage the tradeoffs.

19. 18 The inevitable trade-off. Good (Quality) Fast (Time to Market) Cheap (Cost Effectiveness) Done Pick any three…

20. 19 Finding the optimum solution. We need to manage the project to the best possible outcome. An outcome that maximizes all four qualities. To do this, we need: Data.

21. 20 Wouldn’t this be great?

22. 21 …and this…

23. 22 If we had these two charts on the wall… Then managers could just look at them to see The status of the project.

24. 23 Iterative Development. UI Comms Control Some UI, Comms, and Control for some behavior Data is generated and used to calibrate the plan

25. 24 Calculate the Date. The Calculated Date.... []

26. 25 More data shrinks the error bars. The Calculated Date.... []

27. 26 Without data, all you can manage is: ! ! !

28. 27 Without data managers can: This project will be done on time! Or HEADS will ROLL!

29. 28 OR…. You guys are great. I have faith in you. I know you can do it! I sure hope you can

30. 29 But when we have data… Managers can…. manage.

31. 30 The control knobs of project mgt. Schedule Quality Staff Scope

32. How do you know a slice is done?

33. 32 Test in an Agile Department Test

34. 33 Tests specify each iteration.

35. 34 Tests specify each iteration.

36. A feature is not specified… Until it’s acceptance test is written.

37. A feature is not done… Until all it’s acceptance tests pass.

38. 37 Acceptance Tests Are… Automated. written in a very high level language. executed frequently. written by the stakeholders.

39. A Simple Example

40. The result.

41. Did I mention that they are automated?

42. 41 Manual Acceptance Tests.

43. 42 Manual Acceptance Tests. There aren’t any.

44. 43 Review Question.

45. 44 Review Question. Are there any manual acceptance tests?

46. The Quality First Attitude: Everything can be automatically tested.

47. 46 When is the best time to write them? Astute test managers Talk to the stakeholders days before each iteration. Write initial acceptance tests for the features they plan to schedule. Elaborate those acceptance tests once scheduled.

48. 47 When is the best time to run them? Continuously. At every check-in. No change is allowed to break any passing tests. Continuous Integration.

49. 48 Who runs them? Developers. Testers. Managers. Stakeholders. …They are run automatically. …Results are displayed on the wall.

50. 49 This keeps the data accurate… …and actionable.

51. 50 So… An agile quality department must: Become the specification department. Write automated specifications. Collaborate with developers every week. Continuously run all acceptance tests. Get tool support.

52. 51 And put quality FIRST. At the front of the process.

53. 52 Sample Acceptance Tests. CW-CRM. FitNesse

54. 53 Acceptance Testing Tools + FIT http://fit.c2.com FitNesse http://fitnesse.org Robert C. Martin (Uncle Bob) unclebob@objectmentor.com