tags:

views:

129

answers:

4

as now a days the main focus of software developers is to deliver the functionality upto the satisfaction of the customer in very much short time that requires a short but hybrid team well communication between them and also parallel working on different phases of development.,

after focusing all of this is Agile the best practice or any other can be more effective???

+4  A: 

I don't know about you, but I wouldn't be terribly keen on the idea of fly-by-wire systems for aircraft and other safety critical things being developed using agile methodologies.

Balancing Agility and Discipline: A Guide for the Perplexed is a good reference for a broader discussion on the subject.

awoodland
ok i know no one can ans 100% to this question but the experience can be shared here.....
moon
Agile does not mean undisciplined, it is basically that you build in short steps and always strive to have a working prototype after each step to test and show, even if it is missing functionality or layout. But there is many more methods gathered under the agile description.
David Mårtensson
you r right as i know about Agile it is all about the customer need centered working that is development and documentation, or do what is asked what is needed the leave the time and resource wasting practicing is it right or i miss something here?
moon
+12  A: 

There's almost never a single best answer. Each solution has its strengths and weaknesses. You just have to choose the right tool for the job.

Vilx-
ok its true but every one have some experience in this field can you ans in light of ur experience which one in most suitable in most cases
moon
+7  A: 

The best practice is the right balance giving you full confidence and control of what is going on and is being delivered as the result of the team's work. The strong bias towards any pole is a sign of management unprofessionalism.

Addition (all IMHO, subjective): The interesting phenomenon is Scrum (similar practices were successfully employed in engineering companies in Soviet Union), a "pseudo-agile" approach, where the work is partitioned into a small "micro-agile" blocks but the sizes of blocks are so small and the progress is monitored so strictly that the resulting quality can be quite close to the one when the strict approach is used. In fact, with properly tuned "micro-agile" granularity individual contributors get the full illusion of the freedom (well, freedom indeed) in decision making while the team performance and stays under full control and is well manageble.

bobah
ok it nice but my question is which existing practice will cover ur ans as the best
moon
@moon - as also pointed to by others, the right answer is different in any different situation. If you want specific answers, change the question and give more details. In general words, if the benefits from employing the certain level of agility in management minus support cost increase (including profit loss from potential incidents) is still worth it - go ahead with this level, otherwise decrease it to get to the optimum. And always use measurable indicators.
bobah
ok its good thanx for discussion
moon
+1 for "the right answer is different in any different situation". The bitter truth.
sjt
+2  A: 

Short answer: no. I find that a lot of Agile trainers have never actually coded themselves!

jambox
it is not necessary that a coder can make a good product the necessary is how do a coder can work with the team in best way.
moon
Agile is a collection of several methods, and you should always take care to only implement that which suits your team. Many trainers make money out of teaching, not programing and might have a different goal. Make sure you read up on Agile first and then if needed get someone to teach just that which you like to use. Its not set in stone that you SHOULD use all, rather the opposite ;)
David Mårtensson