Extreme Programming Vs. BDUF
-
Guys, How many of you follow Extreme Programming? Do you believe Big Design Up Front is not necesssary while developing a good quality software? How much importance do you give in Designing? I work in a small team of 10 developers and we always have hot debate on whether to follow XP style of programming or not? milan c gurung satan
-
Guys, How many of you follow Extreme Programming? Do you believe Big Design Up Front is not necesssary while developing a good quality software? How much importance do you give in Designing? I work in a small team of 10 developers and we always have hot debate on whether to follow XP style of programming or not? milan c gurung satan
follow the xp style make users quickly familiar with your software but without personal character, however if not,there would be opposition; so as i think,if your softs have great users ,please think about the users' convenience firstly, to the reverse,you want to stand out of others ,try some other style maybe work. 路漫漫其修远兮，吾将上下而求索。
-
Guys, How many of you follow Extreme Programming? Do you believe Big Design Up Front is not necesssary while developing a good quality software? How much importance do you give in Designing? I work in a small team of 10 developers and we always have hot debate on whether to follow XP style of programming or not? milan c gurung satan
Personally I think XP is a fad and a waste of resources for the most part. I just can't see how two people working together at a computer are going to write a better designed program than one that the whole team has worked through in advance. XP has some good points, but I definitely vote for big design up front.
"A preoccupation with the next world pretty clearly signals an inability to cope credibly with this one."
-
Guys, How many of you follow Extreme Programming? Do you believe Big Design Up Front is not necesssary while developing a good quality software? How much importance do you give in Designing? I work in a small team of 10 developers and we always have hot debate on whether to follow XP style of programming or not? milan c gurung satan
See what you think of this... http://www.eiffel.com/general/monthly_column/2004/september.html[^] Kevin
-
Guys, How many of you follow Extreme Programming? Do you believe Big Design Up Front is not necesssary while developing a good quality software? How much importance do you give in Designing? I work in a small team of 10 developers and we always have hot debate on whether to follow XP style of programming or not? milan c gurung satan
In my experience it has depended greatly on the nature of the project. If you're developing a system that has an easily quantifiable end result -- an interface to a piece of hardware, for instance -- then the BDUF method not only works very well, but is usually necessary. On the other hand, if you're developing a system to automate a user-driven process, one of the rapid iterative methods would be a better fit. In a nutshell: requirements set in (relative) stone? BDUF all the way. Requirements coming from a committee of insurance claims adjusters? Prepare to iterate your way to (their) happiness. --Vincent
-
Guys, How many of you follow Extreme Programming? Do you believe Big Design Up Front is not necesssary while developing a good quality software? How much importance do you give in Designing? I work in a small team of 10 developers and we always have hot debate on whether to follow XP style of programming or not? milan c gurung satan
There are a couple of good points with XP. I think relentlessly writing unit tests for your code is most of the benefit provided by XP. The other really effective practice is the daily SCRUM type meeting. Even if nothing is discussed in most of these, they are effective at keeping people focused on the current task, and helping the right level of communication happen. Now, your question to design or not to design. I've been on projects killed by setting the wrong requirements in stone and struggled through constant change of a chaotic process. The best experience I've had is when there has been good communication between the customer and the development team. This has happened both with the waterfall approach and with the XP style, but I've found the XP style to be effective in more cases, both are better then chaos though. Design is part of that, since you can't do BDUF without settting requirements in stone.
-
Guys, How many of you follow Extreme Programming? Do you believe Big Design Up Front is not necesssary while developing a good quality software? How much importance do you give in Designing? I work in a small team of 10 developers and we always have hot debate on whether to follow XP style of programming or not? milan c gurung satan
One of the misunderstandings of agile methodologies is that there is no design or planning. I don't use XP, but I do use a mongrel of my own creation which borrows from Scrum, XP and Crystal. Instead of a massive requirements document, I write a feature list. I only work on a few features at a time (in 2 week iterations) and work with the user on getting that feature fully documented. Instead of an out of date requirements doc, I have a list of features with all the current information known about it. The user gets working software every 2 weeks to test and make sure it fits what they want. I've worked on too many projects that you spend a month writing a requirements document that the user agrees to, then you go off and write code for 6 months and when you deliver it, the user says "I didn't know it was going to work this way, it would be better if it did something else." Non-technical people can't visualize the way software is going to work based on UML and a Word document. They need to interact with the software. Agile allows me to adapt to my users' needs. My situation may be different from yours. I do not work in the software industry. I work for an engineering company. I design business apps for them to use internally. In a shrinkwrap software business, it may make more sense to design more up front. For me, I can walk down the hall and talk to my users face to face (not all of them, we have multiple offices). I think the key is that with BDUF, you get overcommitted to your code because it takes so long to get it in front of the user. Using short iterations, you never get overcommitted. Just my $0.02 Jeff Martin My Blog