Transcription
Agile testing andDevOpstechniquesBlueOceanWorkshops.com
Agenda: How Agile testing fits Agile Manifesto Best methodology for Agile Scrum testing What is DevOps DevOps optimization
Agile Manifesto: Individuals and interactions over processes and tools Working software over comprehensivedocumentation Customer collaboration over contract negotiation Responding to change over following a planAgile Principles: Simplicity–the art of maximizing the amount ofwork not done–is essential.Source: https://agilemanifesto.org
Agile Scrum methodologyProjectInitiationSprint 0Sprint 1Sprint 2Sprint nProjectClose
Why most Agile Scrum fail?Sprint 1UX designSp1CodedevelopmentSp1QA testingSp1Sprint 2Release Sp1UX designSp2CodedevelopmentSp2QA testingSp2Release Sp2
Slide 5AS1Andrew Soswa, 11/8/2018
Best Agile Scrum strategy – ‘waterfall’ SprintsSprint nUX designSp1Sprint n 1Sprint n 2Arch 0ArchCode devQA testingSp2Sp1
Agile testing retrospective lessons Full end-to-end product testing is seldomlycompleted on Agile projects Most testing is based on risk-driven testingscenarios There is limited time to coach junior QA QA tests the biggest impact/risk of failure in theproduct/serviceFast pace of Agile (not only in Scrum) depends onknowledgeable, self-managing individualsThe entire team owns the quality QA team is not the last team holding ‘hot potato’before product/service is deployed to production
DevOps
DevOps misconceptions Is it a simple migration process or a tool? A fancy name for your development team? A team with a fancy name taking overdevelopment & testing? A fad that blows over in no time?
Let’s ponder project deployment realityDeploymenttime!Wonder what’scoming thistime!*&@#
From humble beginnings Dated to early 2000’s EMS (EnterpriseManagement Systems) failures (andattempts at mitigating them) The official name was coined in 2009 byPatrick Debois and Andrew “Clay” Shafer Officially kicked off by Debois when he heldthe first DevOpsDays event in 2009
Let’s discover (not-so-novel) ideaWhat about if we: Have a support team that works onthe code/product to consistentlyautomate it Automate it to continuously improveproduct’s quality and deploymenttimeQADevOpsDevelopment Deploy it in time from project to operational phase onan established schedule Establish schedule of releases that supports businessobjectives Support business objectives as a support team
What role DevOps perform in an enterprise?
DevOps engineer job role at AmazonSource: s/job-roles/
Key DevOps role features Experience in various infrastructure,software, and network frameworks andtools Knowledge of development anddeployment methods Mindset to simplify and automatizeprocesses and working features
DevOps adoption in large enterprises
Automation benefits
How to start DevOps in any team Recognize that DevOps is: Business, technological, and a cultural changeNot owed by one team member/manager*Allow team to learn best practices in: Version control & monitoringContinuous buildAutomated testingOptimized deploymentProvisioning (seamless transitioning) Start small and consistently improve *unless there is a position created for that purpose
DevOps in Agile Scrum If possible, create a stand-alone DevOps role Otherwise, assign DevOps responsibilities tovarious team members Involve business andoperations teams Create User Stories andadd them to sprints If needed - createRelease Sprints
Use Team Retrospectives to improve 3 P’s:Project’s deliverables (product/service) People Processes Icons made by Freepik from https://www.flaticon.com
DevOps allow system improvementIncremental Agile failure waste Experimentation, failure, andimprovements are essential to creatinga meaningful changeActPlanExperimentCheckFailDoImprove
Three stages of Agility in DevOps Know AgileDo AgileBecome Agile
Relentlessly improveAgile is NOT something that youbecome Agile is something that youbecome more of
About the presenter:Andrew Soswa, PMP, CSM, PSM, PMI-ACP, AgileCoachLinkedIn: https://www.linkedin.com/in/andrewsoswaBlogs on www.blueoceanworkshops.comEmail: andrew@blueoceanworkshops.com
Nov 08, 2018 · Agile testing retrospective lessons Full end-to-end product testing is seldomly completed on Agile projects Most testing is based on risk-driven testing scenarios QA tests the biggest impact/risk of failure in the product/service There is limited time to coach junior QA Fast pace of Agile (not only in S
