Your SlideShare is downloading. ×
Introduction to agile
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.


Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Introduction to agile


Published on

Slide deck that I've used in many presentations for undergrad students.

Slide deck that I've used in many presentations for undergrad students.

Published in: Technology

  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. Introduction to AgilePresented by Juan Banda
  • 2. Roots of Scrum•Jeff Sutherland read apaper about the ToyotaProduction Model thatdeeply influenced histhinking•Ken Schwaber had beenapplying iterative andincremental developmentfor years•The two met and wrote apaper that they presentedback on 1996•Mike Beedle joinedSchwaber and togetherthey wrote a magnificentbook that started the wholething 2
  • 3. Agile Manifesto Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan 3
  • 4. Principles of Agile andScrumWhat is Scrum? •Not a methodology •Not a defined process •Not a set of procedures 4
  • 5. What is not ScrumScrum is not just this Neither just this 5
  • 6. But then, what is it?•Scrum is an opendevelopmentframework with asimple set of rules•Simple rules helpthe team to self-organize•Scrum is somethingthat generates atangible thing “thepotential shippableproduct” 6
  • 7. Scrum is not easy• When you walk into thedojo, the Sensei owns themat•You do exactly what hedoes, over and overagain, until it is part ofmuscle memory• Only when you havedemonstrated mastery ofthe basic practices are youallowed to improvise• Before you have gaineddiscipline, centering andflexibility, you are a hazardto yourself and others 7
  • 8. Not easy at all•Aikido is a martialart unlike any otherThere is nocompetition, sinceeach participantshould be awinner. It is an artthat takes alifetime to learn•Do you see anysimilarities withScrum? 8
  • 9. Simple framework•Scrum uses a very fewconcepts grouped inroles, ceremonies andartifacts•Scrum has to be lightby definition•Light means simple butnot necessarily easy toadopt and follow, evensimple things requiresdisciple•Aikido has twenty basictechniques thatcombined can generatehundreds of variations 9
  • 10. Why Scrum can bedifficult?What type of work do•you prefer?•A and C areopposites types ofwork that representisolation or chaoticwork•Scrum recommendsto try to havesomething like Type Band that can bedifficult to achieve ifiterations are notproperly timeboxed 10
  • 11. Prepare yourself forScrum•Read as much asyou can, practiceeven more•Always look at yourwork with a critic eye•Believe in improvingthings•Share your thoughtsand participate indiscussion groups•Be flexible•Fight your ego 11
  • 12. Relationship with XP•Extreme Programming is aset of principles andpractices created byprogrammers forprogrammers•“If something is good, moreof the same make it evenbetter” this defines the verycore of XP•Note that Scrum can beextended to other domainsthat has nothing to do withsoftware development, inthis sense Scrum can beconsidered more flexibleand less attached to coding 12
  • 13. Thanks for attending