[RakutenTechConf2013] [LT] Scrum of Global Ichiba

519 views
281 views

Published on

Rakuten Technology Conference 2013
"Scrum of Global Ichiba"
Satoshi Yuguchi

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
519
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
5
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • ・世界地図は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
  • [RakutenTechConf2013] [LT] Scrum of Global Ichiba

    1. 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
    2. 2. Global Ichiba 2
    3. 3. Development Teams (over 100 people) Sendai Tokyo San Francisco China India 3
    4. 4. Monthly Release/Many teams Monthly Release PDM Product Backlog QA Product Management Mall RMS API 4
    5. 5. RMS  = Rakuten Merchant Serve 5
    6. 6. RMS  = Rakuten Merchant Server 6
    7. 7. Monthly Release/Many teams Monthly Release PDM Product Backlog QA Product Management Mall RMS API 7
    8. 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. 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. 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. 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. 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. 13. Visualization “Burn Down chart” drawn by JIRA 13
    14. 14. Visualization See progress by using “Burn down chart” pattern 14
    15. 15. Visualization Code Review through “Pull Request” 15
    16. 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. 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. 18. Automation Auto Test / Deploy by Jenkins 18
    19. 19. Automation Auto Test / Deploy by Jenkins 19
    20. 20. Summary Business Requirement Product Ownership PDM Engineer Lead Dev Automation Dev team Product Dev Dev Product Dev Visualization Dev team Dev ・ ・ ・ ・ ・ ・ Simplization 20
    21. 21. Contact Me satoshi.yuguchi@mail.rakuten.com 21

    ×