Infoverity successfully applied the FlexiFrame testing methodology for a project that integrated MDM processes and technologies with in house systems. By using Infoverity’s testing strategy for Informatica MDM, requirements were sharpened, tested iteratively, and the project timetable accelerated, overcoming an earlier project false start. The business solution delivered capabilities to master and govern supplier and product information.
The project goal was to implement and execute quality assurance testing for a new Informatica Supplier and Product Hub within a constrained timeline and budget. As a stressed project, Infoverity had responsibility to bring the project back on schedule and minimize requirements gaps to meet an aggressive, at-risk deployment date. This included testing strategies across MDM technologies supporting the future MDM hub: legacy applications, Informatica’s Data Quality and Address Doctor, and external reference data systems.
Approach
Several key project risks were assessed upon initial engagement. Functional and technical requirements were defined by project members no longer a part of the project, and the testing was assessed to be one month behind schedule and slipping weekly.
Using the Testing FlexiFrame framework, Infoverity was able to reestablish timelines that aligned with the project plan as well as define gaps in existing requirements. Test-driven design reviews were conducted to locate incomplete processes, gaps in ownership of key authoring and approval steps, and client uncertainty about successful outcomes. The Testing FlexiFrame is unique in that a planned sequence of events simultaneously:
- Reviews the design and highlights process, integration and role/responsibility gaps and optimization opportunities,
- Documents testable conditions, scripts, and success outcomes,
- Delivers design and test iterations in an agile schedule, effectively using a prototype-and-test-driven outcome.
Results
The Testing FlexiFrame was successful in clarifying vague requirements as well as qualifying missed requirements and defects. In the course of twelve weeks of effort over 200 test cases and scenarios were documented and executed, identifying 240 additional requirements at a point where they could be considered without severe disruption to the project. Several key ‘wins’ were:
- User/Technical Testing Completed
An initial implementation of Supplier and Product into the MDM Hub was completed on time with minor defects that were deferred by the business. Due to the agile approach, the business was able to sign-off on technical unit testing and user acceptance testing in a timely manner. Consistent, high-context business involvement mitigated the risk of low testing comprehension and acceptance at the end of the project.
- Gap Analysis and Future Requirements Documented
Test cases were executed by business stakeholders in parallel with the Test Lead’s efforts to document next-phase requirements and estimate future phase effort. This enabled the business to view and manage all existing and planned functionality and reflect on other enhancement requests in one location that was easily managed by all team members.
