Acquisition Archetypes Seen within the Wild, DevSecOps Version: Cross-Program Dependencies

This publish examines issues that come up from a shared DevSecOps platform. As a result of a DevSecOps platform and power pipeline is simply too complicated and costly to create and handle individually for every program, the platform usually must be a shared functionality. This example creates dependencies and cooperation points.

These issues are examples of an acquisition archetype, which is how we check with a sample of organizational system behaviors which have been seen throughout the SEI’s experiences in conducting invited unbiased technical assessments (ITAs) on technical and programmatic points of the DoD acquisition packages. In these ITAs, program administration workplace (PMO) workers, contractor workers, customers, and different exterior stakeholder organizations present open and candid responses beneath the situation of anonymity that present the SEI workforce perception into what is actually occurring in a program. These insights recommend that comparable, recurring issues in software program acquisition and growth—archetypes—come up throughout separate and seemingly dissimilar packages.

A earlier SEI Weblog publish examined an archetype of clinging to the previous methods. On this publish, I talk about the recurring downside of cross-program dependencies. I describe the habits within the context of a real-world state of affairs and supply suggestions on recovering from and stopping future occurrences of this downside.

About Acquisition Archetypes

Our use of the phrase, “acquisition archetypes” is predicated on the extra common notion of system archetypes and is supposed to explain recurring patterns of failure noticed in acquisition packages to boost consciousness, together with offering approaches to mitigate or keep away from these hostile patterns. The incentives that drive these patterns are comparable throughout packages and have a tendency to drive comparable behaviors.

Cross-Program Dependencies

Typically a company might must construct a brand new widespread infrastructure functionality. As an illustration, a company may deploy a DevSecOps platform and power pipeline (e.g., compilers, code scanners, containers, and orchestration) that’s too complicated and costly to create and handle individually for every program or challenge. These packages or initiatives is perhaps reluctant to just accept an exterior dependency on the infrastructure program providing a standard infrastructure functionality, resulting in inside pressure. If the widespread infrastructure has points resembling poor efficiency, issue of integration, incapacity to completely carry out its perform, or unavailability throughout the required timeframe, the initiatives offering and supporting that functionality are more likely to turn out to be disenchanted or reluctant to proceed to help the infrastructure, and should criticize and even undermine it. For instance, present packages migrating to make use of the infrastructure is perhaps acquainted with utilizing a specific model-based programs engineering (MBSE) software or a code scanner that implements a particular set of scanning guidelines. Making the change from utilizing the software they’re acquainted with to utilizing a completely totally different software may have each up-front prices when it comes to modifications to the instruments and the system, and longer-term prices as customers should study new methods to perform the identical impact.

Initiatives utilizing DevSecOps infrastructure will usually must make vital modifications to their parts of the potential to accommodate the brand new infrastructure (e.g., modified interfaces, extra performance, or architectural variations). Supporting the brand new infrastructure will make their very own work tougher, require extra effort and assets, adversely have an effect on their present programs, and require rework of points of these programs. Consequently, these initiatives have little incentive to completely help the brand new system. Quite than being a win-win throughout the group, the widespread DevSecOps infrastructure might turn out to be primarily a win for headquarters on the expense of the opposite initiatives.

Report from the Area

The best way a program is established impacts the power of a number of, semi-independent organizations to cooperate to realize a standard aim (Determine 1). In the middle of supporting acquisition packages, the SEI usually encounters and should assist handle some of these organizational points. In a single such dialog a program chief stated, “Some packages get involved once they have dependencies on different packages. It’s an issue when totally different teams management totally different providers, and also you don’t have all of it beneath your management…. The infrastructure program asks us for stuff, and generally there’s funding, and generally there isn’t.” One other chief acknowledged that, in delivering capabilities, “Completely different organizations are in cost, funded individually, with totally different budgets, and they also’re required to ship towards necessities that don’t take note of issues they could need.”

In a single case, “[a] PMO wasn’t ready for the inevitable bow wave of latest work that was coming their approach. They didn’t like being advised what to do [by a higher authority akin to a program executive office or PEO]. That created some competition.” This example generally devolved into finger pointing, fairly than producing outcomes: “The totally different organizations concerned all must work collectively to share necessities and make selections—however nobody owns it, in order that they blame one another.” If the directing authority had been capable of supply schedule aid and/or funding for the extra work, it won’t have been seen by the PMO as basically an “unfunded mandate.”

On this case there was a misalignment of targets that every totally different group was attempting to realize. One official noticed, “The motivation at our program workplace is to fulfill value and schedule efficiency, whereas the infrastructure program is about functionality supply and high quality. Subsequently, the connection mismatch distracts from effectivity.”

Evaluation

