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

Re: Agile and Academia

Expand Messages
  • rasmus4200
    Hi Anders, Very interesting article. I agree with the premise of what you are saying but I would add it goes even much deeper than that. Our institutions have
    Message 1 of 6 , Nov 26 5:23 AM
      Hi Anders,

      Very interesting article. I agree with the premise of what you are saying but I would add it goes even much deeper than that.

      Our institutions have been separating roles and responsibilities for many many years. BA, QA, developer, PM, UX etc has been the traditional way projects have been developed for decades.

      And every time we form agile teams in large organizations we come up against that baked in calcification of roles and responsiblities (I am responsible for these, they do that).

      The evidence comment is interesting because it very hard to prove anything when it comes to productivity and software. All we have is anecdotal evidence. My experience against yours. And I actually kind of find it refreshing for someone to say waterfall has worked for them because in my experience is completely the opposite, and this is the first person I have heard in a long time say they like waterfall.

      But I agree with your original assertion, and I am encourage that institutions like Carnegie Mellon are working towards more cross functional disciplines.

      Thanks for sharing. That was a great post.

      Cheers - Jonathan

      --- In agile-usability@yahoogroups.com, Anders Ramsay <andersr@...> wrote:
      > Hi,
      > I recently posted a blog entry on why I think one key source for much
      > of the Us/Them mentality between UX designers and agile software
      > developers (at least what I have experienced) can be traced back to
      > how we are separated during our formative years in educational
      > institutions, with those studying computer science not having much
      > contact with those studying graphic design, or more recently
      > interaction design. Many of them have never actually worked with
      > those from the other discipline until after graduating and find
      > themselves thrown into project teams with people who may be looking at
      > the craft of software development from a completely different
      > perspective. The full post is at http://is.gd/516fE
      > Is this an accurate assessment? Am I making too much out of this
      > separation? Are there educational institutions that have take steps to
      > better integrate the various disciplines the eventually will need to
      > collaborate in the workplace?
      > I also received an interesting comment to my posting, and would love
      > to hear what people on this list have to say about the following:
      > [In response to me proposing is that educational programs incorporate
      > pairing across disciplines.]
      > Commenter: "Your whole article assumes a truism that I'm not sure has
      > been proven, especially at the academic level, which is that pairing
      > is more efficient (same or cross-disciplinary)."
      > Commenter: "In my experience a solid waterfall approach has been
      > infinitely more successful cross-disciplinarily than any type of good
      > or bad Agile I have worked with (and I've been forced to work with
      > many). Statistically or through any other empirical measure (and I
      > don't have anything but anecdotal evidence myself) no one has PROVEN
      > that Agile is better than non-agile."
      > -Anders
    Your message has been successfully submitted and would be delivered to recipients shortly.