Essay Example on YOUR GUIDE TO DEVOPS FOR GOVERNMENT EXECUTIVE SUMMARY

YOUR GUIDE TO DEVOPS FOR GOVERNMENT EXECUTIVE SUMMARY DevOps has become a common term that often means different things to different people teams and agencies This is particularly true for the public sector which is only now beginning to adopt what were previously private sector tactics for streamlining operations and enhancing application development Now more than ever there is a solid case for the government to start using DevOps practices similar to the way commercial agencies use DevOps With a growing marketplace population and reliance on technology federal agencies must acquiesce to this new approach if it wants to produce relevant applications spend within budget and better serve the public In FY17 the federal government spent over 76B on Information IT projects However the vast majority of these projects have not produced the intended results wasting time energy and valuable tax dollars It's not the resources It s certainly not the funding It s the execution 

DevOps integrates the tasks and goals of developers and operations staffs instead of working separately it encourages collaboration throughout the entire project lifecycle It takes separate functions into one continuous process breaking down obstacles between software development and operations When you hear DevOps think collaboration The collaborative aspect of it entails fundamentally incorporating iterations and the continuous feedback among stakeholders allowing them to successively refine and deliver software systems This allows for quicker development through productive iterations and quick improvements and changes This level of collaboration ensures greater quality assurance a must in government and more quality products resulting in better service to citizens Federal initiatives and projects are heavily reliant upon requirements DevOps brings those requirements to the forefront ensuring the agency can abide by legislative mandates compliance standards and security best practices 

By heavily integrating compliance requirements and security objectives into iterations teams achieve better security performance and spend less time remediating security issues later such as after the product is launched Integrating security throughout the software development life cycle ensures up to date and quality security measures are built and implemented in a measured and well thought out fashion The end goal of DevOps is simple improve stakeholder collaboration system security and product quality from planning through delivery If properly implemented agencies can utilize DevOps methods to improve deployment frequency and development cycles achieve faster time to market build more secure systems enhance public services lower failure rate of new releases and shorten lead time between fixes Furthermore some benefits to DevOps include the ability to Accurately locate specific problem areas Address issues found in development testing and production operations Avoid human errors during development and deployment Continue to make improvements to applications even after they are in production Discover software defects early in the life cycle rather than while in production Prevent delays associated with resource access Speed up development through agile methodologies