Organizational tensions can happen because of the reluctance of packages to just accept an exterior dependency on one other program that may assist to supply a standard infrastructure functionality. The causal loop diagram (CLD) in Determine 1 represents a number of interacting packages and exhibits that the way in which one program is established can have an effect on its means to cooperate with different packages as all of them attain towards a standard aim. The leftmost loop (in inexperienced) exhibits that the much less ready the “consuming” program is to realize their targets by themselves, the extra they want the shared infrastructure. The rightmost loop (in gold) exhibits that when a “producer” group is tasked to supply shared infrastructure for a number of packages however is unable to fulfill all the “client” organizations’ expectations, the shoppers might turn out to be dissatisfied and determine to assemble their very own non-public or customized variations of the infrastructure as a substitute. Nonetheless, the center loop (in crimson) exhibits how doing so usually undermines the specified diploma of interoperability the shared infrastructure was supposed to allow. Establishing a number of, less-interoperable, non-public variations of the infrastructure prices considerably greater than a single shared model, utilizing up funding that might have been spent to construct the shared infrastructure. These non-public variations are the results of needing an instantaneous profit (eradicating the dependency) that can value everybody else—but when everybody does the identical factor, everybody finally ends up worse off because of the extra growth prices, non-standard programs, and schedule spent in growth and rework of the outcomes. It is a balancing loop, which oscillates round an equilibrium worth as help for the infrastructure grows after which wanes. Word that the static mannequin described by this CLD doesn’t predict how this dynamic will play out in all circumstances however does describe the way it usually ends with client packages opting out of the shared infrastructure association if they’ll.

Options and Mitigations

A public good is an economics time period for a service that’s made obtainable to all members of a group the place use by one member doesn’t preclude its use by others. For instance, our nationwide protection itself is a public good for all residents. The dynamic of manufacturing a public good in human organizations has been researched extensively and has a big set of normal options. The event and provision of widespread infrastructure, resembling a DevSecOps platform, is a kind of public good that’s topic to cooperation issues from cross-program dependencies.

In coping with cooperation issues, there are three lessons of options: motivational, strategic, and structural. These are broadly characterised as follows:

• Structural: Reframe the issue and guidelines so that individuals should behave extra cooperatively as a result of there’s formal authority behind, and enforcement of, the foundations (e.g., penalties, legal guidelines).
• Strategic: Give folks a rational and self-interested motive (i.e., incentive) to behave extra cooperatively.
• Motivational: Make folks really feel in a different way in order that they need to behave extra cooperatively.

The cross-program dependencies dynamic might be managed by management that may acknowledge these dependencies as they come up and take steps to mitigate them. Nonetheless, on this state of affairs the management would should be at or above the PEO degree, and the anticipated hostile ramifications of the problem would should be raised to their consideration by a number of of the packages concerned. Hierarchical, authority-based organizations such because the navy take this method, though normally after dialogue with the affected events. It’s a structural resolution, also known as “regulation by an authority,” nevertheless it requires having an authority to impose the foundations, may have enforcement of compliance, and should encourage resistance from these it’s imposed upon.

If a standard infrastructure program has overarching authority over the initiatives offering supporting capabilities, it may possibly handle lots of the points famous above. Nonetheless, the way in which such authority might be granted would range considerably all through the DoD, and in some circumstances might not all the time be potential. When it is potential, it might additionally occur that such authority is overused, even when the infrastructure program has the most effective of intentions in exercising it. The authority might override the needs or wants of the taking part initiatives; for instance, it would pressure taking part packages to implement unfunded and even undesirable mandates.

Wherever potential, the authority of the widespread infrastructure program must be exercised in win-win preparations that attempt to present worth in each instructions, to each events. Win-win relationships can contain offering the supporting initiatives what they need (e.g., funding or assets), fixing points they could have by offering organizational experience, providing specialised coaching or help that they want, and/or discovering methods to burnish their repute.

The second approach to handle cross-program dependencies is thru strategic approaches, resembling organising a significant incentive that rewards cooperation to drive profitable joint end-to-end outcomes for customers. These approaches are weaker than structural approaches, however can be utilized to reinforce them and embody:

• establishing cross-fertilization/cross-functional groups (exchanging folks to interrupt down obstacles and encourage cooperation)
• creating extra interdependencies (encouraging folks to work collectively out of necessity).

The third approach to handle cross-functional dependencies is thru much less formal motivational approaches. These approaches attempt to mitigate lack of belief and cooperation among the many totally different initiatives supporting the widespread infrastructure by utilizing actions that assist preserve or rebuild belief. Whereas weaker than both of the opposite two, these may also be used to reinforce structural and strategic approaches. Attainable motivational approaches for addressing the habits might embody:

• Consciousness: Improve the attention of the issue and talk the significance of everybody making a distinction to resolve it.
• Proof of high quality: Present compelling proof that the services or products will work as marketed earlier than asking organizations to help it or assist pay for it.
• Setting expectations: Encourage voluntary cooperation in settings during which individuals are extra more likely to be public-minded attributable to historical past and custom (e.g., Peace Corps or Battle Bonds).

The Outlook for Cross-Practical Dependencies

On this publish, I’ve investigated one recurring program habits associated to the introduction of DevSecOps: cross-functional dependencies. DevSecOps is a strong method that raises new issues round cross-functional dependencies. The complexities of DevSecOps can require packages to make infrastructure modifications that may have vital downstream results for different packages and initiatives. By growing mutually useful options, the authority of the widespread infrastructure program can encourage cooperation and higher habits.