CSC/ECE 517 Fall 2007/wiki3 10 tm

The Agile debate. Perhaps the most prominent controversy in o-o design today is whether it is possible to do a robust design with as little advance planning as agile methodologies recommend. Research this issue, on the Web and in the ACM DL, and report (fairly) on the major arguments of both sides, and on the evidence for both positions.

What is 'Agile Methodology'?

Agile Methodology was introduced as an iterative approach for developing software as a counter to waterfall approach. Where the five main phases of waterfall (requirement, design, codeing, integration, testing) are practiced through every iteration. Moreover, it put more practices in term of coding and testing, such as: Test drivin design; Unit testing; Refactoring; Pair programming; Collective ownership; Simple design; Metaphor; Continuous integration; and Customer access.
Many Agile methodologies were introduced in the last decade (XP, Scrum, DSDM, FDD, Lean, Adaptive, Crystal). It would be difficult to introduce every aspect of these methodology in this wiki. That is why, This wiki will concentrate in the most popular methodology XP (Extreme Programming).

Comparison Basis for Robust Design

A comparison between Agile methodologies and Waterfall methodology is found to be a little out of scope, as it is already recognized the advantages of iterative methodologies to capture the requirement and generate better softwares. That is why the current wiki will concentrate to compare with other iterative methods, such as RUP (Rational Unified Process). RUP share many of Agile's practices such as Unit testing, Metaphor, and Continuous integration. There is no depate about the benefits of previous practices for design, proparely that is why it is included in most of new processes. Other practices such as Simple design, Collective ownership, Pair programming, and Refactoring which represent a minor practices in XP, although can be immegrated to RUP is discussed. While, other features that are unique in XP as Customer access, early coding and simple design and refactoring is disscussed more.
In the current wiki we will try to test the Agile Manifesto and its related practices relative to design quality. These found to be the best basis as it provide the basis Agile methodologies trying to establish over other iterative methods.

Individuals and Interactions Over processes and tools

Requires too much cultural change to adopt
Only works with senior-level developers

Working software Over comprehensive documentation

Lack of structure and necessary documentation

Customer collaboration Over contract negotiation

Can lead to more difficult contractual negotiations

Responding to change Over following a plan

Incorporates insufficient software design

Agile Methodologies' Values

Previous practices were introduced to achieve certain values (Communication, Feedback, Courage, Simplicity, Respect). It is true that these practices will help to provide the best environement for these values to exist. Neverthless, many of these practices acquire the existance of these values in the project, the company, the manegment, the individuals, and moreover the customer. Certain enough these values represent a moral and professional values that should exist in every social and individual system, neverthless we recognize there variation in every system. Moreover, many of these values might be out of the control as simplicity of the project or the courage of the customer. The author think that is why Agile approach will give even a better results in different area such as R&D or education, where these values exist.

Conclusion

Agile methodologies provided a framework for software development. Certain enough these methodology not for every project, person or company. It will be great if you can apply these practices and gain these values. But if you cant still Agile methodology provide you with a lot of useful tools, you can pick and match what is suitable for your comapny, project, and personality.

Agile is not a religion and nor a trademark, it is the common and old practices of software development that is gathered so everone can work with it. But if you didn't practise it right it will end up by a loose software and development environement. So luky you if you can apply it all, but if you cant more effort in process, documentation, early design will be helpful to get a robust design.

For further information, see "Who Stole Agile?".

External Links by Side

Arguments *Against* XP

• "Extreme Programming Refactored: The Case Against XP "
  
• "Questioning Extreme Programming"
  
• "Extreme Programming vs. Interaction Design"
  
• "Towards Extreme(ly) Usable Software"
  
• "The Case Against Extreme Programming"
  
• "The Agile Method and Other Fairly Tales", *.PDF
  
• "Kevin Brady Blog"
• "Opinion: Extreme Programming Is Evil"
  
• "Xp Critique"
  
• "The Case Against Extreme Programming"
  

Arguments *Support* XP

• "Are agile methods good for design?"
  

Success Stories

• "Breaking the Ice for Agile Development of Embedded Software: An Industry Experience Report"
  
• "Agile enterprise software development using domain-driven design and test first"
  

External Links by Field

Programming

• "XP over Eclipse"
• "Agile Web Development with Rails"

Education

• "Extreme Learning"
• "A cross-program investigation of students' perceptions of agile methods"
• "eXtreme Programming at universities: an educational perspective"
  

Project Manegment

• "Developments in Agile Project Management"

R&D

• "agile practices for R&D projects"