• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Tim Cooke
  • Jeanne Boyarsky
  • Bear Bibeault
Sheriffs:
  • Knute Snortum
  • paul wheaton
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Ron McLeod
  • Piet Souris
  • Ganesh Patekar
Bartenders:
  • Tim Holloway
  • Carey Brown
  • salvin francis

Xtreme Programming

 
Ranch Hand
Posts: 329
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Is Xtreme Programming an agile methodology?
 
Bartender
Posts: 10336
Hibernate Eclipse IDE Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Its a technique you can use on agile projects, though you don't have to for the project to use an agile approach.
 
Ronnie Phelps
Ranch Hand
Posts: 329
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
That is kind of confusing. What makes a project agile?
 
author
Posts: 799
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
See http://agilemanifesto.org for starters; make sure you read the principles.
 
author
Posts: 14112
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Not everyone would agree that XP is a methodology. But it very certainly is part of whatever constitutes "Agile Software Development".
 
Ilja Preuss
author
Posts: 14112
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Jeff Langr wrote:See http://agilemanifesto.org for starters; make sure you read the principles.



And the history!
 
Ronnie Phelps
Ranch Hand
Posts: 329
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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
Posts: 799
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

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
 
Put the moon back where you found it! We need it for tides and poetry and stuff. Like this tiny ad:
professionally read, modify and write PDF files from Java
https://products.aspose.com/pdf/java
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!