What is DevOps Assessment? <\/h5>\n\n\n\n
As you can imagine, it isn\u2019t an easy task to take on DevOps. Every company is built and organized differently. As such, integrating two separate departments isn\u2019t easy. For some companies it may even do more harm than good. The DevOps assessment is made to make sure that while a company is switching over to a DevOps style, that they are keeping in line with DevOps practices. This is to make sure that the company doesn\u2019t go off the rails while transitioning. The DevOps assessment is just a bunch of questions meant to be answered by different departments of a company. And based on the answers, the company can see if it\u2019s going through the transition properly, where it needs to go next, and if necessary, what it needs to fix. <\/p>\n\n\n\n
Now that you know what a DevOps assessment is for, let\u2019s go over what it\u2019ll ask of you <\/p>\n\n\n\n There are many DevOps assessments, but the one I will be going over is the Microsoft DevOps assessment. If you\u2019d like to access it, here\u2019s the link: <\/p>\n\n\n\n https:\/\/devopsassessment.net\/<\/span><\/a><\/p>\n\n\n\n Microsoft measures success by 5 categories: <\/strong><\/p>\n\n\n\n Every question the assessment will ask you is related to one of these. <\/p>\n\n\n\n The questions themselves are relatively straightforward but will most likely require multiple employees to fill one out, as they are all-encompassing of a company\u2019s structure and policies. <\/p>\n\n\n\n These are multiple choice questions, so you can pick as many choices as are accurate. <\/p>\n\n\n\n One of the questions is: <\/strong><\/p>\n\n\n\n How do you review code changes? <\/p>\n\n\n\n You would choose as many of these answers as applies. <\/p>\n\n\n\t\t Talk to our experts today & see how they can help to fulfill your business objectives.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t <\/p>\n\n\n\n At the end of the assessment, which can take 20 \u2013 40 minutes based on if you pick the short or the long one, you will be given a review of how you\u2019ve answered each question. Along with a couple visual charts like these: <\/p>\n\n\n\n Under each answer you\u2019ve chosen, it will show all the answers you didn\u2019t choose. The unchosen answers will be listed in order of importance, so let\u2019s say you\u2019ve answered that example question, and the results show you this: <\/p>\n\n\n\n We review code changes infrequently We do live peer reviews or pair programming Some code is reviewed, and we capture the review history using a pull request workflow or the equivalent. We make sure all code changes are peer-reviewed before being committed to the master or trunk by means of a pull request workflow or the equivalent. <\/p>\n\n\n\n This means that, from the bottom up, you should be integrating the unchosen answers into your company practices. <\/p>\n\n\n\n And it\u2019s just that simple. To get started, simply grab a handful of employees from all the different departments of your company and take this assessment. Here\u2019s the link again if you need it: <\/p>\n\n\n\n![\"What](\"https:\/\/devon.nl\/wp-content\/uploads\/2021\/02\/assess-banner-diagram.png\")
<\/figure>\n\n\n\nQuestions<\/strong> <\/h5>\n\n\n\n
Ready to automate dev & ops to shorten the SDLC? <\/h2>\t\t\t\t<\/div>\n\t\t\t\t
Results<\/strong> <\/h5>\n\n\n\n
![\"What](\"http:\/\/ismiletechnologies.com\/wp-content\/uploads\/2021\/09\/image-35.png\")
<\/figure>\n\n\n\n![\"What](\"http:\/\/ismiletechnologies.com\/wp-content\/uploads\/2021\/09\/image-36.png\")
<\/figure>\n\n\n\nHow do you review code changes?<\/strong> <\/h5>\n\n\n\n