1 / 6

How to be a stronger DevOps leader: 9 tips

Want to lead your DevOps team to new heights? IT leaders and DevOps experts share steps to take in the realms of talent, measurement, vision, and IT culture. Get DevOps Training by best industrial experts.

sudamjena
Télécharger la présentation

How to be a stronger DevOps leader: 9 tips

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. 9Tips Howto Bea Stronger DevOps Leader Address:- PhNo: +91-9704455959,9618245689 Flatno: 205, 2ndFloor, E-MailID :online@visualpath.in NILGIRIBlock,AdityaEnclave, https://www.visualpath.in Ameerpet, Hyderabad-16

  2. Want to lead your DevOps team to new heights? IT leaders and DevOps experts share steps to take in the realms of talent, measurement, vision, and IT culture 1. Make everyone accountable to shared goals SteveBurton, CDandDevOpsevangelist, Harness: "For HowdoyoumakeDevOpsgrowand onething, stopgivingpeople 'DevOps' titlesand thrivewithinyourorganization? We expectingthattomagicallyincreaseyourreleasecycles. recentlylookedatthespecial It'saboutmakingpeopleawareofthebusinessobjectives andgivingthemaccountabilityforsharedgoals. Got traditionsandmeaningfulritualsthat Developers? Makethemresponsibleforhowtheirown rallypeoplearoundagilewaysof codeactsinproduction. GotOps? Findawayforthemto working. Buteventhebestbreakfast spendtheirtimeotherthanhunchingoveraconsoleand overseeingeachrelease. tacoswon’tmakeadifferenceifyou don’thaveasolidstrategyinplaceto Forbothofthem, aligntheircompensationtobusiness scaleDevOpsinyourorganization. outcomes. WhenitcomestoDevOps, it'sdeeds, not words – andhiring100peoplewith ‘DevOpsEngineer’ titleswithoutsharedgoals, accountability, and ITleadersandDevOpsexpertstellus compensation-basedincentivesisalotlikeputting100 thatkeyconsiderationsaroundtalent, tiresonyourcarandexpectingittogofaster." Irishcompanylawrequiresthedirectorstoprepare measurement, vision, andITcultureare financialstatementsforeachfinancialperiodwhichgive therealsecretstotakingDevOpsto atrueandfairviewofthestateofaffairsofthecompany thenextlevel. Herewesharenineof andoftheprofitorlossofthecompanyforthatperiod. theirbesttipsforITleaders. Digin, and Thedirectorsconfirmthattheyhavecompliedwiththe thenshareyoursinthecomments aboverequirementsinpreparingthefinancial statements.  below. https://www.visualpath.in 02

  3. 2. Cut the jargon Fin Goulding, international CIO, Aviva: 4. Move from project to product mindset  "Iwouldrecommendde-jargonizingthe CarmenDeArdo, DevOps technicallanguagethatunderpins leader, Nationwide: "Thesummitofthe DevOpsasmuchaspossible. Instead, DevOpsjourneyisforteamstoreduce focusonthebusinessoutcomesthatwill leadtimeanddelivermorefrequentlyto bedelivered - especiallyifoneislooking bemoreresponsivetotheirbusiness. This foranincreaseininvestmentorto isnotsomethingthatITcanachieveina expandDevOpsacrossawiderselection vacuum. That'swhyIbelievetheconcept ofbusinessandtechnicalteams. Iprefer ofmovingfromaprojecttoproduct- thetermFlowTeamsratherthanDevOps centricmodelisnecessary – whereITis 2.0. Ifundamentallybelievethatthese notseenasacostcenterbutratherafull holisticteamswillbeattheheartofthe partnerworkingwiththebusinessto mostsuccessfulworkplacesofthefuture." acceleratetheflowofdeliveryacrosstheir end-to-endproductvaluestreams." 3. Measure wisely and choose the middle path MircoHering, APACDevOpsandagile lead, Accenture: "First, makesureyou understandwhatsuccessisandhowitis beingmeasuredsothatyoucansee progress. Second, don’tgetdeterredby theincreasinglyevangelistsolution providersandfocusonincremental improvements. EverythinginDevOpsis aboutthemiddlepath – don’tlooktoofar out, butdon’tbeshortsighted; don’tbe toopuristbutdochallengethestatus quo; don’tputalltrustintechnology, but supportyourtransformationwith technology." https://www.visualpath.in 03

  4. 5. Balance soft and technical skills on DevOps teams RobertReeves, CTO, Datical: "ThegoalofDevOpsteamleadersistoenhancetheway organizationsthink, live, andbreathe. Giventhecritical environmentinthemodernenterprisein whichDevOpsprofessionalsareplacedwithintheirorganizations, leadersmustemploythe followingsoftandtechnicalskillsinordertotakeDevOpstothenextlevel: Soft Skills: Oftendismissedinhighlytechnicalteams, itisworthmorethanasmallfootnotethatsoftskills forDevOpsprofessionalsarekeytotheorganization'scultureshift. Softskillsinclude: Adeptwrittenandoralcommunication: Itisimperativethebreadthofknowledgeobtainedby DevOpsengineersisdocumentedandsharedsuccinctly. ThisinvolvestheuseofprivateWikis, issuestrackers, andad-hocbrown-bagsessionstofullyleveragetheinsightsoffellowteam membersandrelaypertinentinformation. Collaborative: Whenthinkingofcollaboration, mostpeoplepictureasmallgroupinaroom staringdownawhiteboard. ForDevOpsengineers, thiscanbethecase, butofteninvolvesahost ofotherskillswhichrelyonleveragingtechnologytoautomatethecollaborativeeffortsforyou. ThinkutilizingchatbotspopularizedbyHipChatandSlacktonotifyateamwhentoolstheyrely onareoutofserviceorleveragingincidentreportsandretrospectivestouncoverfailureswithin process, governance, and/orpolicy. Customer-firstmindset: WhileDevOpsengineerstypicallyarenotexternal-facingroles, their customers (developers, QA, customersuccess, projectmanagement, andbusinessleaders) are theirclients. Whenjugglingrequestsfromoperations, development, andproductteams, the abilitytoempathize, prioritize, andbetransparentarekeytosuccessfulrelationships. Technical Skills:  Itisimperativetocomearmedwithastrongtechnicalfoundationandtheabilitytoworkswiftly inhigh-techenvironmentstofindanswerstosometimesfrustratingissues. Technicalskills include: Systemadministrationandengineering: DevOpsengineersoftendeepdiveintosystemlayers, likeOSImodelforexample. DevOpsengineersshouldbewell-acquaintedwithbuildingand administeringLinuxandWindowsserversandthevariousnetworkstheyworkwithin. Scripting: Likesomanytechenvironments, akeyelementofDevOpsisautomation. Alotofthe manualtasksperformedbymoretraditionalsystemadministratorandengineeringrolescanbe automatedbyusingscriptinglanguageslikePython, Ruby, Bash, Shell, Node.js. Thiswillensure consistentperformanceofmanualtasksbyremovingthehumancomponentandallowingteams tospendthesavedtimeonmorethebroadergoalsoftheteamandcompany. Configurationmanagementtoolbelt: Whendealingwithmultipleserversspreadacrossmany datacentersorcloudserviceproviderspairedwiththeneedtoperformkernelupdates, modify networksettings, securelymanageSSHkeys, andupdatetoolingusedbydevelopersandQA, howdoesaDevOpsengineermanageitall? Configurationmanagementtoolsaretheanswer. Identitygovernance: A keyelement ofDevOpsengineeringsuccessismanagingaccess requirementsofallfunctionalteams, especiallyasitrelatestosystemsandservicesusedbythe developmentteam. Havingagriponwhocanaccesskeysystemsanddatanotonlyensuresa criticallevelofdataanappsecurity, butmoreoftenthannotleadstoincreaseduserproductivity andmoreefficientmanagementoftools. ToolslookedtofacilitatethisareSSHkeys, RDP, rdesktop, andLDAPtonameafew." https://www.visualpath.in 04

  5. 8. Beware of innovation teams 6. Don't let alignment goals delay DevOps AndersWallgren, CTO, ElectricCloud: "Bewareof BenGrinnell, managingdirector, North creating 'innovationteams' forthesakeof Highland: "Don’tinvesttimeup-front company profile dothealignmentinparallelasyouover innovationthroughDevOps. Oftentimes, this tryingtogetalignmentonahypothesisat createsentitledgroupsofpeoplewhoareactually theseniorlevels. Youwillnevergetthere. disconnectedfromtherestofyourorganization, Startimplementingontheground, and andthosepeoplemaybequitelimitedintheir abilitytocreateorganizationalvalue. Thosewho communicatethesuccessesand aremostwillingandabletoadapttochange examplesofprogress. Pickactivitiesthat createthetransformationforotherstofollow. willgiveyoutheseexamplesearlyon. Therefore, myrecommendationsforleadersareto: Examples need to be: Designyourorganizationsothatyourproduct, development, andITOpsteamsshareownership Easyforseniorleaderstounderstand andresponsibilityofthesoftwaredeliverypipeline. Significantenoughforthemtonotice Getthemtoworktogethertotreatyourpipeline Relevantenoughforthemtoeasily likeaproduct. translatetoamuchbiggerareaofthe Createanenvironmentwhereyourteamscan business. easilycollectdataonspecificmetricsandKPIsfor Theotherthingthat’sessentialisavision deliveryperformance. Capturesignalsbetween orNorthStar. Definethedirectionof teamsandworkflowbottlenecks, andfocusonthe travel, don’tgetintothedetailofa valueandqualityofwhatyouaredelivering. destinationandtime – itwilltaketoolong Continuouslymandatethatteamsscrutinizetheir togetagreement. It’smoreimportantto valuestreamsinordertoincrementallyimprove startmovingwithsomethingthatiseasily overtime. Setshort-termgoalsforthemtotackle understoodandagreedupon. Thatthen thebiggestbottlenecksfirst. allowsleadershiptoassesshow Hiretalentandbuildacultureacrosstheentire somethingthatmightseemlikelotsof organizationwithonekeymindset: continuously fragmentedinitiativesareworking disrupttheorganizationbeforeourcompetition togethertomovetheorganizationinthe does." rightdirection." 9. Remember, "continuous" is a keyword 7. Tap into the energy of the organization EranKinsbruner, director, author, leadsoftware JonathanSmart, headofwaysof evangelist, Perfecto: "Remember, DevOpsmeans working, Barclays: "Aiki: Usetheenergyof havingafullyautomatedworkflowtodeliver theorganizationtodrivethechangeyou software. Thiscannothappenwithoutmature wanttosee. Startwiththenatural automationthatworks. Inthatregards, havingthe champions. Rewriteinternalstandards properflowbetweenthethreeCs – Continuous andprocesses. Internalauditsareyour Integration (CI), ContinuousTesting (CT), and friend." ContinuousDelivery (CD) isessential. Thetipfor successhereistohaveamatureCTthatcanglue thedevelopmentCIprocesswiththesoftware delivery (CD) pereachcodechange, daily. https://www.visualpath.in 05

  6. DEVOPSTRAINING INSTITUTEIN HYDERABAD ForDevOpsTrainingContactUs @9704455959/9989971070 https://www.visualpath.in 03

More Related