Introduction to agile presentation @AgileAdria 2013


Published on

Roko Roić

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

No notes for slide
  • It has been in the industry for 13years under that name and for around 18 under other predecesor names There are certification streams, alliances, conferences such as this one C ompanies focusing on coaching for it, representatives of some are here
  • Colleagues with experiences are around you Books are gallore Multi hundred million $ projects being done this way Locally and globally!
  • When you look around, this is not “ an alternative ” , this is mainstream There are more books and publications coming out on Agile methodologies than any other The adoption rate is larger than any other methodology Today you can not get any funding in silicone waley if you are not Agile
  • First car to be produced on the assembly line The price started with 850$ but dropped to 550$ due to the line becoming more efficient All parts were interchangeable It changed the automotive industryIt was so cheap that an assembly line worker could buy it with just 4 monthly pays This automated and streamlined process allowed Henry and his coworkers to think about optimization
  • Introduction to agile presentation @AgileAdria 2013

    1. 1. Introduction to AgileRoko Roić, Agile Adria 2013.Tweet @rroic, Mail, Visit
    2. 2. Agenda• Why are we here today• Principles of Agile thought• Highlighted ceremonies and artefacts• Enjoy the show
    3. 3. Why are we here todayAlso known as The History Of Agile and Lean
    4. 4. Why are we here today?there is a better wayBecauseto create products
    5. 5. Why are we here today?battle-testedIt has beenglobally and locally
    6. 6. Why are we here today?this way is already&mainstream
    7. 7. It all began in 2001. in a resort in UtahBUT WAIT!BUT LET’S GO BACKA BIT FURTHER
    8. 8. The year is now 1908.Ford producesModel T andfocuses oneliminatingwaste inproduction.Introduces JustIn Timepractice.Henry writes a book“Today and Tomorrow”
    9. 9. In come the Japanese. Time is just after WW2.ToyotaProductionSystem is born.The age of LeanManufacturinghas begun.Japanese read the book ;)Visit some supermarketsAnd start thinking...
    10. 10. Key Concepts of the Toyota Production System• Kiichiro Toyoda names JIT,a principle based on USAsupermarkets and Ford• In 1950. Kanban isintroduced as a visual aid• Continuous Improvementand Kaizen are at the core• Eliminating Waste inproduction is at the core
    11. 11. Timeline of what is to become “Lean”• 1973. first internal manual describes TPS• 1977. first english article on TPS• 1979. MIT starts investigating TPS• 1982. TPS first translated to English• 1983. Toyota and GM implement TPS for the 1st time out ofJapan• 1987. Term “Lean” coined to explain the underlying principles ofTPSAnd then again,some books got written
    12. 12. Lean is born and we are back from JapanAnd how is this connected to Agile?Lean and Agile share ideas
    13. 13. And how did Agile come to this world?Method Born ParentsDSDM 1994. ConsortiumScrum 1995.Sutherland&SchwaberASD 1999. HighsmithXP 1999. Kent• The world was desperate onfinding a better way tocreate software• Many lightweightmethodologies emerged asa response to “not so good”waterfall principles• Influenced in part by Lean• Shared many underlyingprinciplesBack to Utah, 2001.
    14. 14. The Agile Manifesto, Utah 2001.
    15. 15. Principles of Agile thoughtWhat is under the hood
    16. 16. The manifestoWe are uncovering better ways of developing software by doing it andhelping others do it. Through this work we have come to value:•Individuals and interactions over processes and tools•Working software over comprehensive documentation•Customer collaboration over contract negotiation•Responding to change over following a planThat is, while there is value in the items on the right, we value the itemson the left more.
    17. 17. • Our highest priority is to satisfy the customer through early andcontinuous delivery of valuable software.• Welcome changing requirements, even late in development. Agileprocesses harness change for the customers competitive advantage.• Deliver working software frequently, from a couple of weeks to a coupleof months, with a preference to the shorter timescale.• Business people and developers must work together daily throughoutthe project.• Build projects around motivated individuals. Give them theenvironment and support they need, and trust them to get the job done.• The most efficient and effective method of conveying information toand within a development team is face-to-face conversation.The 12 principles of the Manifesto
    18. 18. • Working software is the primary measure of progress.• Agile processes promote sustainable development. The sponsors,developers, and users should be able to maintain a constant paceindefinitely.• Continuous attention to technical excellence and good design enhancesagility.• Simplicity--the art of maximizing the amount of work not done--isessential.• The best architectures, requirements, and designs emerge from self-organizing teams.• At regular intervals, the team reflects on how to become more effective,then tunes and adjusts its behavior accordingly.The 12 principles of the ManifestoA new methodology?No, choose one!
    19. 19. • A common name for methodologiesfollowing the said principles. Mostpopular include Scrum, XP, DaD• They share many common practicesSo what IS agile then?And what it is NOT?
    20. 20. It does not mean lack of control
    21. 21. It does not (always) mean work faster
    22. 22. Highlighted ceremoniesand artefactsBy no means a comprehensive guide of practices
    23. 23. Scrum Ceremonies
    24. 24. Kanban board
    25. 25. User Story
    26. 26. Standup meeting
    27. 27. Enjoy the showHope I helped
    28. 28. • Focus on communicationwithin your projects• Try to look for anti patternsin your work• Agile can be appliedprinciple by principleThanks for listening• Implementation that fitsyou?• Just Kanban or the entireScrum ceremonies pack?–let continuousimprovement guide youstep by stepAgile is mainstreamAgile is lightweightThere is a better way