techmaturity

A model and portal from Ticketmaster's team for measuring software maturity across five dimensions, open sourced with Docker and Rails based instructions for trying it.

Tech Maturity measures and tracks the maturity of software over time. The README says it helps identify growth opportunities, set clearly defined targets, and measure progress toward the goal of continuous delivery. Borrowing a line from sports, you cannot tell if you are winning without a scoreboard, so the team built a portal to gather, aggregate, and display patterns from the assembled data and make them visible to everyone in the company.

The model charts a path that can be completed in stages, with flexibility to move through five dimensions of software development: Code, Build and Test, Release, Operate, and Optimize. The dimensions give teams a shared vocabulary for where a product stands. Nothing about the model prescribes a single route through them.

For Ticketmaster's move to the public cloud, the model served as a cloud readiness gauge, quantifying how close a product is to being ready for migration. That was done by setting targets for a subset of capabilities the team considers the minimum requirements for any product in the public cloud. Legacy product owners get a clear, trackable goal, and the company can operate in a decentralized, self-service way while teams run their migrations.

The README's favorite feature is that the model does not prescribe solutions. It offers standards with an aim to give teams a clear path toward efficient product development at scale, and it can be tailored to specific needs. The team says Ticketmaster runs technology ranging from the 1970s to today, and the model has been applied to products from VAX code to JavaScript libraries.

Trying it out is three steps: get Docker, run docker-compose up, and open the local address in your browser. Testing with a bundle involves installing bundle and running the Rails test suite. Contribution follows a fork, commit, squash, and pull request flow. The README closes by being excited about the community response and thrilled to share the tool.

The README is half explanation, half invitation: what the model does, how Ticketmaster used it for cloud readiness, and then the steps to run it with Docker. The open source release is framed as sharing a tool the team is proud of.

• Source 1 · Project repository
• Source 2 · README