辛さしかないふりかえりの口当たりを良くしていった話をふりかえる

Slide 1

Slide 1 text

5TVZPTIJ:BNBNPUP ਏ͔͞͠ͳ͍;Γ͔͑Γͷ ޱ౰ͨΓΛྑ͍ͯͬͨ͘͠࿩Λ ;Γ͔͑Δ %BOCPFOKPZXBUDIJOHBQSFUUZTQSPVUCZ5BLBTIJ BFT JTMJDFOTFEVOEFS$$#:4"

Slide 6

Slide 6 text

Product Owner The Scrum Framework At a Glance Version 5.0 Product Backlog (owned by PO) Refinement Sprint Backlog (owned by the Developers) Increment Sprint Review Sprint Retrospective Daily Scrum Developers ScrumMaster = Scrum artifacts that help manage the work = Events or ceremonies that occur inside each Sprint = Ongoing activity Copyright © 2020 SCRUM ALLIANCE®, Inc. All Rights Reserved. Who should participate and for how long? SPRINT PLANNING: Who: The entire Scrum Team Timebox: Maximum of 8 hours for a month-long Sprint. Shorter timebox for shorter Sprints. DAILY SCRUM: Who: The Developers, but if the Product Owner or Scrum Master are actively working on items in the Sprint Backlog, they participate as Developers. Timebox: Maximum of 15 minutes. SPRINT REVIEW: Who: The entire Scrum Team. Stakeholders are invited to provide feedback on the increment. Timebox: Maximum of 4 hours for a month-long Sprint. Shorter timebox for shorter Sprints. SPRINT RETROSPECTIVE: Who: The entire Scrum Team. Timebox: Maximum of 3 hours meeting for a month-long Sprint. Shorter timebox for shorter Sprints. The Product Backlog is an emergent, ordered list of what is needed to improve the product and includes the Product Goal. Refinement is a continuous activity used to add detail, estimates, and order to items in the Product Backlog. The Sprint Backlog is the set of Product Backlog items selected for the Sprint by the Developers, plus a plan for delivering the product Increment and realizing the Sprint Goal. Each Sprint should bring the product closer to the overall Product Goal. The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work. The purpose of the Sprint Review is to inspect the outcome of the Sprint with stakeholders and determine future adaptations. A sum of usable Sprint Backlog items completed by the Developers in the Sprint that meets the Definition of Done, plus the value of all of the increments that came before. The Sprint Retrospective is when the Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and Definition of Done. The Team identifies improvements to make the next Sprint more effective and enjoyable. This event concludes the Sprint. *Sprint of 1 month or less (the heartbeat of Scrum) Sprint Planning Sprint Planning establishes the Sprint Goal, what can be done, and how the chosen work will be completed. IUUQTSFTPVSDFTTDSVNBMMJBODFPSH"SUJDMFPWFSWJFXTDSVNGSBNFXPSL ;Γ͔͑ΓͰಘΒΕΔ΋ͷ w ίϛϡχέʔγϣϯ͕׆ൃʹͳΓɺ৘ใͷಁ໌ੑ͕ߴ·Δ w ໰୊͕ਝ଎ʹڞ༗͞ΕɺνʔϜ಺Ͱղܾʹ޲͔͍͚ͬͯΔ w Ձ஋ΛੜΈग़͢ϓϩηεΛࣗ෼ͨͪͰݟ௚͠ɺΧΠθϯ͍͚ͯ͠Δ w νʔϜʹඞཁͳ஌ࣝΛੵۃతʹֶͼɺٵऩ͍͚ͯ͠Δ w ࣗ཯తʹߟ͑ɺߦಈͰ͖Δ ʮΞδϟΠϧͳνʔϜΛ࡞Δ;Γ͔͑ΓΨΠυϒοΫʯ͔ΒҾ༻

Slide 1

Slide 1 text

Slide 2

Slide 2 text

Slide 3

Slide 3 text

Slide 4

Slide 4 text

Slide 5

Slide 5 text

Slide 6

Slide 6 text

Slide 7

Slide 7 text

Slide 8

Slide 8 text

Slide 9

Slide 9 text

Slide 10

Slide 10 text

Slide 11

Slide 11 text

Slide 12

Slide 12 text

Slide 13

Slide 13 text

Slide 14

Slide 14 text

Slide 15

Slide 15 text

Slide 16

Slide 16 text

Slide 17

Slide 17 text

Slide 18

Slide 18 text

Slide 19

Slide 19 text

Slide 20

Slide 20 text

Slide 21

Slide 21 text

Slide 22

Slide 22 text

Slide 23

Slide 23 text

Slide 24

Slide 24 text

Slide 25

Slide 25 text

Slide 26

Slide 26 text

Slide 27

Slide 27 text

Slide 28

Slide 28 text

Slide 29

Slide 29 text