There is a difference. "Agile" is an property/adjective, describing how quickly something (a process in our case) can switch direction (adapt to new information). "Agile software development" (or agile methods, methodologies, etc.) is a category of software development methodologies with that (agile) property. XP is just one process that happens to belong under that category. There are others as well, but they don't get nearly as much mind-share as XP.I am a little bit confused if there is a difference between agile and XP. It appears that sometimes these terms are being used interchangeably.
Sure, but not any more than it is related to BDUF, waterfall, etc. processes. It's a tool for communication, documentation, and lately even code generation, and can be applied within a number of different types of processes.And is UML related to this as well?
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
<a href="http://www-306.ibm.com/software/rational/bios/ambler.html" target="_blank" rel="nofollow">Scott W. Ambler</a><br />Practice Leader Agile Development, IBM Rational<br /> <br />Now available: <a href="http://www.ambysoft.com/books/refactoringDatabases.html" target="_blank" rel="nofollow">Refactoring Databases: Evolutionary Database Design</a>
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
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
Originally posted by Garry Garrson:
Hi All,
Thanks for such an informative board.
I would appreciate it if my questions could be answered.
1.)if RUP is a process how does the differ from UML?
2.)I understand UML to be format use �use cases� but what else is it be used for today in the real world?
3.)if XP is a process like waterfall (in my limited experience) but �lighter� what ever that means (if I understand correctly it�s less burocratic) why does XP not seem to be main stream? Particularly in web based development where development cycles are fairly short 3~6 months max
4.)When would u use RUP instead of UML
5.)Does any main stream development shops (web based development) still use waterfall method? If not where is the trend moving?
6.)Who typically create the UML? Project manager?
7.) What currents process in active use (web based) besides XP for short term 3~6 months 6~10 developer Java teams?
I apologies in advance if any of my questions look silly.
Thanks for your time.
Gary
Originally posted by Warren Dew:
XP and other agile processes don't always handle product management well, because of the close link between the developers and the customer. I've seen this result in excessive repolishing of the work in early iterations, at the cost of never getting the rest of the features done.
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
Originally posted by Don Stadler:
xP project may also use UML if the customer demands formal design artifacts, although it's against the spirit of xP. I've seen them use UML after the coding was done to document the design.
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
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
Well, if you tailor RUP enough, you can end up with something that looks very close to XP-by-the-book. However, the typical RUP instances I've seen are most definitely not suitable for a small team. Heck, they haven't been too suitable for any team.Originally posted by Garry Garrson:
From what I have read RUP does seem quite detailed for small projects, Correct?
Originally posted by Garry Garrson:
I am a little confused are you saying that there is another process call "UP" (Unified Process, de-Rationalized) that is preferred in some cases? If so where could I read up on that? What are your thoughts on it?
Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Originally posted by Garry Garrson:
Question: From what I have read RUP does seem quite detailed for small projects, Correct?
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
Originally posted by Ilja Preuss:
Am I understanding you correctly that in your experience/opinion, removing the close communication between Customer and developers would help the developers to produce something closer to the Customer's needs, and therefore reduce the need for "excessive repolishing"?
Originally posted by Garry Garrson:
What is LDAP & Active Directory?
I am going to take a stab at my questions so as to help direct your answers if that makes any sense.
1.) What is Active Directory (is active directory the repository for user name, PWD other confidential information like access rights and what groups this user belongs to ? )
2.) What is LDAP (is L D A P - a standard if so, for what?)
3.) How do they relate to each other ?
If someone could help me understand these concepts (for the purpose of a single user sign on to more than one application from differnt vendors better I would much appreciate it.
From what I understand (although no experience so probably wrong) if an application (say one you built) needs to integrate to a third party application where both your application and the 3rd party require authentication each product must support LDAP . Where does Active Directory come into it? I guess there are different LDAP & Active Directory vendors?
Question: This probably sounds ridiculous but why could you not just use encrypted XML to get authenticated on the 3rd party application (to send user name & password)?
Originally posted by Don Stadler:
Or am I full of crap? You tell me!![]()
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
Originally posted by Ilja Preuss:
Well, you aren't!![]()
Still, even if the Product Manager was the Customer, I wouldn't want to put him *between* the developers and the actual customers/users of the system (at least a couple of them). He might have the final say, but I don't see why he'd need to "protect" the developers from knowing how the software actually will get used first hand.