Continuous Delivery: Building Trust in a Large-Scale, Complex Government Organization

A Survey of DevOps Concepts and Challenges

“…Increase in delivery throughput: Neely and Stolt reported that the delivery throughput per developer in their company increased with the adoption of continuous delivery and defect rate became more predictable [33]. Siqueira et al also reported how, after investments in DevOps and continuous delivery, the number of releases per semester remained the same even after a considerable decrease in the number of team members [44].…”

“…Experience Report: refers to reports of organizations adopting DevOps or continuous delivery/deployment. For example, Siqueira et al describe the impact of a DevOps team in the context of a governmental project [44].…”

“…Building trust: when an organization builds software for other large organization, especially the government, it is common for the relationship between the contractor and contracted to be dominated by mistrust, which leads to cumbersome development processes. However, Siqueira et al advocate, based on their experience, that continuous delivery leverages a trust relationship among the contractor and contracted in software development, even in governmental projects [44].…”

“…Building for the government: although building software for government involves more bureaucratic processes, requirements and prioritization can often change due to political reasons [44], which leads to the need to shorten the release cycle by adopting agile and DevOps practices in the governmental scenario.…”

“…They argue that, although the DevOps team silo is an antipattern, it is acceptable when it is temporary and focused on sharing development practices to operations staff and operations concerns to developers. Siqueira et al report how a DevOps team with senior developers and rotating roles among members was a key decision to construct and maintain a continuous delivery process [44].…”