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 Methodologies'?

'Principle of Least Astonishment' or 'Rule of minimum surprise' asserts that the system will cause the least surprise for the user by being as consistent and predictable as possible, and therefore usable. Which imply that in case of an ambiguity or a conflict in the system, the behavior of the system should be the one which will least surprise the user. In computer science, this principle has a wide range of application in topics such as user-interface design, programming language design, and programming. This principle is used in various disciplines as well as computer science such as engineering, science, and philosophy which are covered later in this wiki. After this brief information about the principle of least astonishment, now we are going to talk more about the sources found online about this topic and how well they explore the topic.

Arguments *Against* Agile Methodologies

lack of structure and necessary documentation only works with senior-level developers incorporates insufficient software design requires too much cultural change to adopt can lead to more difficult contractual negotiations

• "Towards Extreme(ly) Usable Software"
  

• "Extreme Programming Refactored: The Case Against XP "
  
• "Questioning Extreme Programming"
  
• "The Agile Method and Other Fairly Tales", *.PDF
  
• "Opinion: Extreme Programming Is Evil"
  
• Extreme Programming vs. Interaction Design"
  
• "The Case Against Extreme Programming"
  
• "Xp Critique"
  
• "The Case Against Extreme Programming"
  

Arguments *Support* Agile Methodologies

"Are agile methods good for design?" is a blog of an instructor, Alex Bunardzic, where he shares his in class experience when he was teaching Principle of Least Astonishment. The example that he gave in class is the Ruby on Rails code where he suggests using <%yield%> instead of <%content_for_layout%> to demonstrate this principle. This web page is not a good start to learn the topic, but it gives the idea of the principle and it demonstrates it with the Ruby on Rails code which is very related to what we have been doing in our class.

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"
  

Agile Methodologies in Other Disciplines

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"
  

Conclusion

This wiki is intended to be a Guide for Principle of Least Astonishment. It provides many links to online sources that explains the topic simply with easy-to-understand examples, and/or gives an idea where this principle can be used in real-life. These links should be helpful for the ones who want to learn more on this topic or understand the topic in more detail.

This principle can be used in many different disciplines for a universal useful solution for good designs. But it should be taken into consideration that the principle goes parallel with common sense, although it may not go with the convention.

"Who Stole Agile?"

External Links by Side

Against

• "Kevin Brady Blog" from The Art of Unix Programming by E.S. Raymond
• "Wikipedia"
• "Confessions of a Coder"

With

• "Site finding system faces suspension"
• "Applying the Rule of Least Surprise in webpages"

External Links by Methodology

XP

• "XP over Eclipse"