Saturday, January 22, 2011

Extreme Programming Ch 1-3 and Design of Future Things Ch 1

Extreme Programming Installed
By: Ron Jeffries; Ann Anderson; Chet Hendrickson
Publisher: Addison-Wesley Professional
Pub. Date: October 16, 2000

Chapter 1 discusses the role of the customer, the programmer, and the manager.

Customer:
Defines the business value, is on site to communicate with the programmers throughout the entire project and is always available (preferably on-site), defines the tests and requirements that are reflected in "user stories."

Programmer:
Programmers write code in pairs to reduce errors and to always have help. Extreme programming also advocates iterative development where code is released in functioning implements with value added at each iteration. To ensure code quality, refactoring and unit testing is encouraged. Programmers are to stay in constant communication with the customer.

Manager:
Removes obstacles that the programmers might encounter, schedules regular meeting and encourages communication. The manager isn't directly involved in the development but makes the day-to-day operation easier by managing the team's disagreements, giving rewards, coordinating, and reporting.

Chapter 1 also lists manager and customer rights and programmer rights:
Manager and Customer Rights

1. You have the right to an overall plan, to know what can be accomplished, when, and at what cost.
2. You have the right to get the most value out of every programming week.
3. You have the right to see progress in a running system, proven to work by passing repeatable tests that you specify.
4. You have the right to change your mind, to substitute functionality, and to change priorities without paying exorbitant costs.
5. You have the right to be informed of schedule changes, in time to choose how to reduce scope to restore the original date. You can cancel at any time and be left with a useful working system reflecting investment to date.

Programmer Rights

1. You have the right to know what is needed, with clear declarations of priority.
2. You have the right to produce quality work at all times.
3. You have the right to ask for and receive help from peers, superiors, and customers.
4. You have the right to make and update your own estimates.
5. You have the right to accept your responsibilities instead of having them assigned to you.

Chapter 2:
Included a diagram showing customer and programmer communication. It illustrated how extreme programming emphasizes customer/programmer communication and allowed the customer to evaluate the amount of value added in certain features as well as allow the programmer to make good estimates of the time needed to implement those features.

Chapter 3:
This chapter expounds on the benefits of having an on-site customer; namely, that communication will be clearer and more concise than it would be if communication only occurred through e-mail or other slower less expressive forms of communication. This clarity keeps programmers from guessing on potentially important details or switching to work on less important parts of the program. Overall, on-site communication results in a product that the customer will be happier with.

Design of Future Things:
By: Donald Norman
Publisher: New York Basic Book
Pub. Date: November 2007

Chapter 1: Cautious Cars and Cantankerous Kitchens
In this Chapter, Norman expresses his reservations and observations about intelligent or "smart" systems in a number of settings. Norman complains that smart systems don't actually communicate or listen to the user, but rather claims that they condescendingly tell the user through "recommendations" that tend to quite poor. Norman also notes that the machines aren't actually intelligent but that the intelligence is "in the heads of the designers. So when the unexpected happens, the designer isn't there to help out, so the machine usually fails."

Norman cites that what humans can do easily, machines struggle with. For example, machines don't understand their surroundings or the context of their environment. Machines don't communicate, have social knowledge, or empathize with others. (He gives an example of a self driving car that pulls in front of other drivers and slams on the brakes.) On the other hand, machines are able to "think" much faster than their human counterparts. Norman says that human-machine interaction should complement each other and be "synergistic."


Discussion:
The chapters in extreme programming were very terse and extremely cut-and-dry. I've heard of and even used extreme programming principles in my programming studio class and I like the recommendations it makes for programmers. Particularly, I'm a fan of pair programming since tiny bugs are caught and logic errors are found before they become too embedded in the structure of the code. Having the customer on site is a difficult proposition for most real life scenarios, so I think XP's credibility is damaged by their zealous advocacy of it.




The first chapter of "The Design of Future Things" is an interesting introduction that focuses the reader on how intelligent systems can go wrong and raises fears and suspicions about the direction of modern technological development. Primarily, the idea of having haughty and downright annoying applications constantly buzzing recommendations, helpful or otherwise, sounds undesirable. Perhaps Norman's observations will inspire future designers to keep smart systems behind the scenes will still being useful agents. I think that kind of concealing of actions would go a long ways toward the "symbiotic" relationship J.C.R Licklider advocated. Imbuing machines with emotional clues or reactions may be a huge step forward in CHI, but the implementation would require contextual awareness that I think is beyond current technology. (Although that shouldn't stop us from trying.)

No comments:

Post a Comment