[RakutenTechConf2013] [LT] Scrum of Global Ichiba
•Download as PPT, PDF•
1 like•938 views
This document discusses Rakuten's approach to developing their global e-commerce marketplace called Global Ichiba using Scrum. It has over 100 developers split across multiple teams in Japan, the US, China, and India who work together on monthly releases. The teams focus on business requirements, application development, product development, and simplifying goals. They use tools like JIRA for tracking work and visualizing progress through burn down charts. Automated testing and deployment is done through Jenkins. The goal is regular monthly releases through collaboration between distributed teams.
Recommended
Recommended
More Related Content
What's hot
What's hot (10)
Similar to [RakutenTechConf2013] [LT] Scrum of Global Ichiba
Similar to [RakutenTechConf2013] [LT] Scrum of Global Ichiba (20)
More from Rakuten Group, Inc.
More from Rakuten Group, Inc. (20)
Recently uploaded
Recently uploaded (20)
[RakutenTechConf2013] [LT] Scrum of Global Ichiba
- 1. Scrum of Global Ichiba Rakuten Tech Conference 2013 Yuguchi Satoshi Rakuten Ichiba Development Department Global E-commerce Marketplace Section Rakuten, Inc. Rakuten Ichiba Development October 26th, 2013
- 3. Development Teams (over 100 people) Sendai Tokyo San Francisco China India 3
- 4. Monthly Release/Many teams Monthly Release PDM Product Backlog QA Product Management Mall RMS API 4
- 5. ＲＭＳ = Rakuten Merchant Serve 5
- 6. ＲＭＳ = Rakuten Merchant Server 6
- 7. Monthly Release/Many teams Monthly Release PDM Product Backlog QA Product Management Mall RMS API 7
- 8. How are we doing ? Focus on Business business. Requirement Focus on Application. Product Ownership PDM Engineer Lead Dev Product Dev Dev Product Dev Dev ・ ・ ・ 8
- 9. How are we doing ? Business Requirement Product Ownership PDM Engineer Lead Dev Dev Product Dev Dev Dev team Dev Dev Product Dev Dev Dev Dev ・ ・ ・ ・ ・ ・ Simplization Dev team 9
- 10. Simplization Discussing acceptance criteria(develop goal) To simplize GOAL, we update “Acceptance criteria” through Planning Meeting, together. (if necessary , we separate the tickets) 10
- 11. How are we doing ? Business Requirement Product Ownership PDM Engineer Lead Dev Dev Product Dev Dev Dev team Dev Dev Product Dev Dev Dev Dev ・ ・ ・ ・ ・ ・ Simplization Dev team 11
- 12. How are we doing ? Business Requirement Product Ownership PDM Engineer Lead Dev Dev team Product Dev Dev Product Dev Visualization Dev team Dev ・ ・ ・ ・ ・ ・ 12
- 13. Visualization “Burn Down chart” drawn by JIRA 13
- 14. Visualization See progress by using “Burn down chart” pattern 14
- 15. Visualization Code Review through “Pull Request” 15
- 16. How are we doing ? Business Requirement Product Ownership PDM Engineer Lead Dev Dev team Product Dev Dev Product Dev Visualization Dev team Dev ・ ・ ・ ・ ・ ・ 16
- 17. How are we doing ? Business Requirement Product Ownership PDM Engineer Lead Dev Automation Dev team Product Dev Dev Product Dev Dev team Dev ・ ・ ・ ・ ・ ・ 17
- 18. Automation Auto Test / Deploy by Jenkins 18
- 19. Automation Auto Test / Deploy by Jenkins 19
- 20. Summary Business Requirement Product Ownership PDM Engineer Lead Dev Automation Dev team Product Dev Dev Product Dev Visualization Dev team Dev ・ ・ ・ ・ ・ ・ Simplization 20
Editor's Notes
- ・世界地図はPower Point付属のイメージを使用 楽天市場の国際展開をささえる共通プラットフォームを開発しています。
- RMSを
- Organization structure/Role
- Organization structure/Role
- Organization structure/Role
- Organization structure/Role
- ・Reviewer以外でもチーム内、誰でもみれる（みてくれている） ・チケット単位で残ってわかりやすい
- Organization structure/Role
- Organization structure/Role
- Organization structure/Role