Skip to main content

Texas state agency

Keeping a legislative reporting deadline during a legacy migration

A reporting mandate landed mid-migration. The agency needed engineering capacity that could work in the legacy system and the replacement at the same time.

Engagement
ITSAC staff augmentation, 9 months
Time to first candidate slate
3 business days
Deadline outcome
Met, no extension
Contract-to-hire conversions
2

The constraint

  • The reporting deadline was statutory and could not move, while the platform underneath the reports was being replaced.
  • Internal staff were fully committed to the migration itself, leaving no capacity for the reporting work.
  • A full procurement cycle would have consumed most of the remaining schedule.

What we did

  • Solicited through a request for resume on the DIR ITSAC contract, which removed rate negotiation from the critical path.
  • Staffed a small team spanning the legacy data model and the target platform so the same people could bridge both.
  • Sequenced the reporting build to land ahead of the migration cutover, then re-pointed it after.

How it ended

  • The statutory report was filed on the original date.
  • Reporting logic was written once against agreed definitions rather than rebuilt after cutover.
  • Two contract engineers converted to agency roles after the engagement closed.

Client name withheld. This is a composite of engagement shapes we work on regularly, written so the constraints and sequencing are useful rather than as an attributed reference.

Read the rest

Two more engagements with different constraints and different answers.