Loading ...
Sorry, an error occurred while loading the content.

RE: [scrumdevelopment] The Structure of Scientific Revolutions - Thomas Kuhn

Expand Messages
  • Pam Rostal
    Thanks Mike, They re in my to-read pile for the literature review. Pam ... From: Mike Beedle [mailto:beedlem@e-architects.com] Sent: Friday, April 30, 2004
    Message 1 of 7 , Apr 30, 2004
    • 0 Attachment
      Thanks Mike,

      They're in my to-read pile for the literature review.


      -----Original Message-----
      From: Mike Beedle [mailto:beedlem@...]
      Sent: Friday, April 30, 2004 2:51 PM
      To: scrumdevelopment@yahoogroups.com
      Subject: RE: [scrumdevelopment] The Structure of Scientific Revolutions
      - Thomas Kuhn

      Pam writes:
      > I think part of our industry's problem is the
      > lack of attention paid to our own history and the analogies
      > between it and other disciplines who have survived their
      > own paradigm shifts (hopefully, Dave West's book will
      > address some of this).


      Yes, it is an acknowledged fact among long-time practitioners
      with even average memory that our industry tends to *forget*
      "previous art".

      This is apparent from the point of view of methodology, like the
      forgotten origins of Open Source and Agile Development (dating back
      to the MIT Lisp culture); through the invention of the first computer
      -- Zuzze's Z1; through the forgotten origins of languages like the
      origin of Object Oriented technologies dating back to Simula and the
      concept of "frames" at the MIT AI lab in the 1960's; through major
      embarrassments like Wolfram's New Science -- Zuzze had made identical
      proposals in the 60's.

      How ironic that the very people in charge of "information technology",
      and "information management" would be in fact "prone to forget

      Pam writes:
      > The agile methodologies, by contrast, contend that this approach does
      > support success in highly dynamic endeavors where an empirical
      > is necessary to keep efforts focused on a goal that only becomes
      > well-defined as it is attained; hence, their emphasis is on empirical
      > processes (Highsmith, Agile Software Development Ecologies).

      Btw, since, we are talking about previous art, you might want to
      quote Schwaber's 1996 OOPSLA Scrum paper when you talk about
      "empirical approaches to software development". I believe this is
      one of the first references that talks about "empirical approaches"
      within the software development domain.

      Another one is Jim Coplien's et al, Organizational Patterns, described
      in their many papers dating back to 1992. (Patterns, by definition,
      are an "empirical approach".)

      And by implication, as case studies, all references and writings
      of Jeff Sutherland about their early experiences with Scrum dating
      back to 1993. [A historical footnote: Jeff was trying to emulate
      the Quattro Pro team at EASEL in 1993 (based on dense social
      interactions and "daily meetings" ); so the "Scrum approach", greatly
      overlaps with the "org patterns" approach.]

      - Mike

      To Post a message, send it to: scrumdevelopment@...
      To Unsubscribe, send a blank message to:
      Yahoo! Groups Links
    Your message has been successfully submitted and would be delivered to recipients shortly.