Agile2014 Report: As a Speaker and a Reporter of the latest Agile in the world
2 likes790 views
The Agile2014 conference, held in Orlando, Florida, featured approximately 2000 attendees and 272 sessions focused on the latest trends in agile methodologies. Key trends included the rise of enterprise agile practices, metrics utilization, and advancements in testing approaches such as TDD and BDD. The speaker, Hiroyuki Ito from Rakuten, shared insights on the importance of foundational technical approaches and the necessity for change in organizational mindset to foster agile adoption.
Agile2014 Report: As a Speaker and a Reporter of the latest Agile in the world
- 1. Agile2014 Report As a Speaker and a Reporter of the latest Agile in the world Aug/05/2014 Hiroyuki Ito Development Process Optimization Department, Rakuten, Inc. http://www.rakuten.co.jp/
- 2. 2 Hiroyuki Ito About me Test-Driven Development Group @hageyahhoo (The Hiro)
- 3. 3 What is Agile2014?
- 4. 4 WALL CI/CD WALL TDD WALL ATDD The world’s largest Agile Conference
- 5. 5 Attended as a session speaker!
- 6. 6 Agenda 1. Basic Information of Agile2014 3. The Latest Trend of Agile 2. My Presentation 4. Conclusions
- 7. 7 1. Basic Information of Agile2014 3. The Latest Trend of Agile 2. My Presentation 4. Conclusions
- 8. 8 Basic information Location Orlando, Florida, U.S. Duration 4.5 days Attendees Approximately 2000 persons Sessions 272 sessions Session Speakers Over 280 persons
- 9. 9 Rakuten all superstars! Abex (BDD) Dana (R Marketing) TheHiro (TDD) Pramod (PJM) Yasnob (TDD)
- 10. 10 Trend of sessions Category Sessions Memo Agile Bootcamp 7 Coaching & Mentoring 16 Testing & Quality Assurance 13 Collaboration Culture & Teams 23 Development Practices & Craftsmanship 28 DevOps 15 Enterprise Agile 28 Project Program and Portfolio Management 24 Experience Reports 25 TheHiro made a presentation here. Keynote 3 Leadership 16 Learning 15 Lightning Talks 3 Open Jam 4 All day event held everyday. Research 9 Including LT for researchers. 10 min/person. Special Events 9 Including parties. Stalwarts 8 User Experience 11 Working with Customers 15 Total 272 Related to QA Section Top-down approaches are increasing
- 11. 11 Comparison of trends (with Yamaguchi-san @Yahoo) Category Sessions Memo 2012 2013 2014 Adoption & Transformation 26 0 0 Divided into “Enterprise Agile”, “Learning”, and so on. Agile Bootcamp 7 7 7 Coaching & Mentoring 15 15 16 Distrubuted Agile 5 0 0 Held only in 2012. Emerging Applications of Agile 5 0 0 Held only in 2012. Croudsourced 0 14 0 Held only in 2013. Lean Startup 0 15 0 Held only in 2013. Testing & Quality Assurance 12 11 13 Collaboration Culture & Teams 18 15 23 Development Practices & Craftsmanship 16 20 28 DevOps 0 13 15 Enterprise Agile 21 19 28 Project Program and Portfolio Management 0 25 24 Experience Reports 20 14 25 Keynote 3 3 3 Leadership 13 12 16 Learning 0 17 15 Lightning Talks 0 0 3 10 min/person. Open Jam 26 4 4 Including “Coaches Clinic” in 2012. Research 8 9 9 Including LT for researchers. Special Events 9 8 9 Including parties. Stalwarts 9 7 8 User Experience 12 14 11 Working with Customers 17 17 15 Total 242 259 272 Remaining at the same level Increasing
- 12. 12 1. Basic Information of Agile2014 3. The Latest Trend of Agile 2. My Presentation 4. Conclusions
- 13. 13 Information and documents Session information http://agile2014.sched.org/event/356d50c44035cafe4c27c33da03c2b80# Presentation document published on Agile Alliance site http://schd.ws/hosted_files/agile2014/65/1748_TechnologyDrivenDevelopment.pdf Paper published on Agile Alliance site http://www.agilealliance.org/files/5014/0509/9284/ExperienceReport.2014.Ito.pdf
- 15. 15 Before session (expanded) Fully booked!? (105 seats)
- 16. 16 On session program
- 17. 17 Venue
- 18. 18 Key item as a speaker
- 19. 19 Image of presentation
- 20. 20 Result (quick estimation) About 60 persons attended. •Attendance Ratio = 57% •Average : about 50% (-> GOOD!) My shepherds often reacted positively during my presentation. •He is a real SAMURAI! (-> Maybe good ) Only 3 persons left during my presentation. •Remaining Ratio = 95% •Average : about 80% (-> GOOD!)
- 21. 21 Rebecca Wirfs-Brock: Track chair
- 22. 22 Jutta Eckstein: My shepherd
- 23. 23 Impression Englishnization is useful. •I had no trouble •making a presentation with English. •speaking in front of many English native speakers. Writing a paper was very useful for •clarifying ideas got through your work. •acquiring how to think, evaluate, and explain objectively. •publishing ideas throughout the world easily and fast. Practicing a presentation was very useful. •Feedback is very important before the real presentation. •Rakuten members gave me a lot of insightful feedbacks before the conference.
- 24. 24 Next Action Attend as a speaker again! •I have some themes •Advanced testing •Improve by metrics Nurture younger members and colleagues for consistent growth of our company. •Write and submit papers •Attend the next conference as a speaker
- 25. 25 1. Basic Information of Agile2014 3. The Latest Trend of Agile 2. My Presentation 4. Conclusions
- 26. 26 About 3 years ago Value Agile/Scrum/Lean
- 27. 27 This year Value Metrics CFD/Kanban/KPIs Testing BDD/ATDD/ET/MT Enterprise Agile Organizational Change/Psychology Agile/Scrum/Lean
- 28. 28 The latest trend of Agile Agile, Scrum, and Lean are ordinary. •Most of practitioners are thinking about the better ways to utilize them more. I found 3 big trends. •Organizational approach -> Enterprise Agile •Technical approach -> Testing •Combination of both -> Metrics
- 29. 29 Value Metrics CFD/Kanban/KPIs Testing BDD/ATDD/ET/MT Enterprise Agile Organizational Change/Psychology Agile/Scrum/Lean 1. Enterprise Agile
- 30. 30 Executives Managers UI/UX Designers Developers Ordinary Agile Bottom-up approach Business Analyst
- 31. 31 Executives Managers UI/UX Designers Developers Enterprise Agile Business Analyst Decrease silos Top-down approach
- 32. 32 The trend of Enterprise Agile Practitioner’s concern is changing •from improvement of development teams •to total optimization including executives and organization Most of ideas are spiritual… 1.Not concrete 2.Most of speakers just say the importance of changing mindset 3.Expanding in the U.S. On the other hand, the influence of SAFe (Scaled Agile Framework) is increasing dramatically. •There were about 5 sessions about SAFe. •http://scaledagileframework.com/
- 33. 33 Discussion about EA with other practitioners It is ordinary to face with middle management layer and executive layer to adopt the bottom-up approach. •It is necessary to find and decrease wastes based on “command and control” organization and leadership. On the other hand, we’d be better utilize technical foundation to avoid failures. Changing top’s mindset is useful for buy-in.
- 34. 34 Changing mindset is very important, but… YES, YOU CAN!
- 35. 35 My opinion Technical foundation is necessary!
- 36. 36 e.g.) Use automation for collaboration Check-in build (hourly) My PC We demonstrate latest application to the business analyst and managers in every daily scrum Deliver to all team members automatically Build applications and run regression tests automatically
- 37. 37 Working software for building shared understanding Business Analyst UI/UX Designers Developers Get fast feedback Know about the progress
- 38. 38 2. Testing Value Metrics CFD/Kanban/KPIs Testing BDD/ATDD/ET/MT Enterprise Agile Organizational Change/Psychology Agile/Scrum/Lean
- 39. 39 3 topics about testing BDD/ATDD Mutation Testing Exploratory Testing
- 40. 40 Pattern of Automation for BDD/ATDD Specification by Example •Use “examples” to build shared understanding •Create high-level scenarios (by using domain words) •Create cross-functional team for reducing rework Default Data Pattern http://www.cheezyworld.com/2010/11/21/ui-tests-default-dat/ Page Object Pattern https://code.google.com/p/selenium/wiki/PageObjects Test Data Management Pattern •Prepare data for each test and rollback •Prepare data for all tests and rollback •Run all tests and commit all data
- 41. 41 Current knowledge of Exploratory Testing Session-based test management http://www.satisfice.com/articles/sbtm.pdf Heuristics •http://testobsessed.com/wp- content/uploads/2011/04/testheuristicscheatsheetv1.pdf •http://www.satisfice.com/tools/htsm.pdf Test charters http://www.qualitestgroup.com/howTo/How-to-write-an- Exploratory-Test-Charter
- 42. 42 Mutation Testing (1) <Example> // Production code int foo (int x, int y) { int z = 0; if ((x > 0) && (y > 0)) { z = x; } return z; } // Test code assertEquals(2, foo(2, 2)) assertEquals(0, foo(2, -1)) assertEquals(0, foo(-1, 2))
- 43. 43 Mutation Testing (2) <Add mutant> // Production code int foo (int x, int y) { int z = 0; if ((x > 0) && (y >= 0)) { z = x; } return z; } // Test code assertEquals(2, foo(2, 2)) assertEquals(0, foo(2, -1)) assertEquals(0, foo(-1, 2))
- 44. 44 Mutation Testing (3) <Kill mutant by changing unit test> // Production code int foo (int x, int y) { int z = 0; if ((x > 0) && (y >= 0)) { z = x; } return z; } // Test code assertEquals(2, foo(2, 2)) assertEquals(0, foo(2, 0)) assertEquals(0, foo(-1, 2))
- 45. 45 Mutation Testing (4) Objective of Mutation Testing is adding mutant and find code smells. •Basically for improving unit testing. Patterns of mutants http://pitest.org/quickstart/mutators/ •< to <= (adding “=“) •< to >= (reversing) •Reverse + and - •Make if statement invalid (e.g. if (true)) •Change the value of constant •Change return value (e.g. null) •Erase method call
- 46. 46 Mutation Testing (5) Presentation document http://schd.ws/hosted_files/agile2014/c1/1435_Mutation_Test_- _A_New_Way_to_Improve_Code_and_Test.pdf Definition of Mutation Testing by Parasoft http://www.parasoft.com/products/article.jsp?articleId=291 PIT (tool for Mutation Testing, for Java) http://pitest.org/ Research of Mutation Testing http://crestweb.cs.ucl.ac.uk/resources/mutation_testing_repository/
- 47. 47 Next Action Study more about BDD. •based on “Specification by Example” Create Synergy among QA section members by BDD, ATDD, Exploratory Testing, and Mutation Testing. •Create testable & clear specification for ease of testing •Enhance skills for test automation
- 48. 48 3. Metrics Value Metrics CFD/Kanban/KPIs Testing BDD/ATDD/ET/MT Enterprise Agile Organizational Change/Psychology Agile/Scrum/Lean
- 49. 49 •Install applications : 2 minutes/change •Regression testing : 3 minutes/change •Change requests : 3 times/week Example of metrics
- 51. 51 Increasing concerns Do the same thing in software product world. It is useful for clarifying the biggest point to improve. For finding problems and knowing progress.
- 52. 52 “Useful Metrics in a Complex World” by Ken Power (1) Ken’s paper http://www.agilealliance.org/files/9814/0509/9343/ExperienceReport.2014.Power.pdf Point of metrics •What perspective to measure? •What does work flow? •What impedes the flow of work?
- 53. 53 “Useful Metrics in a Complex World” by Ken Power (2) Cumulative flow •Useful for finding problems that impede velocity. •Know information by trend and hypothesize the following movement. Cycle time Useful for finding the difference among each status of Kanban board. Throughput analysis •Useful for knowing the real progress. •Can distinguish the failure demand and value demand.
- 54. 54 “Useful Metrics in a Complex World” by Ken Power (3) Impression •The basic idea of metrics is to find problems and know progress. •Get information from the change of metrics. •Other person’s metrics are very insightful. •We’d be better decide who gather metrics. Point to use metrics •Review each metric continuously
- 55. 55 Next Action I decided to start the study session about metrics. •I have been preparing for the study session before attending Agile2014. •I will combine our experience of Gemba and the latest researches.
- 56. 56 1. Basic Information of Agile2014 3. The Latest Trend of Agile 2. My Presentation 4. Conclusions
- 57. 57 The essence of Agile Agile is a continuous improvement action and process that can adopt the whole things. •PDCA cycles •Less up-front rules •Create rules & processes by team members (mature) •Retrospectives •Based on numerical measurement (metrics) •Anything is ok to improve (automation, non-technical process) •For whole team/organization/company
- 58. 58 The latest Agile The essence of Agile is NOT changing. On the other hand, doing the essence by themselves is very difficult at present. •I will support it as an Agile Coach from now on. Field is expanding. •Including organizational issues, testing, metrics, and so on. You’d better clarify what you need and gather information based on the the essence of Agile.
- 60. 60 Reference Program of Agile2014 http://agile2014.agilealliance.org/program/ My blog (Japanese) http://d.hatena.ne.jp/hageyahhoo/ Papers and resources by Agile Alliance http://www.agilealliance.org/resources/