O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

Agile beyond Scrum: From concept to high performance

589 visualizações

Publicada em

A new approach to Agile adoption.
Choosing the correct Agile methods for your Agile adoption makes it easier to transform the culture of the organization.

Publicada em: Software
  • Seja o primeiro a comentar

Agile beyond Scrum: From concept to high performance

  1. 1. AgileBeyondScrum Agile:FromConcepttoHighPerformance
  2. 2. whoisthisguy? andersonmouriques@gmail.com linkedin.com/in/andersonmouriques @aouriques ANDERSON MACHADO OURIQUES Software Development Manager ● Over 15 years of experience in Software Development ○ 1 year of software development for desktops ○ 8 years of software development for web ○ 6 years of management Certified
  3. 3. MyElePHPants
  4. 4. AgileManifesto - Values Individualsandinteractions overprocessesandtools WorkingSoftware overcomprehensivedocumentation CustomerCollaboration overcontractnegotiation RespondingtoChange overfollowingaplan
  5. 5. AgileManifesto - Principles ● Ourhighestpriorityistosatisfythecustomerthroughearlyandcontinuousdeliveryofvaluablesoftware. ● Welcomechangingrequirements,evenlateindevelopment.Agileprocessesharnesschangeforthecustomer'scompetitiveadvantage. ● DeliverWorkingSoftwarefrequently,fromacoupleofweekstoacoupleofmonths,withapreferencetotheshortertimescale. ● Businesspeopleanddevelopersmustworktogetherdailythroughouttheproject. ● buildprojectsaroundmotivatedindividuals.Givethemtheenvironmentandsupporttheyneed,andtrust themtogetthejobdone. ● Themostefficientandeffectivemethodofconveyinginformationtoandwithinadevelopmentteamisface-to-faceconversation. ● Workingsoftwareistheprimarymeasureofprogress. ● Agileprocessespromotesustainabledevelopment.Thesponsors,developers,andusersshouldbeabletomaintainaconstantpace indefinitely. ● Continuousattentiontotechnicalexcellenceandgooddesignenhancesagility. ● Simplicity-theartofmaximizingtheamountofworknotdone-isessential. ● Thebestarchitectures,requirements,anddesignsemergefromself-organizingteams. ● Atregularintervals,theteamreflectsonhowtobecomemoreeffective,thentunesandadjustsitsbehavioraccordingly.
  6. 6. ● ExtremeProgramming ● Scrum ● Kanban ● ScrumBan ● FeatureDrivenDevelopment ● LeanSoftwareDevelopment ● DynamicSystemsDevelopmentMethod AgileMethods ● AgileUnifiedProcess ● CrystalClear ● RapidApplicationDevelopment ● AgileModeling ● AdaptiveSoftwareDevelopment ● DisciplinedAgileDelivery ● BusinessAnalystDesignerMethod
  7. 7. ExtremeProgramming AgileMethods:Theories,PrinciplesandCoreValues Transparency Inspection Adaptation Openness Focus Courage Commitment Respect Scrum Transparency Balance Agreement Respect Understanding Leadership CustomerFocus Flow Kanban Collaboration Simplicity Courage Respect Communication
  8. 8. ExtremeProgramming AgileMethods:Theories,PrinciplesandCoreValues Transparency Inspection Adaptation Openness Focus Courage Commitment Respect Scrum Transparency Balance Agreement Respect Understanding Leadership CustomerFocus Flow Kanban Collaboration Simplicity Courage Respect Communication
  9. 9. PDCA(Plan-Do-Check-Act)
  10. 10. ExtremeProgramming(XP)
  11. 11. XP Practices
  12. 12. Kanban-TaiichiOhno(TOYOTA) Bottlenecks WIPLimit Visibility
  13. 13. ValueStreamMap(example)
  14. 14. MinimumViableProduct
  15. 15. Scrum-Whatisit? Aframeworkwithinwhichpeoplecanaddress complexadaptiveproblems,whileproductivelyand creativelydeliveringproductsofthehighest possiblevalue.
  16. 16. Scrum-AnotherAgileFramework
  17. 17. Scrum
  18. 18. Scrum-PigsAndChicken
  19. 19. TheProductOwneristhesolepersonresponsiblefor managingtheProductBacklog: ● ClearlyexpressingProductBacklogitems; ● OrderingtheitemsintheProductBacklogtobestachievegoalsandmissions; ● OptimizingthevalueoftheworktheDevelopmentTeamperforms; ● EnsuringthattheProductBacklogisvisible,transparent,andcleartoall,and showswhattheScrumTeamwillworkonnext;and, ● EnsuringtheDevelopmentTeamunderstandsitemsintheProductBacklogtothe levelneeded. ScrumRoles-ProductOwner
  20. 20. “fromtheshortlistofthingsateamneedsaproductownertobe: businessvaluedriver,visionkeeper,dailydecisionmaker,heat shield,andtheoneultimatelyresponsible.” LyssaAdkins ScrumRoles-ProductOwner
  21. 21. TheScrumMasterisresponsibleforensuringScrumis understoodandenacted.ScrumMastersdothisby ensuringthattheScrumTeamadherestoScrum theory,practices,andrules.TheScrumMasterisa servant-leaderfortheScrumTeam. ● Coach ● Facilitator ● GuardianofQualityandPerformance ● RemoveImpediments ScrumRoles-ScrumMaster ● Scrum/AgileVoiceToAll ● FocusedinProductivity ● BuildHighPerformanceTeams
  22. 22. TheDevelopmentTeamconsistsofprofessionalswho dotheworkofdeliveringapotentiallyreleasable Incrementof“Done”productattheendofeach Sprint. ● Self-Organized ● Cross-Functional ● Developers(notitles) ● Accountable ScrumRoles-Team ● Commitment ● Focus ● SkilledMembers
  23. 23. ScrumArtifacts-ProductBacklog Themes Epics UserStories
  24. 24. ScrumArtifacts-SprintBacklog
  25. 25. ScrumArtifacts-IncrementorBurn-Down/UpChart
  26. 26. ScrumEvents-TheSprint ● Timeboxedfrom1to4weeks ● NochangesaremadethatwouldendangertheSprintGoal; ● Qualitygoalsdonotdecrease;and, ● Scopemaybeclarifiedandre-negotiatedbetweentheProduct OwnerandDevelopmentTeamasmoreislearned.(Groomingor Refinement)
  27. 27. ● Timeboxedto2hoursperweeksprint ● WhatcanbedeliveredintheIncrementresultingfromthe upcomingSprint?(Planning1) ● HowwilltheworkneededtodelivertheIncrementbeachieved? (Planning2) ScrumEvents-SprintPlanning
  28. 28. ● Timeboxedto15minutesperday ● WhatdidIdoyesterdaythathelpedtheDevelopmentTeammeetthe SprintGoal? ● WhatwillIdotodaytohelptheDevelopmentTeammeettheSprint Goal? ● DoIseeanyimpedimentthatpreventsmeortheDevelopmentTeam frommeetingtheSprintGoal? ScrumEvents-DailyScrum
  29. 29. ● Timeboxedto1hourperweekSprint ● P.O.Presentswhatisdoneandwhatisnotdone ● DevTeamDiscusseswhatwentwell,whatproblemstheyfacedandhowthey solvedthem. ● TheDevTeamDemonstratestheworkdoneandanswersquestions. ● Groupcollaboratesonwhattodonext. ● BacklogRefinementandReviewofthetimeline,budget,Potential capabilities,andmarketplaceforthenextanticipatedrelease ScrumEvents-SprintReview
  30. 30. ● Timeboxedto45minutesperweekSprint ● InspecthowthelastSprintwentwithregardstopeople,relationships, process,andtools; ● Identifyandorderthemajoritemsthatwentwellandpotential improvements;and, ● CreateaplanforimplementingimprovementstothewaytheScrumTeamdoes itswork. ScrumEvents-SprintRetrospective
  31. 31. ScrumEstimation PlanningPoker T-ShirtSize ● IdealDays ● StoryPoints ● Delphi
  32. 32. AgileProcess http://knowledge21.org
  33. 33. Whatelse? Business LeanStartup P.O.Techniques Organization LeanKanban Management3.0 Leadership ScalingAgile Team Facilitation Leadership LeanKanban Technique Automated Tests Continuous Delivery Object Orientedhttp://knowledge21.org
  34. 34. AgilityHealthRadar http://agiletransformation.com/

×