2010-11

Q1 a)
- XP values simplicity, feedback, courage, communication, 

respect
- Simplicity leads to smaller steps in planning
- XP does not throw away planning; approach is different
- because traditional planning is not flexible and prone 

to issues: unable to adapt to changing business reqs
- Planning is done iteratively, constantly testing and 

reviewing code written before updating plans
- Customer involvement; discussions improve feature plans 

and minimise wasting effort, code, and code issues
- If no planning, then more likely to have issues such as 

antipatterns or common avoidable mistakes.
- Agile manifesto are a bunch of points indicating 

preference for items on the left side, but does not mean 

that agile processes such as XP do not value the items to 

the right: "Responding to change over a plan"
- Obsolete implies agile only has improved properties in 

comparison to plan-driven methodologies, but agile is:
  Not able deal with unforeseen situations e.g. business
  Heavily customer involving; not always possible
  CRACK also not always possible
    Collaborative
    Representative
    Authority
    Committed
    Knowledgeable
  Plan-driven more likely to get CRACK customer, albeit 

for shorter periods of time than another employee from the 

customer's company. But might be worth it? 
-