Evolving DevOps Teams and Flexible Organizational Culture

presented at the Devopsdays 15 Year Anniversary Celebration: Antwerp #DevOpsDays
https://devopsdays.org/events/2024-antwerp/program/evolving-devops-teams-and-flexible-organizational-culture

Transcript

1. Evolving DevOps Teams and Flexible Organizational Culture September 5, 2024 @Devopsdays 15 Year Anniversary Celebration: Antwerp Ikuo Odanaka
2. About • Tokyo, Japan • Engineering Manager at KAKEHASHI Inc. • Focused on Agile Software Development Process and OKR Speaker at • DevOpsDays Tokyo 2023/2024 • Regional Scrum Gathering Tokyo 2021/2023/2024 • Scrum Fest Kanagawa 2024(Keynote) Book Author of • いちばんやさしいアジャイル開発の教本 (Co-Author): comprehensive guide to agile for beginners • アジャイルチームによる目標づくりガイドブック : creating effective goals for agile teams using OKR Ikuo Odanaka 小田中 育生 @dora_e_m
3. © KAKEHASHI Inc. KAKEHASHI Inc. “Inventing a sustainable medical ecosystem” • A healthcare tech startup in Japan(2016〜) • Multiple products for pharmacies • 350+ employees (as of Dec. 2023) • Agile/Scrum
4. © KAKEHASHI Inc. Our Value Integrity Just Do It Leadership & Followership One for all Unlearn Transparency
5. © KAKEHASHI Inc. Overview MVP Phase PoC Phase Collaboration Phase Shortening lead time to release our new product!! A high-speed hypothesis testing cycle with DevOps Collaborate with BIG team Our cycle Their cycle We are changing our development style in accordance with the phase of our products.I will talk about that and explain what could keeps a team an ever-changing DevOps Team.
6. © KAKEHASHI Inc. Our Team TEAM MEMBER 1 Engineering Manager 4 Engineer 3 Product Manager 1 Designer PRODUCT Vertical SaaS for pharmacies Committed to changing patient behavior through changing the behavior of pharmacists product pharmacist patient
7. Shortening lead time to release our new product!! MVP Phase
8. © KAKEHASHI Inc. A Strategy of Our Team SAM Serviceable Available Market SOM Serviceable Obtainable Market We are searching for a fast track and are working on expanding into new markets. Existing Product Our New Product Discover new market
9. © KAKEHASHI Inc. Our product managers have a hypothesis SAM Serviceable Available Market SOM Serviceable Obtainable Market Our New Product Discover new market
10. © KAKEHASHI Inc. Test our hypothesis A.S.A.P.!! To achieve this, lines up user stories at first.
11. © KAKEHASHI Inc. Drawing MVP Line Our MVP line definition is below: “If we haven’t completed up to the line, we’ll postpone the launch.”
12. © KAKEHASHI Inc. Engineers added items Add items from the developers’ perspective e.g.) setup DB, Check Network, testing, etc…
13. © KAKEHASHI Inc. Grouping items
14. © KAKEHASHI Inc. We developed a product iteratively 1st 2nd Priorities changed Items were re-prioritized according to the results of the iteration.
15. © KAKEHASHI Inc. worked together though this map. This map makes our work transparent. Transparency enables us to inspect work and adapt to our situations.
16. © KAKEHASHI Inc. Successful Launch! and into the…
17. A high-speed hypothesis testing cycle with DevOps PoC(Proof of Concept) Phase
18. AARRR!
19. © KAKEHASHI Inc. AARRR Pirates Metrics Framework Acquisition Retension Referral Revenue Activation
20. © KAKEHASHI Inc. Our hypothesis Acquisition Retension Referral Revenue Our new product will solve the problem of pharmacists, so once pharmacists use this products, they will continue to use it! Activation
21. © KAKEHASHI Inc. But, there is a problem…… In Japan, Pharmacists are very busy!
22. © KAKEHASHI Inc. Some customers say that “I don’t have time to use that product”
23. © KAKEHASHI Inc. How could we rise up activation rate? Acquisition Retension Referral Revenue Activation
24. © KAKEHASHI Inc. Creating inception deck (partial) Why are we here? Elevator pitch Product Box NOT list Meet the neighbors Show solution Up at night Size it up What’s going to give What’s going to take To enhance teamwork
25. © KAKEHASHI Inc. Why are we here? For inventing a sustainable medical ecosystem, we contribute to the promotion of new businesses. Regardless of the means.
26. © KAKEHASHI Inc. Scrum Daily Scrum Sprint Review Sprint Retrospective 1-week Sprint Product Backlog Sprint Planning
27. © KAKEHASHI Inc. Sprint Planning Daily Scrum Sprint Review Sprint Retrospective 1-week Sprint Product Backlog Sprint Planning
28. © KAKEHASHI Inc. Updating Hypotheses Product Backlog Observing how users actually used the system Interviewing pharmacists to gain insight Update their hypotheses, written as a Product Backlog
29. © KAKEHASHI Inc. Daily Scrum Daily Scrum 1-week Sprint Product Backlog Sprint Planning Sprint Retrospective Sprint Review
30. © KAKEHASHI Inc. All members are gathering everyday Product Backlog Product Perspective Engineering Perspective Refining our product backlog from a product perspective and an engineering perspective
31. © KAKEHASHI Inc. Refinement has been occurred everyday Daily Scrum 1-week Sprint Product Backlog Sprint Planning Refinement Sprint Retrospective Sprint Review
32. © KAKEHASHI Inc. Trunk-based Development Image from https://trunkbaseddevelopment.com/ （Accessed on 2024-06-30） To enable quick and frequent deployment, we choose trunk-based development. We deploy to production almost daily: deployed to production 25 times a month peak: deployed 4 times in a single day
33. © KAKEHASHI Inc. Several releases during an our sprint Daily Scrum Sprint Review Sprint Retrospective 1-week Sprint Product Backlog Sprint Planning Deploy to production
34. © KAKEHASHI Inc. Sprint review Daily Scrum Sprint Review Sprint Retrospective 1-week Sprint Product Backlog Sprint Planning
35. © KAKEHASHI Inc. Demonstrating some releases Daily Scrum Sprint Review Sprint Retrospective 1-week Sprint Product Backlog Sprint Planning Deploy to production Stakeholders comment based on the demo.
36. © KAKEHASHI Inc. Daily Scrum Sprint Review Sprint Retrospective 1-week Sprint Product Backlog Sprint Planning Sprint Retrospective
37. © KAKEHASHI Inc. Different practices each time
38. © KAKEHASHI Inc. Our Proudest Episode Product Managers visited a customer pharmacy and brought back their feedback. Engineers deployed the new version to production the very same day. This makes a surprise and a delight of our customer.
39. © KAKEHASHI Inc. They said that “We’ve never had feedback reflected so quickly.”
40. © KAKEHASHI Inc. So we rise up activation rate! Acquisition Retension Referral Revenue Activation
41. © KAKEHASHI Inc. Our hypothesis is right Acquisition Retension Referral Revenue Once pharmacists use this products, they will continue to use it! And next step is… Activation
42. Collaborate with BIG team Collaboration Phase
43. © KAKEHASHI Inc. A Strategy of Our Team SAM Serviceable Available Market SOM Serviceable Obtainable Market We are searching for a fast track and were working on expanding into new markets. Existing Product Our New Product Discover new market
44. © KAKEHASHI Inc. Our hypothesis is right Acquisition Retension Referral Revenue Once pharmacists use this products, they will continue to use it! And next step is… Activation
45. © KAKEHASHI Inc. Sources of motivation developer experience customer experience/ user experience mission, vision, value MVV, CX/UX, DX… All sources of motivation are in very good condition.
46. © KAKEHASHI Inc. Our new discovery SAM Serviceable Available Market SOM Serviceable Obtainable Market Our new product features will works well for our existing product customers. Existing Product Our New Product Discover new market Enhance existing market
47. © KAKEHASHI Inc. Our boss said: “We were searching for a fast track and were working on expanding into new markets. However, through deep insights gained from that work, we discovered that the fast track actually exists in existing markets!”
48. Wall of BIG-team
49. © KAKEHASHI Inc. • One month cycle release • Separate roles for each process • Many stakeholders Development process of the Existing Product
50. © KAKEHASHI Inc. Past: Several releases during an our sprint Daily Scrum Sprint Review Sprint Retrospective 1-week Sprint Product Backlog Sprint Planning Deploy to production
51. © KAKEHASHI Inc. • One month cycle release Now: It seems so long time for us
52. © KAKEHASHI Inc. Past: All members are gathering everyday Product Backlog Product Perspective Engineering Perspective Refining our product backlog from a product perspective and an engineering perspective
53. © KAKEHASHI Inc. • Separate roles for each process Now: Silos are there Product Managers Developers QAs Define requirements Development Verification & Validation
54. © KAKEHASHI Inc. All stakeholders attends an our sprint review, therefore decision-making is so fast. Past: had a few stakeholders Daily Scrum Sprint Review Sprint Retrospective 1-week Sprint Product Backlog Sprint Planning Deploy to production
55. © KAKEHASHI Inc. Had to coordinate with each stakeholder individually. Now: had many stakeholders Specification Review with stakeholder A Specification Review with stakeholder B Specification Review with stakeholder C
56. © KAKEHASHI Inc. Sources of motivation developer experience customer experience/ user experience mission, vision, value The developer experience was regressive.
57. © KAKEHASHI Inc. Deployment numbers are decreasing Deploy frequency Measuring Four Keys with Japanese DevOps tool “Findy Team+”
58. © KAKEHASHI Inc. Well-being score is also decreasing well-being Score We also works on organizational development, so we measure wellbeing indicators.
59. © KAKEHASHI Inc. Talk about it through a retrospective Oneday, we talked about this issue. Some were resolved, but the fog was not completely lifted.
60. It’s tough, so tough.
61. but…
62. Why are we here?
63. © KAKEHASHI Inc. Why are we here? For inventing a sustainable medical ecosystem, we contribute to the promotion of new businesses. Regardless of the means.
64. © KAKEHASHI Inc. Sources of motivation developer experience customer experience/ user experience mission, vision, value Our current work is well matched with MVV, and our development will rise up CX/UX. We decided that trying to rise up DX by ourselves. by team
65. © KAKEHASHI Inc. We sought our way through retrospective Daily Scrum Sprint Review Sprint Retrospective 1-week Sprint Product Backlog Sprint Planning Back to the egg. Choosing the path of steady improvement.
66. © KAKEHASHI Inc. Adopt to the process of the collaborating team • One month cycle release • Separate roles for each process • Many stakeholders We accepted these constraints and adopted a process in which we excel.
67. © KAKEHASHI Inc. • One month cycle release • Create working software every week Adopt to the release cycle Working Software Deploy to production
68. © KAKEHASHI Inc. • Working with people in different roles • Working as a team, not in different silos Update their silos Product Managers Developers QAs Define requirements Development Verification & Validation
69. © KAKEHASHI Inc. Our product managers interacts with stakeholders frequently. Stakeholder collaboration Specification Review with stakeholder A Specification Review with stakeholder B Specification Review with stakeholder C
70. Finally, we released new features in an existing product. and…
71. © KAKEHASHI Inc. It’s time to celebrate!! “Look! The product utilization is clearly increasing!”
72. © KAKEHASHI Inc. Our customers said that “This update has clearly made it easier to use.”
73. © KAKEHASHI Inc. A step forward in SOM expansion SAM Serviceable Available Market SOM Serviceable Obtainable Market We did it. Existing Product Our New Product Discover new market Enhance existing market
74. what could keeps a team an ever-changing DevOps Team Conclusion
75. © KAKEHASHI Inc. Our jouney MVP Phase PoC Phase Collaboration Phase Shortening lead time to release our new product!! A high-speed hypothesis testing cycle with DevOps Collaborate with BIG team Our cycle Their cycle Our development style is changing accordance with the phase of our products. What makes us an ever-changing DevOps team?
76. © KAKEHASHI Inc. Why are we here? For inventing a sustainable medical ecosystem, we contribute to the promotion of new businesses. Regardless of the means.
77. © KAKEHASHI Inc. Our Value Integrity Just Do It Leadership & Followership One for all Unlearn Transparency
78. © KAKEHASHI Inc. Daily Scrum Sprint Review Sprint Retrospective 1-week Sprint Product Backlog Sprint Planning Sprint Retrospective
79. © KAKEHASHI Inc. Value,mission,and practices Our Company’s Value “Just Do It” and “Unlearn” Our “Why are we here?” Generating highly GRIT to the goal Bringing the courage to keep changing enabling a team as ever-changing, and realizing an our goal
80. © KAKEHASHI Inc. ever-changing team can rise-up CX/UX. “This update has clearly made it easier to use.”
81. © KAKEHASHI Inc. Our SNS account is here: 𝕏 @kakehashi_dev Thank you!!