Too often the ed tech project managers for a client agency and a contractor sit across the table and disagree on when a deliverable is finished, when the acceptance sign-off should happen, and when the payment must be made.
At times, there are some trade-offs. Sign-off now in exchange for more data loaded later. Keep working longer in exchange for a sign-off if half of these data elements can be provided in two weeks.
If both parties are truly objective, neither is likely to believe they got what they expected at the beginning of the contract.
Defining data scope is arguably the most difficult and the most important milestone in an ed tech project. Data scope is the agreed-upon source data to be moved from by ETL into the ed tech solution’s destination database to satisfy the contract.
Incredibly, data scope is too often deferred, underperformed, delegated to the contractor, or assumed to be obvious by the nature of the project.
This twiminar provides insight into the process for defining data scope to reduce risk in an ed tech project. Click here to access the complete white paper, Has Your Scope Creep Created a Scope Monster?
ESPTwiminars: EdTechScopeCreep – Follow & respond to tweets w/ lessons learned/insights. #ESPTwiminar8.1… https://t.co/gUPw9wcVqV
— ESP Solutions Group (@espsg) December 5, 2016
#ESPTwiminar8.2: Most significant insight about #EdTech project risk: lack of agreement on #DATASCOPE results from ill-defined source data.
— ESP Solutions Group (@espsg) December 5, 2016
#ESPTwiminar8.3 #DataScope is the agreed-upon source data to be moved by ETL into the #EdTech solution’s database to satisfy contract.
— ESP Solutions Group (@espsg) December 5, 2016
#ESPTwiminar8.4: Agreement on #DataScope is the most critical success factor for an #EdTech project. Sign-off in a Scope Document is crucial
— ESP Solutions Group (@espsg) December 5, 2016
#ESPTwiminar8.5:Ill-defined #DataScope puts an #EdTech project at risk of missing target dates, not accepting deliverables&overrunning costs
— ESP Solutions Group (@espsg) December 7, 2016
#ESPTwiminar8.6 #ESPTwiminars: #ScopeCreep begins when #DataScope starts to expand because agreement on source data was not secured.
— ESP Solutions Group (@espsg) December 7, 2016
#ESPTwiminar8.7: Data source documentation rarely meets the expectations of #EdTech contractors. Ed agency must invest effort to document.
— ESP Solutions Group (@espsg) December 7, 2016
#ESPTwiminar8.8 #DataScope=Discover data sources, document metadata, map ETL, achieve agreement, sign-off on Scope Document. 6-step process.
— ESP Solutions Group (@espsg) December 7, 2016
#ESPTwiminar8.9 #ESPTwiminars: Step 1: Document source data in a data source to repository to destination database flow diagram.
— ESP Solutions Group (@espsg) December 7, 2016
#ESPTwiminar8.10 #ESPTwiminars: Step 2: Document data elements & definitions in a metadata dictionary. #dataelements #metadatadictionary
— ESP Solutions Group (@espsg) December 7, 2016
#ESPTwiminar8.11 #ESPTwiminars: Step 3: Create ETL maps to validate existence of source data to match required decision questions. #ETLMaps
— ESP Solutions Group (@espsg) December 7, 2016
#ESPTwiminar8.12: Step 4-Write a #DataScope section for the Project Scope Document; get agreement; get sign-off by agency & contractor.
— ESP Solutions Group (@espsg) December 7, 2016
#ESPTwiminar8.13 #ESPTwiminars: Step 5 Follow #ChangeManagement Plan as project proceeds to amend the #DataScope.
— ESP Solutions Group (@espsg) December 8, 2016
#ESPTwiminar8.14 Step 6: Update the #DataScope document to remain aligned with the reality of the project (especially w/ waterfall projects)
— ESP Solutions Group (@espsg) December 8, 2016
#ESPTwiminar8.15 #ESPTwiminars: Ed agency should document source data before an RFP/contract—they rarely do. #sourcedata
— ESP Solutions Group (@espsg) December 8, 2016
#ESPTwiminar8.16 #ESPTwiminars: Documentation during a contract delays the implementation, but is a valuable investment that pays off later.
— ESP Solutions Group (@espsg) December 8, 2016
#ESPTwiminar8.17 #DataScope management includes ETL mapping integrity. Source element definition must match field in destination database.
— ESP Solutions Group (@espsg) December 9, 2016
#ESPTwiminar8.18 #DataScope documentation for agreement & sign-off includes verifying the existence of all source data as required.
— ESP Solutions Group (@espsg) December 9, 2016
#ESPTwiminar8.19 #ESPTwiminars: The success of an #EdTech project is 20% technology/software & 80% the data—the right data that people need.
— ESP Solutions Group (@espsg) December 9, 2016
#ESPTwiminar8.20: Click here to access the full white paper on #DataScope https://t.co/dpVcJ9tGfc
— ESP Solutions Group (@espsg) December 9, 2016