Scrum in a nutshell

  • 5,571 views
Uploaded on

by: deqode.com …

by: deqode.com

More in: Technology , Sports
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
5,571
On Slideshare
0
From Embeds
0
Number of Embeds
2

Actions

Shares
Downloads
582
Comments
0
Likes
10

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. 1Muhammad Azani Hasibuanmuhammad.azani@gmail.com
  • 2. Definition of SCRUMSCRUM ComponentsSCRUM Process
  • 3. Definition of SCRUMSCRUM ComponentsSCRUM Process
  • 4. simple complexknownuncertaintyPREDICTABLECOMPLICATEDCOMPLEXCHAOS
  • 5. simple complexknownuncertaintyPREDICTABLECOMPLICATEDCOMPLEXCHAOSAgileProjectStructuredProject
  • 6. The best way to optimize the predictabilityand control the risk is by employs aniterative and incremental approach.--SCRUM Guide
  • 7. SCRUM GUIDEA framework within which people can addresscomplex adaptive problems, while productivelyand creatively delivering products of the highestpossible value.Source: Ken Schwaber, SCRUM Guide
  • 8. Jan Feb Mar Apr Mei Jun Jul Aug Oct NovPlanningDesignCodingTestingReleaseReview
  • 9. Jan Feb Mar Apr Mei Jun Jul Aug Oct NovPlanningReviewDesignCodingTestingReleasePlanningReviewDesignCodingTestingReleasePlanningReviewDesignCodingTestingReleasePlanningReviewDesignCodingTestingReleaseITERATION #1 ITERATION #2 ITERATION #3 ITERATION #4
  • 10. Definition of SCRUMSCRUM ComponentsSCRUM Process
  • 11. ROLEProduct OwnerScrum MasterDevelopment TeamARTIFACTSProduct BacklogSprint BacklogIncrementEVENTSSprint PlanningDaily SCRUMSprint ExecutionSprint ReviewSprint Retrospective
  • 12. Product Owner SCRUM Master Development Team
  • 13. Define features/Product BacklogPrioritize features/ Product BacklogPick release datesGive feedbackManage stakeholdersAccept or reject results Product Owner
  • 14. Define tasksEstimate effortDevelop product CollaborativelyEnsure qualityEvolve processesDevelopment Team
  • 15. Remove impedimentsPrevent interruptionsFacilitate the teamSupport the processEnsuring SCRUM is undestood and enactedSCRUM MasterKeep the team fully productive
  • 16. Definition of SCRUMSCRUM ComponentsSCRUM Process
  • 17. SPRINTPLANNINGSPRINTEXECUTIONSPRINTREVIEWSPRINTRETROSPECTIVESPRINT/ ITERATIONDAILYSCRUM
  • 18. SPRINTPLANNINGDAILYSCRUMSPRINTREVIEWSPRINTRETROSPECTIVESPRINT/ ITERATIONProduct Owner• An ordered list of requirement• Potential features of the product• The single source of truth for what is planned inthe product• Public and available
  • 19. DAILYSCRUMSPRINTREVIEWSPRINTRETROSPECTIVESPRINT/ ITERATIONSubset ofProduct BacklogSPRINTPLANNING4 hours for 2 weeks sprint /8 hours for 4 weeks sprintProduct Owner, SCRUM Master, and Dev. Team•Estimate the complexity of each productbacklog item (PBI)•Negotiate the scope of PBI to PO•Decompose each product backlog items intotasks (called sprint backlog)Subset of product backlogSprint backlog, Sprint Goal
  • 20. SPRINTPLANNINGSPRINTREVIEWSPRINTRETROSPECTIVESPRINT/ ITERATIONSprint Backlog15 minute ( in the early day)SCRUM Master, and Dev. Team• Create a plan for the next 24 hours• Assess progress toward the SprintGoal• By the Development Team, for theDevelopment Team)Progress in previous daySPRINTEXECUTIONDAILYSCRUM
  • 21. SPRINTPLANNINGSPRINTREVIEWSPRINTRETROSPECTIVESPRINT/ ITERATIONSprint Backlog2-4 weeksSCRUM Master, and Dev. TeamImplement the sprint backlogSprint BacklogSPRINTEXECUTIONDAILYSCRUMIncrement
  • 22. SPRINTRETROSPECTIVESPRINT/ ITERATIONSprint BacklogSPRINTPLANNINGSPRINTEXECUTIONDAILYSCRUMPO, SCRUM Master, and Dev. Team• No Slides• Show the increment• Get Feedback form Product OwnerIncrement Of Software2 hours for 2 weeks sprint/4 hours for 4 weeks sprintFeedback from Product OwnerSPRINTREVIEWIncrement
  • 23. SPRINTPLANNINGSPRINTREVIEWIncrementSPRINT/ ITERATIONSprint BacklogSPRINTEXECUTIONDAILYSCRUMSCRUM Master, and Dev. Team• Identify what worked well• Identify what could be improved• Find the actionable improvementsFeedback from PO & Experiences2 hours for 2 weeks sprint/4 hours for 4 weeks sprintFuture ImprovementsSPRINTRETROSPECTIVE
  • 24. SPRINTPLANNINGSPRINTREVIEWIncrementSPRINT/ ITERATIONSPRINTEXECUTIONDAILYSCRUMSPRINTRETROSPECTIVE
  • 25. ROLEProduct OwnerScrum MasterDevelopment TeamARTIFACTSProduct BacklogSprint BacklogIncrementEVENTSSprint PlanningDaily SCRUMSprint ExecutionSprint ReviewSprint Retrospective
  • 26. • Schwaber, Ken & Jeff Sutherland (2011), The Scrum Guide, scrum.org•Joshua Partogi (2012), The Scrum Fundamental Course, scrumway.co