《4、2023 DODPPT会场- Bart de Best(1).pdf》由会员分享,可在线阅读,更多相关《4、2023 DODPPT会场- Bart de Best(1).pdf(42页珍藏版)》请在三个皮匠报告上搜索。
1、DevOps Assessment Case Study欧洲政府机构的DevOps持续评估案例Bart De Best 2023 China DevOpsDays-8月12日 北京-Continuous Assessment(CS)Continuous Assessment(CS)Case studyBeijing DevOps days12 August 202340 minBart de BestCS case studyCS case studyAgenda My background My background(1 min)What is CS about?What is CS abo
2、ut?(5 min)The case study organisation The case study organisation(1 min)The goals The goals(3 min)The steps The steps(3 min)The results The results(10 min)The lessons learned The lessons learned(3 min)Q&A Q&A(4 min)IT industry since 1985IT industry since 1985 DevOps since 2013DevOps since 2013CS cas
3、e studyCS case studyBackground DevOps Trainer DevOps Examiner DevOps Coach DevOps AuthorDevOps ConsultantDevOps ArchitectCS case studyCS case studyService Management PublicationsCS CS case studycase studyThe originationDevelopmentDevOperationsOpsDevOpsCS CS case studycase studyThe originationCEConti
4、nuous EverythingCICTCNCPCDCMCLCS case studyCS case studyCE Publications 2021/2022CS case studyCS case studyCE PublicationsAll books have the same structure:All books have the same structure:-Concepts and definitionsConcepts and definitions-5 times why5 times why-Change paradigmChange paradigm-Archit
5、ecture models and Architecture models and principlesprinciples-CE Best practicesCE Best practices-List of terms and explanationList of terms and explanationCS case studyCS case studyBackground My background My background What is CS about?What is CS about?The case study organisation The case study or
6、ganisation The goals The goals The stepsThe steps The resultsThe results The lessons learnedThe lessons learned Q&AQ&ACS CS case studycase studyThe scope(green)CP=Continuous PlanningCN=Continuous DesignCT=Continuous TestingCI=Continuous IntegrationCD=Continuous DeploymentCM=Continuous MonitoringCL=C
7、ontinuous LearningCY=Continuous SecurityCQ=Continuous SLACA=Continuous AuditCS=Continuous AssessmentPossible future CXs:CR=Continuous RoboticsCC=Continuous AcceptanceCO=Continuous Documentation“CX”refers to all CE aspects Scope CS AssessmentCSCScase studycase studyThe maturity axisThe flow is undefi
8、ned,but minimal DevOps capabilities are in place to perform basic operations.1The flow is defined to support the value stream in a fixed work sequence.2The entire flow is supported by an integrated and automated E2E pipeline.3The flow in the pipeline is measured based on predefined quality criteria.
9、4The flow is integrated in the business flow and the flow of external parties in the chain.5 Ad Hoc Repeatable ConsistentQuantitativelyOptimizingCSCScase studycase studyThe topic axis DevOps Data DevOps Control DevOps Strategy DevOps QualityDevOps MethodologyDevOps Management12345QualityDataManageme
10、ntStrategyControl Mechanism/Tools12345ContinuousEverythingAd hocRepeatableConsistentQuantitativelyOptimizingMethodologyCSCScase studycase studyThe questionnairestructureCSCScase studycase studyAn exampleOwnToolingSprint planningManualPlanningGivenPrioritiesPlanning toolDefinedPlanningobjectsShared P
11、lanningRepositoryDoR andDoR12345Product backlogManagementQualityDataManagementStrategyControl Mechanism/ToolsDesignToolIntegration12345Planning Meta DataProductRoadmapManualRecordsRelease planningManagementOne Rhythmfor planningDeploymentToolIntegrationRepository tool IntegrationEffective Acceptance
12、PlanningmonitoringPlanning synchronizedAcross chained DevOps teamsKPI Trend MeasurementIntegrated DashboardsCP Monitor informationPlanningDeviationRecordsRoadmapManagementPlanning conformDefined architectureDirectionContinuousPlanningSystem Building BlocksIST,SOLL,Migration PathPlanning ConformBalan
13、ced ScorecardPlanningRecordsAd hocRepeatableConsistentQuantitativelyOptimizingSprintGoalMethodologyLate FeedbackMVPManagementAuditabilityMeasurableVelocityBurn Down/UpChartsReliableForecastEpic OnePagerBalanced ScorecardStrategic Planning BoardReleaseplanningProductVisionIntegratedRelease planLocalR
14、epository#SubjectQuestionAnswerScore Extra questionAnswerEvidence Need Y/NEvidence ReferenceCM-L1-01Manual monitoringDo monitoring activities take place(manually or automated)e.g.,for Central Processing Unit(CPU),memory and network bandwidth utilisation?YesWhich tool?CM-L1-02Monitoring toolsHas a me
15、thod of monitoring been established,whether or not per object type?-See monitorlagenmodelYesWhich methods?CM-L1-03Integrated monitoringDoes monitoring take place in all the D-T-A-P environment regardless of whether or not they differ?YesWhich of the D-T-A-P?CM-L1-04Ad hoc monitoringDoes monitoring t
16、ake place continuously or not?YesWhat is the frequency?CM-L1-05Basic eventsAre events monitored(all or only the exceptions)?YesLogfilesTraps(SNMP traps)Which event types are collected?-Informational-Warnings-ExceptionsLevel 1:Ad Hoc CSCScase studycase studyThe questionnaireThe CS toolbox offers a sp
17、readsheet per CXAt least one questions per level per topicScore for Yes,No,Y/NAutomatic calculation of the maturity on a dashboardCSCScase studycase studyThe experienceThe CS toolbox is used for:1.A training for the lead engineers of a large bank in the Netherlands2.Building a CE academy for one of
18、the suppliers of Netflix3.An aid during DevOps consultancy4.Exercises in CE trainings5.Writing the CE books including Continuous Assessment6.Enrichment of the DevOps Professional and DevOps master trainings7.Two audits for Chinese organisationsPlanned to use the CS toolbox for:1.Certification of Dev
19、Ops professionals2.Certification of DevOps teams3.Certification of DevOps organisation4.Tenders5.Body of KnowledgeCS case studyCS case studyBackground My backgroundMy background What is CS about?What is CS about?The case study organisation The case study organisation The goals The goals The steps Th
20、e steps The resultsThe results The lessons learnedThe lessons learned Q&A Q&A CS case studyCS case studyThe organisation European governmentEuropean government#teams=3#teams=3#employees=30#employees=30For privacy reasons:No name is sharedNo details are sharedNo results are sharedFor case study reaso
21、ns:The approach is sharedThe results are anonymizedCS case studyCS case studyBackground My background My background What is CS about?What is CS about?The case study organisationThe case study organisation The goals The goals The stepsThe steps The resultsThe results The lessons learnedThe lessons le
22、arned Q&AQ&ACS case studyCS case studyThe goals Fun,energy,improvementFun,energy,improvement Learn DevOps practicesLearn DevOps practices Measure where we areMeasure where we are Fill and prioritise the Fill and prioritise the technical debt backlogtechnical debt backlog Create the roadmap for Creat
23、e the roadmap for short and long termshort and long term Anchor CE growth in the Anchor CE growth in the organisationorganisationCS case studyCS case studyBackground My backgroundMy background What is CS about?What is CS about?The case study organisationThe case study organisation The goals The goal
24、s The stepsThe steps The resultsThe results The lessons learnedThe lessons learned Q&AQ&ACS case studyCS case studyThe stepsTraining:Training:2 CE trainings2*15 employees 2*3 daysAssessments:Assessments:8 CE assessments2 employees per assessmentOff site days:Off site days:2 CE off site days2*15 empl
25、oyeesFollow up:Follow up:Management commitmentInvolve more teams,train and coach teamsPlan new assessmentetcCS case studyCS case studyBackground My background My background What is CS about?What is CS about?The case study organisation The case study organisation The goals The goals The stepsThe step
26、s The resultsThe results The lessons learnedThe lessons learned Q&A Q&A CS case studyCS case studyThe results(anonymized)CE-CPCE-CNCE-CTCE-CICE-CDCE-CMCE-CLCE-CYLevel 500055000Level 455059506140Level 33825268080272581Level 279895Level 008681100CP=Continuous PlanningCN=Continuou
27、s DesignCT=Continuous TestingCI=Continuous IntegrationCD=Continuous DeploymentCM=Continuous MonitoringCL=Continuous LearningCY=Continuous Security=80%=20%80%20%Yes=2 pointsY/N=1 pointNo=0 pointsScore is%of max pointsper CX per levelCS case studyCS case studyThe results(anonymized)12345OwnToolingAnno
28、tationDesignReviewSourceCode TagsEmergingDesignLate FeedbackTDDDesign toolDefinedDesignobjectsDoR andDoRDesignOwnershipBDDDesign enablesFit for use andFit for purposeUnitTestCasesGWTShared DesignRepositoryPlanningToolIntegrationUse CaseAutomationDomain DesignApprovalUse CaseDiagramDeploymentToolInte
29、grationRepository tool IntegrationDesignTraceabilityAuditabilityUse CasesDesign ConformArchitecture Principles and modelsValueStreamMappingVersioningDesign IntegritymonitoringDesign SynchronizedAcross Chained DevOps TeamsBuildingBlockMeta dataDesign Conform Solution ArchitectureSystem Building Block
30、sValue Stream CanvasDesignRecordsChain DesignAuthorityMeasurableDesign QualityIntegratedDesignKPI Trend MeasurementIntegrated DashboardsCN Monitor informationDesign ConformReference ArchitectureSystem Context DiagramStrategic Design Approval BoardCS case studyCS case studyThe results(anonymized)OwnT
31、oolingTDDAnnotationDesignReviewDesign toolDefinedDesignobjectsShared DesignRepositoryDoR andDoR12345DesignOwnershipQualityDataManagementStrategyControl Mechanism/ToolsPlanningToolIntegration12345Use CaseAutomationSourceCode TagsDomain DesignApprovalUse CaseDiagramDeploymentToolIntegrationRepository
32、tool IntegrationDesignTraceabilityDesign IntegritymonitoringDesign SynchronizedAcross Chained DevOps TeamsKPI Trend MeasurementIntegrated DashboardsCN Monitor informationBuildingBlockMeta dataDesign Conform Solution ArchitectureContinuousDesignSystem Building BlocksValue Stream CanvasDesign ConformR
33、eference ArchitectureDesignRecordsAd hocRepeatableConsistentQuantitativelyOptimizingEmergingDesignMethodologyLate FeedbackChain DesignAuthorityAuditabilityMeasurableDesign QualityIntegratedDesignUse CasesSystem Context DiagramStrategic Design Approval BoardBDDDesign ConformArchitecture Principles an
34、d modelsDesign enablesFit for use andFit for purposeUnitTestCasesValueStreamMappingGWTVersioningCS case studyCS case studyThe off site days Low hanging fruit 3 months Per CX 2 persons Define the top 3 improvement:Business caseSize in feature/story#sprint lead timeAcceptance criteria High hanging fru
35、it 9 months Per CX 2 persons Define the top 3 improvement:Business caseSize in epic/theme#sprint lead timeAcceptance criteriaLowHighHighHigh45 min.break-out and 45 min sharingCS case studyCS case studyThe off site daysMeasure and Manager-(F)DevOps quick-scan-(G)DevOps maturityContinuous Improvement-
36、(J)Plan-Do-Check-Act-(K)Technical debt-(L)LeanAgile project-(H)Agile Scrum-(I)Continuous PlanningChange Management-(A)The Three Ways-(B)Kotter-(C)Organisation alternatives-(D)Change paradigm-(E)Obeya roomVisionGoalsOrganisationContinuum45 min.break-out and 45 min sharing Group exercise Select 4 inst
37、ruments 4 teams of 3-4 people Each one instrument Visualize the usage Deliver:Visualisation Example PresentThe group selected:-Kotter-Lean-Change paradigm-Obeya roomThey agreed upon to use all in their journeyCS case studyCS case studyBackground My backgroundMy background What is CS about?What is CS
38、 about?The case study organisationThe case study organisation The goals The goals The stepsThe steps The resultsThe results The lessons learnedThe lessons learned Q&AQ&ACS ToolboxCS ToolboxLessons learned in the last 5 years EnergyEnergy Eager,open and honestEager,open and honest EmpowermentEmpowerm
39、ent Terminology is keyTerminology is key TimelineTimeline Share more existing knowledgeShare more existing knowledge Toxic CultureToxic Culture Create a devops academyCreate a devops academy Determine ownershipDetermine ownershipCS ToolboxCS ToolboxEnergy People cant wait to fill in the questionnair
40、e Having fun during the interview Liking to hear what they already achieved Are proud of their scoresCS ToolboxCS ToolboxEnergyCS ToolboxCS ToolboxEager,open,honest People are eager to seek where they have examples of fulfilling the CE measure People are open during the questions They tell the truth
41、CS ToolboxCS ToolboxEager,open,honestCS ToolboxCS ToolboxEmpower During the roadmap sessions people ask for empowerment to accomplish the goals set Product owners sometimes complain that they have to give away velocity percentages to everybody Product owners often give 10%of the velocity as an inves
42、tment to learn new ways of working and actually improve what is on the technical debt backlogCS ToolboxCS ToolboxEmpowerCS ToolboxCS ToolboxMissing Terminology Terms used in the assessments areoften not understood Training is needed Use of a DevOps dictionary is neededCS ToolboxCS ToolboxMissing Ter
43、minologyCS ToolboxCS ToolboxTimeline Time between training and assessmentmay not be too long People forget concepts that are not yetpractices Plan the assessment as part of the training Split the assessments in blocks of 2 hours over max on month timeCS ToolboxCS ToolboxTimelineCS ToolboxCS ToolboxS
44、iloed Communication The exchange of information,knowledge&knowhow is not always 100%The reason is often the specialisms thatpeople still have(not E-shaped)Create guildsCS ToolboxCS ToolboxSiloed CommunicationCS ToolboxCS ToolboxToxic Culture Negative culture Not willing to learn Not invented here sy
45、ndrome Lack of leadership Forbid to use maturity scans,fearing for targets and obligation Negative leadership Publicly blame people for having technical debt Lack of investment and performance Not giving time to improve Deployment pain Not willing to join existing pipelinesCS ToolboxCS ToolboxToxic
46、CultureCS ToolboxCS ToolboxNo Academy No relationship with strategy No relationship with HR No learning building blocks No Academy Create an academy Create a set of ten learning building blocks for each CX including content,exams and certificates Define function and roles and bind them to certificat
47、esCS ToolboxCS ToolboxNo AcademyCS ToolboxCS ToolboxNo ownership The exchange of information,knowledge&knowhow is often partial There is a lack of evangelists,guilds etc for specific topics Make a team owner of a cell in the CE matrix Make a team owner of a learning build blockCS ToolboxCS ToolboxOw
48、ershipCS case studyCS case studyBackground My backgroundMy background What is CS about?What is CS about?The case study organisation The case study organisation The goals The goals The stepsThe steps The resultsThe results The lessons learnedThe lessons learned Q&AQ&AThanks感 谢 聆 听2023 China DevOpsDays-8月12日 北京-