Partner Co-Build Delivery Checklist
This article is a quick checklist for organizations engaging a System Integrator (SI) partner for an Unqork co-build. Its purpose is twofold: Knowledge Transfer (ensuring your team learns the partner's methods) and Delivery Oversight (guaranteeing the partner builds a performant, scalable application that meets your requirements).
We recommend reading the full document in addition to using this checklist found here.
Meeting Checklist
The following cadence ensures active involvement, demanding rigor and accountability from your SI Partner. It is critical that your team is intimately involved in all meetings to catch issues early and keep the project on track. It is also essential that all team members are enabled and certified through Unqork Academy. This expedited the build process and ensures there is an “even playing field” when discussing choices made by the SI.
Artifact Checklist
To ensure your application is built to a high degree of quality, meets requirements, and is easily maintainable by your team moving forward, it is essential to receive the following documents and review their completeness before closing out the project.
Before signing off on these documents, please make sure you are confident in the depth and completeness of each. Asking clarifying questions before acceptance should be the norm. Here are a few sample questions:
Does the documentation detail all modules and APIs? Does it define user roles?
Does the documentation list each or all major components functions?
Have you followed our security plan for PII data?
Does the RBAC structure follow the proposed plan?
Does the documentation include steps for manually forcing a workflow state change if an error occurs?
Does it explain the "why" behind the most complex DWF logic?
Is reusable configuration documented with its purpose?
