1. The Feature Trap
Michael Feathers

2. Is Scrum more than a Software
Development Process?

3. Who Has It Rough in Software
Development?

4. Hardware Companies

5. Banks and Insurance
Companies

6. Agile

7. XP

8. Scrum

9. Gatekeeper Organizational Pattern
Jim Coplien

10. The Planning Game
Kent Beck

11. Agile attempted to bridge the
gap by bringing structure to the
relationship between business
and development

12. Organizations, as a whole, need to
understand the effects of their decisions

13. The Startup Crucible

14. “Systems develop goals of their own
the instant they come into being.”
The Systems Bible - John Gall

15. The Function / Communication
Problem

16. The Dangers of Modularity

17. “All problems in computer science can be
solved by another level of indirection”
- David Wheeler

18. “All problems in computer science can be
solved by another level of indirection”
- David Wheeler
Maybe:
All human problems can be solved by
removing a level of indirection

19. Quality Assurance

20. “Between the Cracks”

21. Pressure Cookers

22. Pressure Cookers
Systems break at the weakest point under stress

23. Domain Agnostic Project Management

24. The Law of Leaky Abstractions
“All non-trivial abstractions, to some degree, are leaky.”
Joel Spolsky

25. Features are a Leaky Abstraction
in Software Development

26. Features are a Leaky Abstraction
in Software Development
Software development is too complicated to be
managed through the prism of features

27. Project Substrate
Anything impacted by your decisions that can
affect your later decisions

28. The Substrate Problem

29. The things you don’t pay
attention to end up hurting you

30. Total Ignorance

31. Total Ignorance
Metrics Targeted

34. Whenever you say something is important, people
hear it as “everything else is less important.”

35. Total Ignorance
Metrics Targeted
Qualitatively Assessing

39. Total Ignorance
Metrics Targeted
Qualitatively Assessing
Lifecycle Managing

42. Total Ignorance
Metrics Targeted
Qualitatively Assessing
Lifecycle Managing
Integrated Knowing

43. Conway’s Law
Any organization that designs a system
will inevitably produce a design whose
structure is a copy of the organization's
communication structure.

44. Org
Team
Code

46. Understand Substrate

47. Understand Substrate + Allocate Talent

49. At what point does technical debt
become a runaway cost?

50. At what point does technical debt
become a runaway cost?
Sooner than we realize

54. Boiled Frog Syndrome

55. Features are a Leaky Abstraction
in Software Development
Software development is too complicated to be
managed through the prism of features

56. The Challenge

57. The Challenge
Find innovative ways to manage the substrate

58. Thank You