Doddi Priyambodo - Scrum Day Asia 20121123 - AGILE SOFTWARE DEVELOPMENT LIFE CYCLE USING SCRUM

1. By : Doddi Priyambodo PT Indonesia Comnets Plus (http://www.iconpln.co.id) Presented at Universitas Maranatha, Bandung, Jawa Barat Bandung, November 24th 2012 How ICON+ implements Scrum + Minimizing Risk and Maximizing Business Value with continuous one-week delivery i-PANDAWA Framework http://i-pandawa.com

2. i-PANDAWA Agile Scrum Framework

3. - Private and Confidential - i-PANDAWA - Page 3The Premier Event for Software and Systems Innovation Topic of Presentations ► 1. Introduction : Who is ICON+ PLN ► 2. Introduction : Who am I ► 3. Changing to Agile Scrum Framework ► 4. What is i-PANDAWA Framework ► 5. Continuous One Week Delivery ► 5. Real Life Experience using Scrum ► 6. What has Changed Now ► 7. Testimonials

4. - Private and Confidential - i-PANDAWA - Page 4The Premier Event for Software and Systems Innovation I. WHO IS ICON+ PT. Indonesia Comnets Plus better known by its trade name of ICON+ was established on October 3rd, 2000, as a wholly-owned subsidiary of the state power utility company, PT PLN (PERSERO) INDONESIA. It positions to provide solution the state of the art telecommunication network and information technology demand in Indonesia

5. - Private and Confidential - i-PANDAWA - Page 5The Premier Event for Software and Systems Innovation ► Our product to provide solution to the customer is a synergy between IT, telco, IP network, engineering capabilities and high- end technologies. ► There are : • Fiber Optic Backbone (Sumatera, Jawa, Bali, Kalimantan, Sulawesi) • IP VPN Multi Protocol Label Switch (MPLS). • IP VSAT • ENTERPRISE DATA CENTER • IT Content Services :  AP2T (PLN Billing and Collection, CRM)  CONTACT CENTER 123, APKT  i-BBO, i-RIMA, i-CoalSys, etc • Other Services:  ICON+ private user-group telephony system (JWOT)  Multimedia and Video Conferencing System, etc continued…

6. - Private and Confidential - i-PANDAWA - Page 6The Premier Event for Software and Systems Innovation II. WHO AM I ► Name : DODDI PRIYAMBODO ► Info Detail : http://id.linkedin.com/pub/doddi-priyambodo/4/254/12b ► Experiences : ► Deputy Manager IT Enterprise Planning and Product Development, ICON+ ► Technology Leader Stream for AP2T Implementation in PLN Jawa Bali ► Solution Architect for AP2T (Software, Hardware, etc) ► Developer for Application Development i-Rev, i-IDA, etc ► Software Architect for PLN Payment Gateway, i-Pay, etc ► Project Manager for SIP3 Implementation and Operation at PLN KalTim, etc ► Oracle Database Administrator and System Administrator ► Software Developer (.NET, JAVA) for SIP3, SOPP, MGT, CIS

7. - Private and Confidential - i-PANDAWA - Page 7The Premier Event for Software and Systems Innovation III. Changing to Agile Scrum Framework ► We are Looking For : ► Simple Process and Easy to Adapt, but it must be a BEST PRACTICE and PROVEN Process! ► Make a Lot of Improvement Ideas from the Team ► Team must deliver the project on Schedule ► Minimize the Risk! ► Maximize the Business Value!

8. - Private and Confidential - i-PANDAWA - Page 8The Premier Event for Software and Systems Innovation The Manifesto for Agile Software Development ► We are uncovering better ways of developing software by doing it and helping 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 plan ► That is, while there is value in the items on the right, we value the items on the left more.

9. - Private and Confidential - i-PANDAWA - Page 9The Premier Event for Software and Systems Innovation ► AGILE SCRUM FRAMEWORK IS THE SOLUTION !

10. - Private and Confidential - i-PANDAWA - Page 10The Premier Event for Software and Systems Innovation Simple Process

11. - Private and Confidential - i-PANDAWA - Page 11The Premier Event for Software and Systems Innovation Simple Roles - PRODUCT OWNER - SCRUM MASTER - SCRUM TEAM picture by exfordy

12. - Private and Confidential - i-PANDAWA - Page 12The Premier Event for Software and Systems Innovation Product Owner Owner of project vision Represents the customerpicture by Official Star Wars Blog

13. - Private and Confidential - i-PANDAWA - Page 13The Premier Event for Software and Systems Innovation Product Owner Define features (according to vision) Prioritize features (according to ROI) Pick release dates Give feedback Manage stakeholders Accept or reject results

14. - Private and Confidential - i-PANDAWA - Page 14The Premier Event for Software and Systems Innovation Scrum Master Servant leader Team protector Troubleshooter Scrum guide picture by Orange Beard

15. - Private and Confidential - i-PANDAWA - Page 15The Premier Event for Software and Systems Innovation Scrum Master Remove impediments Prevent interruptions Facilitate the team Support the process Manage management

16. - Private and Confidential - i-PANDAWA - Page 16The Premier Event for Software and Systems Innovation The Team Small (5–9 people) Colocated - Cross-functional Self-organized - Full-timepicture by ewen and donabel

17. - Private and Confidential - i-PANDAWA - Page 17The Premier Event for Software and Systems Innovation The Team Define tasks Estimate effort Develop product Ensure quality Evolve processes

18. - Private and Confidential - i-PANDAWA - Page 18The Premier Event for Software and Systems Innovation Team Commitment!  TEAM DEFINE THEIR OWN RULES OF WORK  TEAM HAS THE FULL CONTROL OF WHAT THEY DO  TRANSPARANT  TEAM MUST COMMIT TO DELIVER  MAKE CONTINOUS IMPROVEMENT

19. - Private and Confidential - i-PANDAWA - Page 19The Premier Event for Software and Systems Innovation The Challenge! Looks Simple, But It Is Hard No Silver Bullet Need Process Takes Time picture by a2gemma

20. - Private and Confidential - i-PANDAWA - Page 20The Premier Event for Software and Systems Innovation IV. What is i-PANDAWA Framework ► 1. i-PANDAWA Framework DEFINITION ► 2. i-PANDAWA Motto and Way of Life ► 3. SDLC Methodology ► 4. How We Collaborate ► 5. Flow of Works and Standard Operating Procedure ► 6. i-PANDAWA Application Architecture

21. - Private and Confidential - i-PANDAWA - Page 21The Premier Event for Software and Systems Innovation i-PANDAWA FRAMEWORK DEFINITION What is i-PANDAWA i-PANDAWA is a framework that is initiated by Business Unit of ICTS ICON+, PLTI Division. This framework is designed for a baseline Standard that can be used for the daily activities by Planning and Product Development (PPD) Sub Division to make Innovations for the Company. Why we use i-PANDAWA i-PANDAWA is a standard way to create the Applications in sub division of Planning and Product Development. It is a standard way to manage the creation of new applications, and it has a standard platform of technology to create the new applications. Who use i-PANDAWA i-PANDAWA can be used by all of the teams in ICON+ to develop and deploy the new applications When we use i-PANDAWA i-PANDAWA is used in daily development process of creating new applications and maintain the existing applications How to use i-PANDAWA i-PANDAWA Framework has 2 big items, these 2 items are : - iPandawa Methodology of the Application Lifecycle Management – powered by SCRUM - iPandawa Platform of the Application Technology – powered by INNOVATION Definition of i-PANDAWA The letter "I" stands for the word INNOVATION, INNITIATIVE, ICTS (Information Computer Technology Solution), ICON+ (Indonesia Comnets Plus), and INDONESIA The word "PANDAWA" comes from the epic story of Mahabharata. Pandawa is the Family's name of five great persons (Yudhistira, Bima, Arjuna, Nakula, Sadewa). The value of this Pandawa family that can be used in this framework are "We are in This Together", "We Die Together, We Win Together". YES, that is our Methodology of Working in here. Motto of i-PANDAWA "We are in This Together. We Die Together, We Win Together!"

22. - Private and Confidential - i-PANDAWA - Page 22The Premier Event for Software and Systems Innovation i-PANDAWA FRAMEWORK iPandawa Methodology – Powered by SCRUM Our Motto: WE ARE IN THIS TOGETHER WE DIE TOGETHER! WE WIN TOGETHER !

23. - Private and Confidential - i-PANDAWA - Page 23The Premier Event for Software and Systems Innovation SDLC Methodology Application Lifecycle Management - iPandawa Methodology

24. - Private and Confidential - i-PANDAWA - Page 24The Premier Event for Software and Systems Innovation i-PANDAWA PRINCIPLES

25. - Private and Confidential - i-PANDAWA - Page 25The Premier Event for Software and Systems Innovation Remember : The Key of “Working Together” is : MAKE HIGH BANDWITH OF COMMUNICATION ! Permasalahan utama dari 80% semua masalah adalah = KOMUNIKASI, TRANSPARANSI

26. - Private and Confidential - i-PANDAWA - Page 26The Premier Event for Software and Systems Innovation COMMUNICATION TOOLS MICROSOFT SKYPE GROUP DROPBOX FILE SHARE

27. - Private and Confidential - i-PANDAWA - Page 27The Premier Event for Software and Systems Innovation COMMUNICATION TOOLS ► EVERNOTE ► WHATSAPP GROUP TEAMVIEWER

28. - Private and Confidential - i-PANDAWA - Page 28The Premier Event for Software and Systems Innovation Remember : GOOD PROCESS make GOOD AND CONSISTENT RESULT! Focus on People, and Framework that Empower and Protect People. Our Motto: WE ARE IN THIS TOGETHER WE DIE TOGETHER! WE WIN TOGETHER !

29. - Private and Confidential - i-PANDAWA - Page 29The Premier Event for Software and Systems Innovation MINIMIZING THE RISKS AND MAXIMIZING THE BUSINESS VALUES BY CONTINOUS ONE WEEK DELIVERY

30. - Private and Confidential - i-PANDAWA - Page 30The Premier Event for Software and Systems Innovation One Week Delivery?

31. - Private and Confidential - i-PANDAWA - Page 31The Premier Event for Software and Systems Innovation Why Frequent Delivery? ► #1 Deliver Business Value Faster  a lot of Versions ► #2 Fail Fast and Early to Minimize The Risks ► #3 Fail Small to Do the Fast Recovery ► #4 Deploying Often, Less Number of Defects ► #5 Maximizing Opportunity for Feedbacks ► #6 Satisfy the Customer with Frequent Delivery Notes : - Prepare your Rollback Plan - Prepare all the Logs - Transparent is very Important - Everything is under Source Control

32. - Private and Confidential - i-PANDAWA - Page 32The Premier Event for Software and Systems Innovation What is Frequent Delivery in ICON+? ► Is it always Deployed Weekly?  YES ► Continuous Delivery is about keeping your application in a state where it is always able to release. (Ready for Production!) ► Is it Un-Matured Software to Release?  NO ► Tester always Test Daily, if not they will complain at Standup Daily Meeting. And Developers also won’t like if the Tester doesn’t have anything to do at that day. ► The deployed items are the user stories that have reach the status of DONE

33. - Private and Confidential - i-PANDAWA - Page 33The Premier Event for Software and Systems Innovation Definition of Frequent Delivery ► Being “Production Ready” is not the same definition as “Releasing to the Users Massively with the Real Environments” ► The goal of the Development Team is to give the Product Owner the ability to release New Product Backlog Items whenever the Product Owner decides to. This means that the Product Owner might release every Product Backlog Item immediately, or he delays it until he gets feedback from another stakeholders or he aligns the release to external events (or specific dates)

34. - Private and Confidential - i-PANDAWA - Page 34The Premier Event for Software and Systems Innovation Versioning Convention ► Versioning Mechanism : ► ALPHA Finished Dev, Please Do the QA ► BETA Finished Test, Please Do the Beta Roll Out ► STABLE Finished Beta Test, it is creating money now! ► Versioning Mechanism, per-Phase Development ►  Maximize Business Values ►  Sprint and Process Transparency

35. - Private and Confidential - i-PANDAWA - Page 35The Premier Event for Software and Systems Innovation Infrastructure of Continuous Delivery ► Development Machine : only for developers ► QC VMachine : Ready for Test (Alpha) – internal ► Ready to Prod VMachine : Production Ready (Beta) – users ► Production Machine : Production (Stable) – users Dev + Tools Server Alpha and Beta Server Production Server

36. - Private and Confidential - i-PANDAWA - Page 36The Premier Event for Software and Systems Innovation SOP - Release Management : Approval Standard Operational Procedure - iPandawa Methodology

37. - Private and Confidential - i-PANDAWA - Page 37The Premier Event for Software and Systems Innovation IV. Real Life Experience using SCRUM ► How we Do Sprint Planning ► How we Do Sprint Daily Meeting ► How we Do Sprint Review ► How we Do Sprint Retrospective

38. - Private and Confidential - i-PANDAWA - Page 38The Premier Event for Software and Systems Innovation

40. - Private and Confidential - i-PANDAWA - Page 40The Premier Event for Software and Systems Innovation Online Scrum Board Standard Operational Procedure - iPandawa Methodology

41. - Private and Confidential - i-PANDAWA - Page 41The Premier Event for Software and Systems Innovation Online Scrum Board Standard Operational Procedure - iPandawa Methodology

42. - Private and Confidential - i-PANDAWA - Page 42The Premier Event for Software and Systems Innovation Sprint Planning Breakdown of business value into assignable tasks picture by oskay

43. - Private and Confidential - i-PANDAWA - Page 43The Premier Event for Software and Systems Innovation SPRINT 2.3 (ARJUNA) We are in this Together. We Die Together, We Win Together! SPRINT GOAL : APLIKASI i-BBO-STABLE.v.2.3.0.0 DONE NAMA DAN DESKRIPSI SPRINT : SPRINT 2.3 - ARJUNA JADWAL PELAKSANAAN SPRINT : - PERIODE SPRINT : 18 JANUARI 2012 s/d 25 JANUARI 2012 (09:00-17:00) - LOKASI, TANGGAL, JAM, SPRINT PLANNING : WISMUL LT.51 – SELASA, 17 JANUARI 2012 - 13:00 - LOKASI, JAM DAILY MEETING : i-PANDAWA SCRUM TEAM AREA, 09:00 WIB OR SKYPE VIDEO CONFERENCE, 09:00 WIB - LOKASI, TANGGAL, JAM, SPRINT DEMO : WISMUL LT.51 – KAMIS, 26 JANUARI 2012 - 09:00 - LOKASI, TANGGAL, JAM, RETROSPECTIVE : WISMUL LT.51 – KAMIS, 26 JANUARI 2012 - 13:00 VELOCITY COMMITMENT DI SPRINT INI : 120 DETAIL FITUR YANG DISEPAKATI : ADA DI COLLABORATION TOOLS DAN SCRUM BOARD NAMA ANGGOTA TIM (YANG WAJIB DI DAILY MEETING) : RIDHO (SCRUM MASTER), DARIE, REZA, SUTAN, SYAIFUL, DJAINUL, AIDA, BAYU HISSAF, HANIN

44. - Private and Confidential - i-PANDAWA - Page 44The Premier Event for Software and Systems Innovation S KONSENSUS TIM We are in this Together. We Die Together, We Win Together! JAM KERJA YANG DISEPAKATI ADALAH 8 JAM HARI KERJA, YAITU DARI JAM 09:00 WIB SAMPAI DENGAN 17:00 WIB SEPAKAT MENJALANI SEMUA CEREMONY SECARA DISIPLIN : SPRINT DAILY MEETING, DAILY SCRUM, SPRINT DEMO, RETROSPECTIVE JIKA TERLAMBAT DAILY MEETING DENDA RP 5.000,-, JIKA TELAT DIATAS 15 MENIT DENDA RP 10.000,- 1 JAM PERTAMA SETIAP HARI SETELAH DAILY MEETING UNTUK MENYELESAIKAN BUGS OPERASIONAL JIKA ADA SETIAP HARI DIUSAHAKAN ADA DEPLOYMENT UNTUK DIKERJAKAN OLEH QA. PADA SAAT DEPLOYMENT, HARUS KIRIM EMAIL PEMBERITAHUAN. WE WILL YELL OUR MOTTO EVERY CEREMONY! SELALU MENGUPDATE BOARD DI SETIAP KEGIATAN SCRUM BOARD DAN BURN DOWN CHART AKAN DI UPDATE SETIAP HARI DI DINDING (SEBAGAI INFORMASI VISUAL PROGRESS REPORT HARIAN)

45. - Private and Confidential - i-PANDAWA - Page 45The Premier Event for Software and Systems Innovation Photo of US doing Sprint Planning

46. - Private and Confidential - i-PANDAWA - Page 46The Premier Event for Software and Systems Innovation Daily Scrum This is The Heartbeat of Scrum!

47. - Private and Confidential - i-PANDAWA - Page 47The Premier Event for Software and Systems Innovation What to Talk in Daily Meeting What I did since Yesterday What I will do Today What things are in my way Only the team talks Not to Scrum Master No problem solving Max 15 minutes Standing up Notes : ► If some members are in a Business Trip, you still do the Daily Meeting (via Skype video calls, or by phone). Still… You must StandUp! ► Respect the Team Member who is speaking

48. - Private and Confidential - i-PANDAWA - Page 48The Premier Event for Software and Systems Innovation Photo of US doing Daily Meeting

49. - Private and Confidential - i-PANDAWA - Page 49The Premier Event for Software and Systems Innovation Sprint Review picture by oskay

50. - Private and Confidential - i-PANDAWA - Page 50The Premier Event for Software and Systems Innovation Goal of the Sprint Review GOAL : ► Satisfy Product Owner ! ► Get some feedbacks that need to be discussed later in Retrospective ► WE WIN TOGETHER! PROCESS : ► Be there on Time! ► Prepare the Data ► Prepare the Demo Scenarios (based on Test Scenarios) ► All the team members must support the demo ► This is the Final Sprint Process! Do it Seriously!

51. - Private and Confidential - i-PANDAWA - Page 51The Premier Event for Software and Systems Innovation Sprint Retrospective (we love this !) Evolve the process picture by kevindooley

53. - Private and Confidential - i-PANDAWA - Page 53The Premier Event for Software and Systems Innovation Why we Love Sprint Retrospective? ► This will Tell Us… Are we Improving yet? ► Different focus in every Sprint Retrospective ► Are you Happy using SCRUM? (individual perspective) ► Are we in the same BOAT? (team perspective) ► How to Solve our problems? ► We are open for Critics and Applauses or Gratitude

54. - Private and Confidential - i-PANDAWA - Page 54The Premier Event for Software and Systems Innovation V. What has Changed Now ► WE ARE IMPROVING ! ► We always try to Improve our self ► Our earlier problem is solved Incrementally per-sprint ► New ideas come in Sprint Retrospective ► We are still learning to be better all day ► Versioning Mechanism can impact to Business Contract ► We are in this Together ► We Die Together, We Win Together!

55. - Private and Confidential - i-PANDAWA - Page 55The Premier Event for Software and Systems Innovation Testimonial Scrum Board!

56. - Private and Confidential - i-PANDAWA - Page 56The Premier Event for Software and Systems Innovation VI. Testimonials Berikut ini adalah Daftar Testimonial yang ditulis oleh seluruh Anggota Tim di Papan Testimonial pada Scrum Board saat Sprint Retrospective terakhir : ► Setelah SCRUM, proses QA (Quality Assurance) menjadi sangat PENTING! ► Dengan SCRUM, semua menjadi beban bersama! Bukan perorangan. ► Dengan SCRUM, semua progress menjadi transparan dan tidak tersembunyi ► Awalnya SCRUM itu kejam, tetapi menjadi sangat berguna bagi saya pribadi ► Pekerjaan saya menjadi lebih berbobot dan lebih dihargai ► Waktu kerja menjadi lebih Jelas dan Pasti ► Dengan Scrum tumbuh rasa tanggung jawab yang lebih besar dari seluruh anggota tim ► Dengan SCRUM, semua menjadi lebih DISIPLIN! ► Dengan pengawasan yang minimum dari manajemen, pekerjaan tetap dapat diselesaikan sesuai dengan target yang disepakati

57. - Private and Confidential - i-PANDAWA - Page 57The Premier Event for Software and Systems Innovation Our Best Testimonial

58. SCRUM ON! i-PANDAWA Framework Our Great Teams http://www.iconpln.co.id http://www.i-pandawa.com