ABCDEFGHIJKLMNOPQRSTUVWXYZAAABACADAE
1
2
Implementation Checklist: {PROJECT NAME}
3
4
PhaseTask IDTask NameResponsibleStatusStart DateEnd DateDependent onDocs LinkComment
5
1) Preparing for the Implementation1) Preparing for the Implementation
6
1) Preparing for the Implementation1.APoint of contacts identified for each target system (incl. system administrators, folks who can speak to the functional and technical requirements)BD/PM/AnalystNot Started02-20-202303-03-2023
7
1) Preparing for the Implementation1.BData sharing agreement finalized (if required; common for cross-organization workflows)BD/PM/AnalystNot Started02-20-202303-03-2023Mark "n/a" if not relevant
8
1) Preparing for the Implementation1.CBusiness value assessed & documentedBD/PM/AnalystNot Started02-20-202303-03-2023See questions to guide assessment
9
1) Preparing for the Implementation1.DHigh-level workflow requirements gathered & documented (in diagram)Business AnalystNot Started02-20-202303-03-2023Add link to diagramSee questions to guide assessment
10
1) Preparing for the Implementation1.ETechnical feasibility assessment completed to verify integration approach, available connection points, and OpenFn deployment option and adaptorsTechnical AnalystNot Started02-20-202303-03-2023See questions to guide assessment
11
1) Preparing for the Implementation1.FCapacity assessment completedBD/PM/AnalystNot Started02-20-202303-03-2023See questions to guide assessment
12
1Milestone: Implementation preparation complete BD/PM/AnalystNot Started03-03-202303-03-20231.A - 1.F
13
2) Discovery & Design - Functional Workflow Requirements
14
2) Workflow Functional Requirements2.AWorkflow BPMN diagram capturing functional steps of the business process finalizedBusiness AnalystNot Started03-01-202303-03-20231.DWorkflow diagram
15
2.BClient sign-offs on workflow diagram & mapping specsClientNot Started03-15-202303-17-20232.A, 2.D
16
2) Workflow Functional Requirements2.CRequest list of data elements from administrators of target systemsBusiness AnalystNot Started02-27-202303-07-20231
17
2) Workflow Functional Requirements2.DData element mapping specifications finalized (functional/business-friendly version)Business AnalystNot Started03-08-202303-15-20232.CSee mapping specifications template
18
2) Workflow Functional Requirements2.EWorkflow assumptions documented (e.g., what human, manual steps does the workflow rely on; what are the unique identifiers) Business AnalystNot Started03-08-202303-15-20231
19
2) Workflow Functional Requirements2.FTesting scenarios drafted Business AnalystNot Started03-08-202303-21-20231See Test Suite template
20
2Milestone: Functional workflow requirements finalizedBusiness AnalystNot Started03-21-202303-21-20232.A - 2-F
21
3) Discovery & Design - Technical Specifications
22
3) Technical Specifications3.ADocumentation on APIs or target connection points securedTechnical AnalystNot Started02-27-202303-08-20232Link to Docs
23
3) Technical Specifications3.BConnection points, authentication methods & target API endpoints confirmed and testedTechnical AnalystNot Started02-27-202303-03-20233.AExample Diagram
If client says they want to update 'financial' data, which API endpoint to use? Are 'updates' supported?
24
3) Technical Specifications3.CAccess secured to developer/sandbox environments for testingTechnical AnalystNot Started02-27-202303-15-2023Secure the following for each target system:
1. URL where a dev environment of each system can be accessed
2. Username
3. Password
4. Any other details needed in order to authenticate
25
3) Technical Specifications3.DAuthentication and authorization methods & credentials testedTechnical AnalystNot Started02-27-202303-15-20233.COnce the credentials for the developer environments have been procured, log in/ authenticate to make sure you have the appropriate access and can see relevant test data.
26
3) Technical Specifications3.EWorkflow BPMN diagram capturing the technical steps of the workflow finalized (to include the names of specific endpoints to access, HTTP methods/operations to use for each, triggers or starting events for each workflow) Technical AnalystNot Started03-15-202303-20-20232Technical Version of the Workflow DiagramClone your ""functional"" workflow diagram to create a technical version.
27
3) Technical Specifications3.FTechnical version of data element mapping specifications created
(this typically includes system, backend fields not visible/known by the end user, as well as more technical descriptions for any desired data transformations or cleaning logic)		Technical AnalystNot Started03-15-202303-21-20232Technical Version of the Mapping SpecsExpand upon your "functional" data element mapping specs to include other system- or API-specific fields we'll need to specify in order to successfully get/create/update data from the target systems.
28
3.GData volumes assessedTechnical AnalystNot Started03-15-202303-21-20232
29
3) Technical Specifications3.HTest scenarios updated to include any technical considerationsTechnical AnalystNot Started03-20-202303-22-20232.F
30
3) Technical Specifications3.IProject Security Configuration Checklist drafted to capture data security & compliance considerationsTechnical AnalystNot Started03-20-202303-22-20232See Security Checklist template - used if with strict security requirements
31
3) Technical Specifications3.JGithub repository createdTechnical AnalystNot Started03-20-202303-20-2023See OpenFn template 'project' repo
32
3) Technical Specifications3.KJob specifications written for developers Technical AnalystNot Started03-20-202303-22-20232See OpenFn Github issue template for 'New Requests'
33
3.LTest data created (if needed)AnalystsNot Started03-15-202303-22-20232
34
3Milestone: Technical workflow requirements finalizedAnalystsNot Started03-22-202303-22-20233.A - 3.L
35
4) Build
36
4) Build4.AOpenFn platform: project space created & relevant users invitedAnalystsNot Started03-20-202303-20-2023
37
4) Build4.BOpenFn platform: Workflows, triggers, and credentials configured AnalystsNot Started03-22-202303-22-20233
38
4) Build4.COpenFn platform: Version control configured to connect Github repoAnalystsNot Started03-22-202303-22-20233.J
39
4) Build4.DJob code written & pushed to branch on GithubDevelopersNot Started03-23-202303-24-20233.J
40
4) Build4.ECode review complete and merged to main branch on GithubDevelopersNot Started03-27-202303-27-20233.J
41
4Milestone: Workflows built on platformDev/AnalystNot Started03-27-202303-27-20234.A - 4.E
42
5) Testing
43
5) Testing5.ATesting Round 1: Developers run workflows locally with sample data providedDevelopersNot Started03-24-202303-24-20234
44
5) Testing5.B
Testing Round 2: Analysts complete Test Scenarios & run workflows on platform
AnalystsNot Started03-28-202303-28-20235.A
45
5) Testing5.CIteration: Analysts submit feedback to developers & re-testAnalystsNot Started03-28-202303-31-20235.B
46
5) Testing5.DUAT Round 1: Client completes Test ScenariosClientNot Started04-03-202304-06-20235.C
47
5) Testing5.EIteration: Analysts submit feedback to developers & re-testAnalystsNot Started04-07-202304-12-20235.D
48
5) Testing5.FUAT Round 2 (if needed): Client completes Test ScenariosClientNot Started04-13-202304-13-20235.E
49
5) Testing5.GIteration: Analysts submit feedback to developers & re-testAnalystsNot Started04-14-202304-14-20235.F
50
5Milestone: Client signs off on workflows configured ClientNot Started04-14-202304-14-20235.A - 5.G
51
6) Training & Prep for Go-Live
52
6) Training & Prep for Go-Live6.ATraining materials drafted for client administratorsAnalystsNot Started04-03-202304-04-2023See example admin training deck
53
6) Training & Prep for Go-Live6.BDocumentation drafted, and all project artefacts/docs linkedAnalystsNot Started04-03-202304-04-2023This should be a summary of the project and link to all of the completed specifications and templates for future reference in case this OpenFn solution needs to be updated. See example Github documentation site
54
6) Training & Prep for Go-Live6.CProject Security Configuration Checklist reviewed to determine if any configuration changes or settings need to be implemented post-testingTechnical AnalystNot Started04-12-202304-12-20235
55
6.DConfirm that production system(s) have been configuredTechnical AnalystNot Started04-12-202304-12-2023
56
6) Training & Prep for Go-Live6.EProduction credentials secured & tested (authentication & authorization)Technical AnalystNot Started04-17-202304-19-20236.D
57
6) Training & Prep for Go-Live6.FOpenFn platform: "production" project created (cloned from "staging" project), job configuration migrated, & jobs connected to production credentialsAnalystsNot Started04-18-202304-19-20235
58
6) Training & Prep for Go-Live6.GOpenFn administrator users & access levels confirmed and grantedAnalystsNot Started04-20-202304-20-20234.A
59
6.IEstablish support structures & governance model for change management Analysts/PMNot Started04-17-202304-21-2023
60
6) Training & Prep for Go-Live6Milestone: Send email to confirm go-live timeline & preparation statusAnalystsNot Started04-20-202304-21-20236.A - 6.J
61
7) Rollout & Support
62
7) Go-Live7.AGo Live: Turn "on" OpenFn jobs in production platform project so that the workflow is now live in production systemsAnalystsNot Started04-21-202304-21-20236
63
7) Go-Live7.BConfirm administrators have OpenFn notifications turned on to "Each Time" so that they will receive failure notifications (see OpenFn Account Settings)AnalystsNot Started04-21-202304-21-20236.G
64
7) Go-Live7Milestone: Communicate to end users as needed about the go-live and its implicationsAnalysts/PMNot Started04-21-202304-21-2023
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100