MANTA Cases #2: Pure Development Efficiency

MANTA Cases #2: Pure Development Efficiency

In the second part of the “MANTA Cases” series, we will take a look at a US investment management company that deployed MANTA six years ago, primarily for their development team to perform impact analyses and to boost the overall efficiency and agile development processes of their internal software. 

MANTA Cases #2: Pure Development Efficiency

In the second part of the “MANTA Cases” series, we will take a look at a US investment management company that deployed MANTA six years ago, primarily for their development team to perform impact analyses and to boost the overall efficiency and agile development processes of their internal software. 

The Customer had a fairly small yet, for its size, very complex data environment. The environment consisted of three databases:

  1. One was used as the main data warehouse that collected data for the core business
  2. The second database was a special investment data mart database (this database had specific requirements, making it even more challenging for it to co-op with new releases)
  3. The third database contained resources for the sales team

The entire environment contained about 15 hundred scripts, of which 20 to 30 percent were legacy code. The other 70 to 80 percent were newer code that was evolving at a fast pace due to the customer’s agile development standards. The customer used Microsoft SQL, most of the ETL code was in T-SQL, and some scripts were in SSAS.

Given the user requirements for each of the separate databases, the environment was growing and its expansion was necessary – otherwise, it would have become a burden. And, as is always the case in development teams, that familiar question was floating around in everyone’s heads: What’s gonna break if we make changes? The customer had developed an automated testing process for new code involving Unitask software, but for the legacy code, there was nothing like that. This made it necessary to deploy a tool that would define the dependencies between various parts of the code.

Now that MANTA has become part of the customer’s development process, MANTA can show the development team the impact a new release will have on existing code, making it easier to catch most of the larger issues during the testing phase. The issues the customer faces after a release have been, in their words, reduced by half and are in general much smaller.

Another benefit of MANTA for the development team is that the overall testing time before a new software release has been cut by 10 to 20 percent, and the number of developers needed to perform a release is now 2 people!

In this case, MANTA helped the customer maintain an agile development strategy for their internal software and improve the overall performance of impact analyses. However, due to the benefits that came with it, such as the reduction in overall testing time and the number of people needed to perform a release, MANTA could easily be beneficial for companies having trouble with staffing as well as for other small development and business analytics teams.

Do you have any questions about this specific case, or would you like to learn more about how to deploy MANTA in your company? Write us at manta@getmanta.com.

We cherish your privacy.

And we need to tell you that this site uses cookies. Learn more in our Privacy Policy.