Critical releases. Evidence for the decision.

From the work

Anonymised project outlines; client names are withheld at their request. Every engagement listed here began at the founder's previous company and continues with SKYPhoenix IT. The durations therefore describe the engagement, not the age of the company.

• Public sector

  Group-wide SAP transformation

  More than 10,000 unreliable test cases became roughly 500 maintained ones that actually run. For the first time there is a regression a release decision can rest on.

  Engaged for more than five years Team of 4+

• Public sector

  Several programmes, one quality model

  New programmes go live without quality assurance becoming the bottleneck. Test types, automation and release criteria were moved closer to the product across several applications.

  Engaged for more than six years Team of 2+

• Banking

  Test infrastructure renewed while in use

  The environments stayed usable through every migration step: testing and rebuilding ran side by side, not one after the other. The migration covered the full test infrastructure including the Tosca environment, alongside an assessment of the security-relevant points.

  Engaged for more than five years Team of 2+

• Credit institution

  Customer applications and service landscape

  Before every release it is dependably visible where quality stands and what is open. Previously the test cases were so loosely described that two people running the same check reached different conclusions.

  Engaged for two years Team of 3+