├── LICENSE └── README.md /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | 178 | APPENDIX: How to apply the Apache License to your work. 179 | 180 | To apply the Apache License to your work, attach the following 181 | boilerplate notice, with the fields enclosed by brackets "[]" 182 | replaced with your own identifying information. (Don't include 183 | the brackets!) The text should be enclosed in the appropriate 184 | comment syntax for the file format. We also recommend that a 185 | file or class name and description of purpose be included on the 186 | same "printed page" as the copyright notice for easier 187 | identification within third-party archives. 188 | 189 | Copyright [yyyy] [name of copyright owner] 190 | 191 | Licensed under the Apache License, Version 2.0 (the "License"); 192 | you may not use this file except in compliance with the License. 193 | You may obtain a copy of the License at 194 | 195 | http://www.apache.org/licenses/LICENSE-2.0 196 | 197 | Unless required by applicable law or agreed to in writing, software 198 | distributed under the License is distributed on an "AS IS" BASIS, 199 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 200 | See the License for the specific language governing permissions and 201 | limitations under the License. 202 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # DevOps Onboarding Checklist 2 | 3 | ## About OSO DevOps 4 | 5 | We are a DevOps and Amazon Web Services (AWS) Professional Services 6 | Consultancy based in London. We build secure bespoke automated big data 7 | platforms on AWS using open source tooling, helping businesses to 8 | extract value from their data in the most cost effective and agile way. 9 | We provide self service tooling to enable business workflows to make 10 | data driven decisions. 11 | 12 | ## Our Approach To DevOps Onboarding 13 | This onboarding checklist contains sample activities that are good 14 | practices for onboarding application teams to utilise DevOps 15 | capabilities. Alter the checklist to reflect onboarding activities 16 | specific your company, and assign owners (e.g., Teams, Service Desk, Cloud 17 | Technical Team) for each activity. Once you have customized the 18 | checklist appropriately, provide it to the DevOps onboarding team to 19 | process and ensure accountability for completing necessary onboarding 20 | activities. 21 | 22 | ## Central DevOps Team 23 | There are many logistical and strategic components to onboard software 24 | development teams effectively. Yet, this critical stage often fails to 25 | receive the attention it warrants due to divided or unclear 26 | responsibilities and a lack of defined tasks and activities. Use this 27 | framework as a guideline for enrolling team into DevOps and improve and 28 | automate the process. 29 | 30 | ## Sample DevOps Onboarding Checklist 31 | ***Import:*** The team must be software development focused for the 32 | onboarding to proceed 33 | 34 | ## Product 35 | What is the current project vision and mission? 36 | 37 | 38 | 39 | 40 | 41 | 42 | 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | 52 | 53 | 54 | 55 | 56 | 57 | 58 | 59 | 60 | 61 | 62 | 63 | 64 | 65 | 66 | 67 | 68 |
Product Information Baseline
Name of Project
Product Vision
Product Lead
Product Members
Product Users
Product Duration
69 | 70 | ## Delivery Methodology 71 | What methodologies does the team use to deliver the software? 72 | 73 | 74 | 75 | 76 | 77 | 78 | 79 | 80 | 81 | 82 | 83 | 84 | 85 | 86 | 87 | 88 | 89 | 90 | 91 | 92 | 93 | 94 | 95 | 96 | 97 | 98 | 99 | 100 | 101 | 102 | 103 | 104 | 105 | 106 | 107 | 108 |
Delivery Frameworks used
FrameworkUsed
Jira
Trello
Confluence Space
Scrum
Kanban
Extreme Programming
109 | 110 | ## Software Language & Development Frameworks 111 | What languages and frameworks are the development team using to deliver the software? 112 | 113 | 114 | 115 | 116 | 117 | 118 | 119 | 120 | 121 | 122 | 123 | 124 | 125 | 126 | 127 | 128 | 129 | 130 | 131 | 132 | 133 | 135 | 136 | 137 | 138 | 139 | 140 | 149 | 150 | 151 | 152 | 153 | 154 | 163 | 164 | 165 | 166 | 167 | 168 | 180 | 181 | 182 | 183 | 184 |
Software product and environment Details
CategoryOptionsOwnerCompletion Date
Project Source Repository ExistGit / SVN / CVS
Programming languages

JavaScript / Python / Java / C/C++ /PHP / Swift

134 |

C# / Ruby / Objective-C /SQL

Development Platforms

Unkown / Linux / Windows

141 |

Android / AWS / MAC OS / iOS

142 |

Rasberry Pi / Firebase / Azure / Heroku

143 |

Arduino / Google Cloud

144 |

Serverless / Drupal / Amazon Echo

145 |

Salesforce / SAP

146 |

Apple Watch or TV / IBM Cloud or Watson

147 |

Google Home

148 |

Gaming console / Mainframe

Types of Software Development

Web Development

155 |

Mobile Development

156 |

Data Science

157 |

Application Development

158 |

Back-end Development

159 |

API Development

160 |

Embedded Systems Development

161 |

Security Software Development

162 |

Cloud Computing

Integrated Developer Environments

Atom / CLion / Cloud9 / Coda2

169 |

Code::Blocks / Codefresh / CodeLite

170 |

/ Eclipse / Eric Python IDE / Geany / Idle IDE

171 |

IntelliJ IDEA / JCreator / KDevelop

172 |

Komodo / Lazarus / Light Table

173 |

Microsoft Visual Studio IDE / Monkey Studio

174 |

MyEclipse / NetBeans IDE / Nuclide

175 |

NuSphere PhpED / PhpStorm / PyCharm

176 |

Qt Creator / RubyMine / SapphireSteel

177 |

Squad / Visual LANSA / Visual Studio Code

178 |

WebStorm / Xamarin / Xcode / Zend Studio

179 |

185 | 186 | ## Assigning Project Roles 187 | Who will be responsible for what in this project? 188 | 189 | 190 | 191 | 192 | 193 | 194 | 195 | 196 | 197 | 198 | 199 | 200 | 201 | 202 | 203 | 204 | 205 | 206 | 207 | 208 | 209 | 210 | 211 | 212 | 213 | 214 | 215 | 216 | 217 | 218 | 219 | 220 | 221 | 222 | 223 | 224 | 225 | 226 | 227 | 228 | 229 | 230 | 231 | 232 | 233 | 234 | 235 |
Assigned project roles
RoleAdditional InformationOwnerCompletion Date
Product OwnerThe Product Owner is the sole person responsible for managing the Product Backlog






236 | 237 | ## Validate Request 238 | Does the requesting team meet all of the onboarding requirements? 239 | 240 | 241 | 242 | 243 | 244 | 245 | 246 | 247 | 248 | 249 | 250 | 251 | 252 | 253 | 254 | 255 | 256 | 257 | 258 | 259 | 260 | 261 | 262 | 263 | 264 | 265 | 266 | 267 | 268 | 269 | 270 | 271 | 272 | 273 | 274 | 275 | 276 | 277 | 278 | 279 |
Onboarding Requirements
Project Name validComplete
Project Lead Valid
Project members valid
Valid software project
Development Platform Supported
Software Development type supported
IDE’s Supported
Programming Language Supported
280 | 281 | ## Supported DevOps pipeline 282 | The software which is being written by the development team 283 | 284 | 285 | 286 | 287 | 288 | 289 | 290 | 291 | 292 | 293 | 294 | 295 | 296 | 297 | 298 | 302 | 303 | 304 | 305 | 306 | 307 | 311 | 312 | 313 | 314 | 315 | 316 | 320 | 321 | 322 | 323 | 324 | 325 | 332 | 333 | 334 | 335 | 336 |
Supported software product and environment details
CategoryOptionsOwnerCompletion Date
Development Platforms

Linux

299 |

AWS

300 |

MAC OS

301 |

Serverless

Types of Software Development

Web Development

308 |

Application Development

309 |

Back-end Development

310 |

Cloud Computing

Integrated Developer Environments

IntelliJ IDEA

317 |

Microsoft Visual Studio IDE

318 |

PhpStorm / PyCharm

319 |

Visual Studio Code

Programming languages 326 |

Python

327 |

Java / Scala

328 |

Go

329 |

JavaScript

330 |

C++

331 |
337 | 338 | Have any questions? Require a DevOps assessment? Email us [enquiries@osodevops.io](mailto:enquiries@osodevops.io) or [schedule a call](https://calendly.com/sionsmith/oso-devops) --------------------------------------------------------------------------------