Project Management - Iterating Change with Scrum

All internal product work on the IgniteConnex platform adheres strictly to Scrum Management practices. However, “integrations” implemented through customer projects can also benefit from the same practices. You can use this model with an in-house project manager or use IgniteConnex (or Service Partner) teams to manage integration development on an ongoing basis. This can have a variety of options. You can use IgniteConnex to develop small, medium, or large enhancements through our services partner, ad-hoc, or using a dedicated team.

Scrum Framework

Version Control

For API Production, Metadata and Flows (which declare how the integration should execute) are version controlled with an Azure DevOps Repository, and Automations are in place to build, test, and deploy change. For API Consumption, Interfaces are defined within our API Specs feature which documents an Interface Model each API must use to establish a secure and monitored API layer. Before changes can be deployed to Production, an approver from the bank must have access to our Azure DevOps board and approve the change. In addition, there is a document template/form that must be filled out for each release and submitted to the project tool (Azure DevOps).

Ad-Hoc Development Examples

Prices are examples only and require a custom quote from IgniteConnex or CG Infinity (Services Partner), based on your specific needs.

Cost Factor Examples	Small	Medium	Large	Custom
Price Estimate	(Contact sales)	(Contact sales)	(Contact sales)	(Contact sales)
Duration	2 weeks	Up to 4 weeks	Up to 8 weeks	Beyond 8 weeks
Complexity	Integrating to an existing interface	Integrating to an existing interface	New vendor integration	Multiple vendor integrations
Interface Changes	Expose existing accessible data	Expose existing accessible data	Expose new data through platform	Expose new data through platform
Vendor	IgniteConnex	IgniteConnex	CG Infinity	CG Infinity