1. Houston 2015 COMFORTABLE SOFTWARE DEVELOPMENT FOR TEAMS FEATURE-DRIVEN DEVELOPMENT TM

2. Three reasons why FDD may not be for you…

3. Do you do that voodoo that you do, so well? Copyright 1974 by Warner Brothers, Inc.

4. Are you small? Hi, I’m Larry. This is my brother, Darryl. And this is my other brother, Darryl. And, our nephew, Steve Jobs.

5. You cannot champion change …nothing more difficult… …nor more doubtful of success… …nor more dangerous to handle… …has enemies in…the old order… …lukewarm defenders… …nothing more difficult… …nor more doubtful of success… …nor more dangerous to handle… …has enemies in…the old order… …lukewarm defenders…

6. i am curtis schlak

7. How to participate how i present

8. Comfort The premises and conclusions by which I entrust myself to FDD

9. Axiom software is about people 1

10. Axiom all methodologies provide an illusion of control 2

11. Corollary participants’ belief in a process enable the success of a process 1

12. Corollary participants’ belief in a process enables accurate reporting 2

13. What we need believability familiarity simplicity

14. FDD: Who/How High-Level Review of Feature-Driven Development

15. The roles in FDD project manager chief architect development manager chief programmers class owners* domain experts

16. Develop an Overall Model Build a Feature List Plan by Feature 213 BUFD! Phases 1 - 3

17. Design by Feature Build by Feature 54 Phases 4 and 5

18. The anatomy of a phase entry criteria tasks verification exit criteria

19. Example Requirements People join the club to become members and get invoiced monthly a flat fee and participation fees for classes Participation fees for classes consist of a prorated amount of the instructor’s hourly rate and a percentage of the cost of the equipment used by participants in the class Record member purchases of food and beverages from the club for rewards For every ten dollars spent on food and beverages from the club, the member receives a one dollar credit on their next invoice Members RSVP for classes and their arrival is recorded Instructors schedule rooms and equipment for classes

20. Develop an Overall Model Phase I

21. Model Building Mechanics tasks learn the domain develop the model verification by team output diagrams and notes

22. Four Categories of Domain Objects problem domain systems integration data management user interface

23. Problem Domain Advice problem domain modeling in color

24. Systems Integration and Data Management Advice systems integration data management traditional design enterprise patterns blah blah blah

25. User Interface Advice user interface hand waving and unicorns

26. A Note on Modeling domain-neutral component moment-interval moment-interval details role thing description

27. Example Model

28. Build a Features List Phase II

29. Features List Mechanics tasks build a features list verification by domain experts output a categorized list of features by business activity and feature type

30. Syntax of a Feature feature: «action» «result» «object» «calculate» the «total amount» of a «sale» «determine» the «total quantity sold by a retail outlet» for an «item description»

31. Syntax of a Business Activity business activity: «action» «object» «completing» a «sale» «forecasting» «inventory»

32. Syntax of a Subject Area subject area: «object» management «sales» management «inventory» management

33. Member Management Rewarding a Member «create» a «$1 credit» for a «member purchase» «create» an «invoice line item» for «every credit»

34. Plan by Feature Phase III

35. Features List Mechanics tasks determine development sequence assign business activities owners assign class owners Output development order completion dates owners

36. intermezzo fixed-cost estimates

37. Design by Feature Phase IV

38. Features List Mechanics tasks form the team review features and domain in-depth design verification through inspection output the “design package”

39. Task Percentages of Time walkthrough1% design40% inspection3%

40. Build by Feature Phase V

41. Build Mechanics tasks code verification through code inspections and unit tests output promote to main

42. Task Percentages of Time code45% inspection10% promote1%

43. Tracking and Reporting

44. All Percentages of Tasks walkthrough1% design40% design inspection3% code45% code inspection10% promote1%

45. Tracking by Feature

46. Burn-Up

47. Report Board Member Management Billing a Member (18) 77% March 2016 Rewarding a Member (4) April 2016 Invoicing a Member (7) 50% January 2016

48. Houston 2015 fin curtis@curtissimo.com