aspose file tools*
The moose likes Agile and Other Processes and the fly likes Xtreme Programming Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Java 8 in Action this week in the Java 8 forum!
JavaRanch » Java Forums » Engineering » Agile and Other Processes
Bookmark "Xtreme Programming" Watch "Xtreme Programming" New topic
Author

Xtreme Programming

Ronnie Phelps
Ranch Hand

Joined: Mar 12, 2001
Posts: 329
Is Xtreme Programming an agile methodology?
Paul Sturrock
Bartender

Joined: Apr 14, 2004
Posts: 10336

Its a technique you can use on agile projects, though you don't have to for the project to use an agile approach.


JavaRanch FAQ HowToAskQuestionsOnJavaRanch
Ronnie Phelps
Ranch Hand

Joined: Mar 12, 2001
Posts: 329
That is kind of confusing. What makes a project agile?
Jeff Langr
author
Ranch Hand

Joined: May 14, 2003
Posts: 762
See http://agilemanifesto.org for starters; make sure you read the principles.


Books: Agile Java, Modern C++ Programming with TDD, Essential Java Style, Agile in a Flash. Contributor, Clean Code.
Ilja Preuss
author
Sheriff

Joined: Jul 11, 2001
Posts: 14112
Not everyone would agree that XP is a methodology. But it very certainly is part of whatever constitutes "Agile Software Development".


The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Ilja Preuss
author
Sheriff

Joined: Jul 11, 2001
Posts: 14112
Jeff Langr wrote:See http://agilemanifesto.org for starters; make sure you read the principles.


And the history!
Ronnie Phelps
Ranch Hand

Joined: Mar 12, 2001
Posts: 329
Okay I guess that makes senses. So Agile Methodologies are based on what is done and not how it is done. Correct?
Jeff Langr
author
Ranch Hand

Joined: May 14, 2003
Posts: 762
Ronnie Phelps wrote:So Agile Methodologies are based on what is done and not how it is done. Correct?


In a sense, perhaps. In general: the primary goal of an agile method is to be able to deliver high-quality software every few weeks or so ("Our highest priority is to satisfy the customer through early and continuous delivery of valuable software"). The short increments allow feedback (from the customer and from the data gathered around the reality of trying to deliver software every two weeks) and thus adaptation. That's the core; I think what makes the agile premise viable is the principles and values behind it.

There are about a half-dozen "major" agile methods, and they only have the values and principles in common. Actually I'd boil it down to three of any real relevance: Scrum, XP, and "we're kind of agile, I guess, and we do some of these things that Scrum or XP do." Some like Scrum are simply a "planning and organizational framework," to put it loosely.

XP, on the other hand, sits atop a similar framework, but also defines a number of fairly prescriptive elements, such as TDD and continuous integration, that a team should employ. In that sense, it does define some of "how it is done." Scrum does too, to a lesser extent. Maybe "agile" is more about what is done and the specific methodologies (XP, Scrum) are more about what that boils down to, i.e. how it's done.

Jeff
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Xtreme Programming
 
Similar Threads
What exactly is meant by Test-Driven Development?
Good reference for jBoss ?
Ant build separation
Web Services
Permission denied...focus