Your SlideShare is downloading. ×
0
Scrum meetings
Scrum meetings
Scrum meetings
Scrum meetings
Scrum meetings
Scrum meetings
Scrum meetings
Scrum meetings
Scrum meetings
Scrum meetings
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Scrum meetings

390

Published on

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

  • Be the first to like this

No Downloads
Views
Total Views
390
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Scrum MeetingsPresented by Juan Banda
  • 2. Scrum meetingsMeetings try to create this In order to avoid this 2
  • 3. Estimation Meetings•Preparation forSprint Planning•Formal estimation•Have at least twomeetings perSprint•Estimate only Sizenot Time•Provides input forRelease Planning 3
  • 4. Sprint Planning - Part 1The team shouldreview and analyzethe: •Product Backlog •Team capabilities Business • conditions Technology • stability Executable • product increment 4
  • 5. Sprint Planning - Part 2And then analyzeand design the: •Sprint Goal •Selected Product BacklogIn order to get theSprint Backlog 5
  • 6. Daily Scrum Meeting•Daily 15 minute meeting•Same place and time everyday•Team room - with taskboard•Chickens and pigs•Three questions: What have you • ACHIEVED since last meeting? What will you ACHIEVE • before next meeting? • What is in your way?Impediments and•Decisions 6
  • 7. Sprint Review•Attended by theScrum Team + allinterestedstakeholdersReview Selected•Product Backlog•Show built (done)functionalityGroom Product•Backlog based onoutcome of Sprint andconversation• Set next Sprint goal 7
  • 8. EvaluationConsequences•Move back to the backlogunfinished work andreprioritize it•Review the backlog to seeif it’s still current•Decide to make changes inteam configuration andtasks assignation•Changes in teamconfiguration might include(not recommended) addingextra muscle to try to keepon schedule or sped upproduction 8
  • 9. Sprint Retrospective•Team meets withScrum Master toinspect and adapttheir processTeam devises•solution to one or twomost importantproblems•Changing everythingat the time is notpossible, the true andlasting improvementcomes for small butsustainable changes 9
  • 10. Thanks for attending

×