[RakutenTechConf2013] [LT] Scrum of Global Ichiba
Upcoming SlideShare
Loading in...5
×
 

[RakutenTechConf2013] [LT] Scrum of Global Ichiba

on

  • 506 views

Rakuten Technology Conference 2013

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

Statistics

Views

Total Views
506
Views on SlideShare
506
Embed Views
0

Actions

Likes
1
Downloads
3
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • ・世界地図はPower Point付属のイメージを使用 <br /> 楽天市場の国際展開をささえる共通プラットフォームを開発しています。 <br />
  • RMSを <br />
  • Organization structure/Role <br />
  • Organization structure/Role <br />
  • Organization structure/Role <br />
  • Organization structure/Role <br />
  • ・Reviewer以外でもチーム内、誰でもみれる(みてくれている) <br /> ・チケット単位で残ってわかりやすい <br />
  • Organization structure/Role <br />
  • Organization structure/Role <br />
  • Organization structure/Role <br />

[RakutenTechConf2013] [LT] Scrum of Global Ichiba[RakutenTechConf2013] [LT] Scrum of Global Ichiba Presentation Transcript

  • 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
  • Global Ichiba 2
  • Development Teams (over 100 people) Sendai Tokyo San Francisco China India 3
  • Monthly Release/Many teams Monthly Release PDM Product Backlog QA Product Management Mall RMS API 4
  • RMS  = Rakuten Merchant Serve 5
  • RMS  = Rakuten Merchant Server 6
  • Monthly Release/Many teams Monthly Release PDM Product Backlog QA Product Management Mall RMS API 7
  • 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
  • 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
  • Simplization Discussing acceptance criteria(develop goal) To simplize GOAL, we update “Acceptance criteria” through Planning Meeting, together. (if necessary , we separate the tickets) 10
  • 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
  • How are we doing ? Business Requirement Product Ownership PDM Engineer Lead Dev Dev team Product Dev Dev Product Dev Visualization Dev team Dev ・ ・ ・ ・ ・ ・ 12
  • Visualization “Burn Down chart” drawn by JIRA 13
  • Visualization See progress by using “Burn down chart” pattern 14
  • Visualization Code Review through “Pull Request” 15
  • How are we doing ? Business Requirement Product Ownership PDM Engineer Lead Dev Dev team Product Dev Dev Product Dev Visualization Dev team Dev ・ ・ ・ ・ ・ ・ 16
  • How are we doing ? Business Requirement Product Ownership PDM Engineer Lead Dev Automation Dev team Product Dev Dev Product Dev Dev team Dev ・ ・ ・ ・ ・ ・ 17
  • Automation Auto Test / Deploy by Jenkins 18
  • Automation Auto Test / Deploy by Jenkins 19
  • Summary Business Requirement Product Ownership PDM Engineer Lead Dev Automation Dev team Product Dev Dev Product Dev Visualization Dev team Dev ・ ・ ・ ・ ・ ・ Simplization 20
  • Contact Me satoshi.yuguchi@mail.rakuten.com 21