Case Study: Scaling Software Delivery Capability for Preqin

The challenge

Preqin, a major data services provider in the Financial Services industry, were at a crossroads: do they continue to work with delivery partners to supplement their engineering capability, or invest in building their own?

Having used Plandek to do an initial assessment of the value their delivery partners were providing, Preqin elected to build their own delivery capability, and faced the challenge of quickly scaling up new processes and team located in different locations throughout the world.

The scope

As Preqin grew from only a handful of developers in the UK to an in-house professional delivery capability, they used Plandek to ensure new recruits were settling in, processes were scaling, and teams were effectively able to deliver to clients.

As a growing delivery team, Preqin focused on speed to market, process compliance and efficiency, and Sprint effectiveness.

Plandek provided the Board, the technology leadership team, and the individual teams with a clear picture of how well they are scaling, balancing the challenges of embedding new people and processes whilst continuing to deliver their business’s priorities.

The outcome

Preqin have successfully built (and continue to build) a strong delivery organisation that stretches three continents. Through Plandek, they monitor each team’s journey from day 0, providing support and guidance where needed.

Over the course of building this new organisation, Preqin have:

Reduced Speeding Tickets by 64% (process compliance);

Improved their First Time Pass Rate by 12% (team collaboration and efficiency);

Tripled their commit frequency (best practice);

Reduced their Time to Resolve a Pull Request by 18% (team collaboration and efficiency);

All whilst maintaining a very strong Cycle Time (speed to market).

Other case studies

Case Study: Sharing success across teams at a financial software company

Using Plandek to track and replicate high performing engineering teams

Breakdown and Filtering Options

As with all our metrics we have a broad selection of breakdowns and filters to allow you to tailor Commits without a Pull Request to your various needs.

The first two options below are based on the commit data itself – Committer and Repository. Useful to be able to drill down on where this PR process is being used or not.

The other options, prefixed “Ticket”, are pulling in the fields for related tickets that are referenced in those commits. For further detail see Commits without a Ticket Reference.

So where ticket linking is in place you’ll be able to gain unique perspectives of this metric based on attributes like Issue Type, Epic Link or Fix Version etc.