Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Scrum way the way


Published on

This is an introductory presentation on Agile and Scrum that was presented at Maranatha Christian University on December 2nd 2011

Published in: Business, Technology

Scrum way the way

  1. 1. Scrum Way, the way <ul><li>@jpartogi </li></ul><ul><li> </li></ul>
  2. 2. Human knot game <ul><li>Bentuk tim beranggotakan 5-7 orang </li></ul><ul><li>Bentuk formasi lingkaran dan dempetkan antar bahu </li></ul><ul><li>Angkat tangan kanan dan pegang tangan kanan orang lain </li></ul><ul><li>Angkat tangan kiri dan pegang tangan kanan orang yang berbeda </li></ul><ul><li>Bentuk lingkaran dengan formasi saling bergandengan tanpa ada pegangan yang lepas </li></ul>
  3. 3. Sosiogram <ul><li>Siapa yang sudah pernah mendengar Scrum? </li></ul><ul><li>Apa yang anda ketahui tentang Scrum sejauh ini? </li></ul>
  4. 4. How we got here <ul><li>Frederick Taylor’s Scientific Management: </li></ul><ul><li>“ ... In the past, Man has been first. In the future, the system must be first ... the first object of any good system must be that of developing first-class men; and under systematic management the best man rises to the top more certainly and more rapidly than ever before” </li></ul>
  5. 5. <ul><li>Peter Drucker (1960): “ Knowledge workers is a new breed of employees who employ their knowledge and brainpower, instead of their hands, as a mean to income.” </li></ul>
  6. 6. Software Developer is a knowledge worker!
  7. 7. Base Waterfall model “ Managing the Development of Software Systems: Concepts and Techniques.” - Winston W. Royce
  8. 8. Waterfall model is “risky and invites failure” because it leaves testing until the end - Dr. Winston W. Royce Dr. Winston W. Royce
  9. 9. Modified Waterfall model
  10. 10. If only it is this simple...
  11. 11. Kategorisasi Proyek Jauh dari kepastian Dekat dengan kepastian Dekat dengan persetujuan Jauh dari persetujuan Sederhana Kompleks Sulit Anarkis Sulit Requirement Teknologi
  12. 12. The origins of Agile <ul><li>NASA dan Department of Defense (DoD) telah menggunakan Iterative and Incremental Development (IID) sejak tahun 1950. </li></ul>
  13. 13. Iterative and Incremental Development <ul><li>Pendekatan untuk membangun sebuah sistem yang dicerminkan lewat eksekusi beberapa putaran secara beruntun dimana setiap putaran merupakan sebuah rilis dari rangkaian fitur. </li></ul>
  14. 14. Evolutionary Project Management (Evo) <ul><li>Thomas Gilb pada tahun 1960 mengkonseptualisasikan Evo yang menekankan pembuatan software secara sepotong setiap 2-4 minggu sekali guna mendapatkan nilai bisnis secara maksimal yang ke depannya mengevolusikan deliverable di masa mendatang </li></ul>
  15. 15. New new Product Development Game “ The New New Product Development Game” - Hirotaka Takeuchi and Ikujiro Nonaka (1986)
  16. 16. Agile Manifesto <ul><li>We are uncovering better ways of developing software by doing it and helping others do it. </li></ul><ul><li>Through this work we have come to value: </li></ul><ul><li>Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan </li></ul><ul><li>That is, while there is value in the items on the right, we value the items on the left more. </li></ul>
  17. 17. What is Agile? <ul><li>Agile is about people, employee and customer satisfaction, communication, working software, being flexible with change. </li></ul>
  18. 18. What is Agile? <ul><li>Agile is not just a set of process or tools, it’s a mindset to get things done and delight the customers. </li></ul>
  19. 19. What is Agile? <ul><li>Agile is a mindset, defined by values, guided by principles, expressed through practices. </li></ul>
  20. 20. The old way simply does not work!
  21. 21. Insanity: doing the same thing over and over again and expecting different results. - Albert Einstein Albert Einstein
  22. 22. Agile is hard to be done right because it involves a new way thinking
  23. 23. When you change the way you look at things, the things you look at change - Max Planck Max Planck
  24. 24. From holistic to empirical
  25. 25. It is a mistake to look too far ahead. Only one link in the chain of destiny can be handled at a time - Winston Churchill Winston Churchill
  26. 26. From command & control to facilitate & empower
  27. 27. Never tell people how to do things. Tell them what to do and they will surprise you with their ingenuity. - George S. Patton George S. Patton
  28. 28. From hierarchies of individuals to team
  29. 29. The modern organization cannot be an organization of “boss” and “subordinate”: it must be organized as a team of “associates” - Peter Drucker Peter Drucker
  30. 30. From process first to people first
  31. 31. Why not make the work easier and more interesting so that people do not have to sweat? The Toyota style is not to create results by working hard. It is a system that says there is no limit to people's creativity. People don't go to Toyota to 'work' they go there to 'think' - Taiichi Ono Taiichi Ono
  32. 32. From human resources to people
  33. 33. I think management is about just that - managing people via man-to-man skills. - Stuart Pearce Stuart Pearce
  34. 34. From one way that works to continuous improvement
  35. 35. Excellent firms don’t believe in excellence – only in constant improvement and constant change. - Tom Peters Tom Peters
  36. 36. From plan driven to value driven
  37. 37. All we are doing is looking at the time line, from the moment the customer gives us an order to the point when we collect the cash. And we are reducing the time line by reducing the non-value adding wastes. - Taiichi Ono Taiichi Ono
  38. 38. Agile’s flavour <ul><li>eXtreme Programming </li></ul><ul><li>Feature Driven Development </li></ul><ul><li>Dynamic Systems Development Method </li></ul><ul><li>Lean Software Development </li></ul><ul><li>Crystal Clear </li></ul><ul><li>Scrum </li></ul>
  39. 39. 85% of Agile companies use Scrum
  40. 40. Why Scrum <ul><li>Scrum is very simple </li></ul><ul><li>Scrum can run with existing engineering practices </li></ul><ul><li>Scrum is generic - it can run in non-IT organization </li></ul><ul><li>Scrum will tell you how to do Agile </li></ul>
  41. 41. Scrum is used for complex work in which it is impossible to predict everything that will occur - Ken Schwabber Ken Schwabber
  42. 42. Complexity & Unpredictability = Traffic Jam in Jakarta
  43. 44. Product increment ibarat Sashimi, dimana setiap potongan adalah potongan yang komplit dan dapat berdiri sendiri
  44. 45. Sprint ibarat lampu depan mobil, dimana ia hanya menyorot ke depan agar resiko dapat dikendalikan Sprint
  45. 46. <ul><li>Tidak boleh ada penambahan Product Backlog ke dalam Sprint selama Sprint sedang berlangsung selain oleh anggota Tim Pengembang </li></ul><ul><li>Product Backlog boleh dirubah dan ditambah oleh Pemilik Produk di luar Sprint tetapi bukan untuk dimasukkan ke dalam Sprint yang berjalan </li></ul>Sprint Perubahan
  46. 47. Scrum’s Roles <ul><li>Product Owner manages the Product </li></ul><ul><li>Scrum Master manages the Scrum process </li></ul><ul><li>Development Team manages itself to create the product </li></ul>
  47. 48. Scrum’s Roles <ul><li>Product Owner tells the team what to make (strategic) </li></ul><ul><li>Development Team manage the “how to” (tactic) </li></ul><ul><li>Scrum Master empowers the team and removes obstacles </li></ul>
  48. 49. Scrum’s Artefact <ul><li>Product Backlog is an ordered list of everything that might be needed in the product </li></ul><ul><li>Sprint Backlog is a selected Product Backlog items for the Sprint </li></ul>
  49. 50. Scrum’s Meetings <ul><li>In Sprint Planning the team plan what to do (Sprint Backlog) and how to do it </li></ul><ul><li>In Sprint Review the team demonstrate what they have done </li></ul><ul><li>In Sprint Retrospective the team discuss how they can improve for the next Sprint </li></ul>
  50. 51. Scrum’s Meetings <ul><li>What they have done yesterday </li></ul><ul><li>What they will do today </li></ul><ul><li>Obstacles that are on their way </li></ul>In Daily Standup Meeting the team tell the other team member three things:
  51. 52. Scrum’s Timeline Untuk Sprint yang jangka waktunya 1 bulan 8 hours 4 hours 3 hours <ul><li>Daily Scrum </li></ul>1 bulan Sprint Perencanaan Ulasan Refleksi Pengembangan
  52. 53. Scrum dan Startup We made a initial startup from idea - business plan - pitch in less than 2 days
  53. 54. Scrum in Startup <ul><li>There are so many uncertainty in a startup </li></ul><ul><li>On time and on budget is irrelevant in a startup </li></ul><ul><li>Big design upfront is irrelevant </li></ul><ul><li>Don’t build what the customer don’t want </li></ul>
  54. 55. Scrum in Startup company <ul><li>Prioritize - Build - Measure - Learn </li></ul><ul><li>Prioritize the most wanted features </li></ul><ul><li>Build and release every 2-4 weeks (release early, release often) </li></ul><ul><li>Gain feedback from customers and learn! </li></ul>
  55. 56. Scrum in Startup company Prioritize Build Release Measure & Learn 2-4 minggu
  56. 57. Banyak perusahaan di Indonesia yang telah dan akan beralih ke Scrum, apakah anda sudah siap?
  57. 58. Scrum is hard <ul><li>It requires new mindset! </li></ul><ul><li>Highly initiative and proactive developers </li></ul><ul><li>Cross-functional team </li></ul><ul><li>Serving and protective managers </li></ul><ul><li>Work is done in short iterations </li></ul><ul><li>Product ownership by customer </li></ul><ul><li>This will make many people uncomfortable </li></ul>
  58. 59. ScrumWay apprentice <ul><li>Guna akselerasi pemahaman Scrum dan mempersiapkan semakin banyak individu yang siap masuk dalam tim Scrum, ScrumWay mengajak mahasiswa yang ingin memahami Scrum untuk ikut program ScrumWay apprentice - </li></ul>
  59. 60. UK Maranatha dan ScrumWay bekerja-sama untuk mempersiapkan orang-orang yang memiliki mindset Scrum
  60. 61. Ide-ide penelitian Scrum <ul><li>Psikologi produktifitas pegawai dalam organisasi Scrum </li></ul><ul><li>Scrum dalam organisasi besar ( > 100 pegawai) </li></ul><ul><li>Scrum dalam organisasi multinasional </li></ul><ul><li>Scrum dalam perusahaan startup </li></ul><ul><li>Scrum dalam organisasi non-IT (contoh: event organizer, advertising, universitas) </li></ul>
  61. 62. Ide-ide penelitian Scrum <ul><li>Menggabungkan Scrum dengan proses lainnya (contoh: CMMI, PMBoK, ISO 9001) </li></ul><ul><li>Perbandingan antara organisasi yang menggunakan Scrum dan bukan: </li></ul><ul><ul><li>Kualitas produk </li></ul></ul><ul><ul><li>Return on investment </li></ul></ul><ul><ul><li>Kepuasan pegawai </li></ul></ul><ul><ul><li>Kepuasan pelanggan </li></ul></ul>
  62. 63. <ul><li>Scrum adalah sebuah pola pikir yang: </li></ul><ul><li>dijelaskan lewat nilai-nilai </li></ul><ul><li>diarahkan lewat prinsip-prinsip </li></ul><ul><li>dicerminkan lewat praktik-praktik </li></ul>Kesimpulan Scrum is a mindset, defined by values, guided by principles, expressed through practices.
  63. 64. Komunitas Scrum <ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul>
  64. 65. <ul><li> </li></ul><ul><li> </li></ul><ul><li>http://scrum.j </li></ul><ul><li>http://infoq. com/agile </li></ul><ul><li> </li></ul><ul><li> scrum-indonesia </li></ul>Narasumber
  65. 66. Terima Kasih