The Feature Trap    Michael Feathers
Is Scrum more than a Software     Development Process?
Who Has It Rough in Software      Development?
Hardware Companies
Banks and Insurance    Companies
Agile
XP
Scrum
Gatekeeper Organizational Pattern           Jim Coplien
The Planning Game   Kent Beck
Agile attempted to bridge thegap by bringing structure to the relationship between business        and development
Organizations, as a whole, need tounderstand the effects of their decisions
The Startup Crucible
“Systems develop goals of their own the instant they come into being.”         The Systems Bible - John Gall
The Function / Communication           Problem
The Dangers of Modularity
“All problems in computer science can be  solved by another level of indirection”            - David Wheeler
“All problems in computer science can be  solved by another level of indirection”            - David Wheeler              ...
Quality Assurance
“Between the Cracks”
Pressure Cookers
Pressure CookersSystems break at the weakest point under stress
Domain Agnostic Project Management
The Law of Leaky Abstractions “All non-trivial abstractions, to some degree, are leaky.”                                  ...
Features are a Leaky Abstraction   in Software Development
Features are a Leaky Abstraction   in Software Development Software development is too complicated to be     managed throu...
Project SubstrateAnything impacted by your decisions that can          affect your later decisions
The Substrate Problem
The things you don’t payattention to end up hurting you
Total Ignorance
Total IgnoranceMetrics Targeted
Whenever you say something is important, people hear it as “everything else is less important.”
Total Ignorance   Metrics TargetedQualitatively Assessing
Total Ignorance   Metrics TargetedQualitatively Assessing  Lifecycle Managing
Total Ignorance   Metrics TargetedQualitatively Assessing  Lifecycle Managing Integrated Knowing
Conway’s LawAny organization that designs a systemwill inevitably produce a design whosestructure is a copy of the organiz...
Org      Team             Code
Understand Substrate
Understand Substrate + Allocate Talent
At what point does technical debt    become a runaway cost?
At what point does technical debt    become a runaway cost?       Sooner than we realize
Boiled Frog Syndrome
Features are a Leaky Abstraction   in Software Development Software development is too complicated to be     managed throu...
The Challenge
The ChallengeFind innovative ways to manage the substrate
Thank You
Keynote Scrum Gathering Barcelona 2012
Keynote Scrum Gathering Barcelona 2012
Keynote Scrum Gathering Barcelona 2012
Keynote Scrum Gathering Barcelona 2012
Keynote Scrum Gathering Barcelona 2012
Keynote Scrum Gathering Barcelona 2012
Keynote Scrum Gathering Barcelona 2012
Keynote Scrum Gathering Barcelona 2012
Keynote Scrum Gathering Barcelona 2012
Keynote Scrum Gathering Barcelona 2012
Keynote Scrum Gathering Barcelona 2012
Keynote Scrum Gathering Barcelona 2012
Upcoming SlideShare
Loading in …5
×

Keynote Scrum Gathering Barcelona 2012

1,709 views

Published on

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,709
On SlideShare
0
From Embeds
0
Number of Embeds
46
Actions
Shares
0
Downloads
18
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Keynote Scrum Gathering Barcelona 2012

    1. 1. The Feature Trap Michael Feathers
    2. 2. Is Scrum more than a Software Development Process?
    3. 3. Who Has It Rough in Software Development?
    4. 4. Hardware Companies
    5. 5. Banks and Insurance Companies
    6. 6. Agile
    7. 7. XP
    8. 8. Scrum
    9. 9. Gatekeeper Organizational Pattern Jim Coplien
    10. 10. The Planning Game Kent Beck
    11. 11. Agile attempted to bridge thegap by bringing structure to the relationship between business and development
    12. 12. Organizations, as a whole, need tounderstand the effects of their decisions
    13. 13. The Startup Crucible
    14. 14. “Systems develop goals of their own the instant they come into being.” The Systems Bible - John Gall
    15. 15. The Function / Communication Problem
    16. 16. The Dangers of Modularity
    17. 17. “All problems in computer science can be solved by another level of indirection” - David Wheeler
    18. 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. 19. Quality Assurance
    20. 20. “Between the Cracks”
    21. 21. Pressure Cookers
    22. 22. Pressure CookersSystems break at the weakest point under stress
    23. 23. Domain Agnostic Project Management
    24. 24. The Law of Leaky Abstractions “All non-trivial abstractions, to some degree, are leaky.” Joel Spolsky
    25. 25. Features are a Leaky Abstraction in Software Development
    26. 26. Features are a Leaky Abstraction in Software Development Software development is too complicated to be managed through the prism of features
    27. 27. Project SubstrateAnything impacted by your decisions that can affect your later decisions
    28. 28. The Substrate Problem
    29. 29. The things you don’t payattention to end up hurting you
    30. 30. Total Ignorance
    31. 31. Total IgnoranceMetrics Targeted
    32. 32. Whenever you say something is important, people hear it as “everything else is less important.”
    33. 33. Total Ignorance Metrics TargetedQualitatively Assessing
    34. 34. Total Ignorance Metrics TargetedQualitatively Assessing Lifecycle Managing
    35. 35. Total Ignorance Metrics TargetedQualitatively Assessing Lifecycle Managing Integrated Knowing
    36. 36. Conway’s LawAny organization that designs a systemwill inevitably produce a design whosestructure is a copy of the organizationscommunication structure.
    37. 37. Org Team Code
    38. 38. Understand Substrate
    39. 39. Understand Substrate + Allocate Talent
    40. 40. At what point does technical debt become a runaway cost?
    41. 41. At what point does technical debt become a runaway cost? Sooner than we realize
    42. 42. Boiled Frog Syndrome
    43. 43. Features are a Leaky Abstraction in Software Development Software development is too complicated to be managed through the prism of features
    44. 44. The Challenge
    45. 45. The ChallengeFind innovative ways to manage the substrate
    46. 46. Thank You

    ×