AGILE
Paul Wilson - NewContext
  http://newcontext.com
Royce, Winston (1970), "Managing the Development of
    Large Software Systems", Proceedings of IEEE
            WESCON 26 (August): 1–9
MANIFESTO
UNCOVERING AND DOING
VALUE
MONEY
AGILE METHODOLOGIES




           Photo by mseckington - http://flic.kr/p/7VwJUz
SCRUM
Defensive




       Photo by David Spender - http://flic.kr/p/4sFDj2
Scrum - Team isolation




      http://www.flickr.com/photos/cali4niadreamn/2362956348/
Scrum Master
EXTREME PROGRAMMING
INCLUDES TECHNICAL
     PRACTICES
BOEHM’S COST OF CHANGE
BECK’S COST OF CHANGE
TECHNICAL DEBT
ITERATIONS
POTENTIALLY SHIPPABLE
ACTIVITY/THEME PRIORITIES


• Necessity

• Flexibility

• Safety

• Luxury
RHYTHM
LIMITS WORK IN PROGRESS
KANBAN - ALTERNATIVE




              Photo by alq666 - http://flic.kr/p/67X96H
INVENTORY IS WASTE




          Photo by (nutmeg) - http://flic.kr/p/4zwxnT
CONTROL
MAKE THINGS VISIBLE
RELEASE BURN-DOWN
RELEASE BURN-UP
COMMUNICATION
Lord Raglan wishes the cavalry
to advance rapidly to the front,
 follow the enemy, and try to
  prevent the enemy carrying
        away the guns.
As Army Commander, Lord
 Raglan wants the cavalry to
 engage the enemy that have
   captured the redoubt on
 Causeway Heights so that
the the naval guns will not be
  carried away by the enemy.
As Army Commander, Lord
 Raglan wants the cavalry to
 engage the enemy that have
   captured the redoubt on
 Causeway Heights so that
the the naval guns will not be
  carried away by the enemy.
ACCEPTANCE CRITERIA
•Guns  from Causeway Height remain
in Allied control
•Enemy that captured Causeway
Heights is harried
•Light   Brigade is not destroyed

Iiba

Editor's Notes

  • #2 \n
  • #3 \n
  • #4 \n
  • #5 \n
  • #6 Uncovering, not found the answer to everything\nDoing - not thinking about and writing papers\n
  • #7 Highest priority to deliver value. In other words....\n
  • #8 It’s all about the money. If it doesn’t make money in some way, why do it?\n
  • #9 \n
  • #10 Scrum process - \n
  • #11 \n
  • #12 \n
  • #13 \n
  • #14 Technical and Planning practices. Whole team.\n
  • #15 \n
  • #16 \n
  • #17 \n
  • #18 Bad technical practices lead to fragile hard to change code - analogy technical debt\n\n\n
  • #19 Scrum process - \n
  • #20 \n
  • #21 \n
  • #22 \n
  • #23 \n
  • #24 \n
  • #25 \n
  • #26 \n
  • #27 \n
  • #28 Burndown\n
  • #29 \n
  • #30 \n
  • #31 Ambiguous order. Lord Raglan wanted the cavalry to prevent the Russians from carrying away guns from a captured redoubt, not charge entrenched artillery.\n
  • #32 \n
  • #33 \n