The Curriculum That Became the Federal DITAP Program

The Challenge

Federal agencies once bought custom software the way they bought office buildings. A contracting officer wrote the requirements up front, competed a fixed scope, and held the vendor to a schedule of phase gates and document deliverables. That structure suits construction. It suits software badly, because a requirements document written two years before launch describes a product nobody has used, and the contract then punishes the vendor who learns something in month nine.

The acquisition workforce carried no training that offered an alternative. Contracting officers across the government had spent careers mastering the Federal Acquisition Regulation, and none of their professional development explained how to write a statement of work that pays for working software every few weeks. Agencies kept buying waterfall because waterfall was the only shape their buyers knew how to price, evaluate, and defend.

The Executive Office of the President moved on that gap. The United States Digital Service and 18F had started rotating engineers out of industry and into agencies, and those technologists kept landing inside programs whose contracts made iterative delivery impossible in practice. The Office of Management and Budget competed a training effort aimed squarely at the people who write the contracts.

Vidya’s Approach

Vidya earned a place on the winning team for that competition and worked alongside the United States Digital Service and 18F, together with other vendors, to build the first iteration of what became the Digital IT Acquisition Professional program. Vidya authored curriculum and taught the course for the Executive Office of the President. The goal was narrow and concrete, namely teaching federal procurement officials to write contracts that motivate better vendor behavior and therefore better software.

Contracting officers filled the room, and that audience decided nearly every design choice in the material. The team drew a hard boundary around scope. The curriculum would cover contract structure, market research, and vendor incentives. It would leave software engineering to the engineers. A contracting officer who understands why a fixed-scope award produces an unusable product will restructure the next acquisition, and that single change buys an agency more than any engineering vocabulary the same officer could memorize.

Vidya still argues the position that curriculum started from. Any contract type that fixes product scope up front hands the program a bad outcome no amount of oversight recovers, and confidence in one implementation should never harden into lock-in to the vendor who built it. Vidya carries that argument into federal market research today and laid out the underlying history publicly in Don’t Go Chasing Waterfall. Buying behavior follows organizational culture, which is the same problem Vidya works on inside agencies through its technology culture practice.

One limit belongs on the record. Vidya held a teaming position on that award rather than the prime contract, and the government owns the curriculum outright. Vidya kept the thread going through membership in the GAO Agile Expert Group and contributions to Government Accountability Office agile reports, which is where the federal conversation about measuring agile delivery continued after the course ended.

What Changed

Federal contracting officers now hold a credential for this work. The TechFAR Hub runs DITAP as a standing program with cohorts of 25 to 30 students over roughly six months, covering digital services market intelligence, stakeholder analysis, and leading change as a digital IT acquisition professional. Graduates earn 60 to 80 Continuous Learning Points and a DITAP Training Certificate that qualifies them for the Digital Services Credential through the Federal Acquisition Institute. An Office of Federal Procurement Policy memo established the Federal Acquisition Certification in Core-Plus Specialization in Digital Services, and FAC-C (Professional) holders who work digital services acquisitions above the FAR 13.500(c) thresholds have to take the training. A course agencies once volunteered for became a requirement their senior buyers cannot route around.

An agency that wants the delivery behavior DITAP describes still has to write the solicitation that pays for it, and that work happens one acquisition at a time. Vidya brings the same argument to government modernization engagements, where the contract shape and the architecture get decided in the same room. Program offices planning a digital services acquisition can put that structure in place before the solicitation goes out, and the vendors who answer it will build differently because of it.