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.
Meeting | Cadence | Attendees | Purpose |
Stand-up | Daily | Business Lead, Technical Lead, Application Engineers | Daily Planning. Remove blockers and discuss work to be done for the day. |
Sprint Planning | Weekly | Application Engineers | Work Allocation. Discuss tickets, prioritize requirements, and make sure work is distributed appropriately. |
Co-Build Sync | Weekly | Business Lead, Technical Lead, Business Analyst | Knowledge Transfer. Review configuration progress, discuss technical challenges, and agree on who builds what next. |
Architecture Review | Bi-Weekly | Business Lead, Technical Lead, Solution Architect, Lead Application Engineer | Mandatory Sign-off. Review the Partner's evolving technical design, data model, and reusable components. (Focus: Scalability, Performance, Governance) |
Bi-Weekly Sprint Demo | Bi-Weekly | Technical Lead, Application Engineers | Validate Functionality. Formally accept or reject features based on finalized user stories. Ensure the work delivered aligns with the scope. |
Executive Steering | Monthly | Sponsor, Business Lead, Technical Lead | Review Metrics & Risk. Present ROI status, highlight major risks, and obtain high-level approvals. |
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?
Received? | Artifact | Purpose or Description | Phase |
| Project Plan | Detailed schedule including tasks, resource assignments, and overall timeline management. | Kickoff |
| Stakeholder Interview Questions | The guide used by the Partner to capture key perspectives and alignment from leadership and process owners. | Kickoff |
| Non-Functional Requirements | Defines technical criteria for system operation, including performance, security, and compliance requirements (NFRs). | Kickoff |
| User Persona | Defines the goals, needs, and pain points of the different end-user types (e.g., Submitter, Approver). | Kickoff |
| Environment Setup Tracker | Tracks the status, access keys, and configuration details of all development and testing environments. | Kickoff |
| Functional Requirements | Defines what the application must do, detailing specific application behavior and features. | Discovery and Requirements Gathering |
| Business Process Architecture | Documents a high-level view of the entire application flow end-to-end, including roles and integration points. | Discovery and Requirements Gathering |
| Solutions Architecture (System Context) | High-level technical overview of the application's place in the broader system landscape and core technical strategy. | Discovery and Requirements Gathering |
| API Specification | Details all external API calls, including resilience strategy, authentication scheme, and request/response schemas. | Discovery and Requirements Gathering |
| Integrations Summary Deck | High-level summary of all systems to be integrated, including status and data flow. | Discovery and Requirements Gathering |
| Data Model | Illustrates how data entities (people, objects, concepts) relate to each other, often including schemas and an Entity Relationship Diagram (ERD). | Discovery and Requirements Gathering |
| Data Dictionary | Collects descriptions of all data objects, fields, and items used in the data model. | Discovery and Requirements Gathering |
| Data Architecture Components | Documents data sources, acquisition, transformation, storage, retention, and exit strategy. | Discovery and Requirements Gathering |
| RBAC Diagram | Documents the application's roles, groups, and the approach to restricting module and submission access. | Discovery and Requirements Gathering |
| QA Test Strategy | Defines the methodology, tools, and overall approach for quality assurance and testing efforts. | Discovery and Requirements Gathering |
| Test Scenario and Test Case | Detailed list of scenarios and specific steps for formal testing and validation. | Discovery and Requirements Gathering |
| Artifact Process Flow (UI Example) | Documents the application flow and provides visual user interface examples (wireframes/mockups). | Discovery and Requirements Gathering |
| Release Roadmap | High-level plan showing architecture, configuration, and final release milestones. | Go Live and Handoff |
| Runbook / Production Readiness Guide | Step-by-step guide for monitoring, troubleshooting, and resolving common incidents after go-live (L1/L2 support). | Go Live and Handoff |
| Configuration Documentation | Explains complex module configurations, custom settings, and rationale for using specific components for future maintenance. | Go Live and Handoff |
| NFR Validation Report | Formal report proving the application meets all agreed-upon Non-Functional Requirements (e.g., latency, peak load, security checks). | Go Live and Handoff |
