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

Re: [XP] Wikipedia XP article. Was: Which Extreme Programming?

Expand Messages
  • Ron Jeffries
    ... Thanks, I understand and agree. Ron Jeffries www.XProgramming.com 2 + 2 = 5, for sufficiently large values of 2.
    Message 1 of 5 , Jun 29, 2006
    • 0 Attachment
      On Thursday, June 29, 2006, at 8:00:12 PM, yahoogroups@... wrote:

      >> On Thursday, June 29, 2006, at 3:03:53 PM, yahoogroups@... wrote:
      >>
      >>> I just took a look at it, and I agree that it needs
      >>> a ground up rewrite. I'd take a fairly conservative
      >>> approach to how it's being practiced now.
      >>
      >> I don't understand this last sentence, please elaborate so that I
      >> can agree or disagree.

      > First, what are people actually doing? We have a
      > fair number of consultants and coaches on this list,
      > I think we have a pretty good handle on that.

      > By conservative, I mean trying to hit the center of
      > current practice and theory. Wikipedia has a fairly
      > definite policy of not wanting people to take extreme
      > views.

      > For example, if I was going to write the article, I'd probably
      > start off with something like:

      > -------------------------------

      > Extreme Programming (XP) is one of a group of
      > Agile methodologies. These methodologies use iterative
      > development methods to address the perceived failings
      > of more traditional methodologies which regard long
      > projects as single entities which are difficult to change
      > in midstream.

      > In common with most Agile methodologies, XP recommends
      > creating a new version of running, tested software on a
      > regular schedule. It recommends a one or two week schedule,
      > the iteration, which is shorter than many of the other Agile methods.
      > It differs from many of them in that it has a more developed set
      > of practices for development teams, and a more developed set of
      > practices for constructing the software.

      > --------------------

      > The I'd break it down into project management,
      > software construction and team practice, very much
      > like the three circle chart on your site, and finish
      > up with a discussion of how the values (feedback,
      > communication and so forth) feed into the practices.

      Thanks, I understand and agree.

      Ron Jeffries
      www.XProgramming.com
      2 + 2 = 5, for sufficiently large values of 2.
    Your message has been successfully submitted and would be delivered to recipients shortly.