Similar jobs
Sr Azure DevOps Data Migration Architects
Denver, CO.
Urgent Hiring
Contract W2
Contract 1099
C2H 1099
C2H W2
Contract Corp-To-Corp
C2H Corp-To-Corp
Job Alerts:
NoYes
Save
Posted on:09/11/2023
196
Similar Jobs
Depends on experience
Azure DevOps,Data migration,Migrate Features,SQL Data Access,Tasks,User Stories
Work type: Remote and Local
Work authorization: US local resources,Work authorization required,Work authorization sponsored,Work authorization in field of study
Duration: 3 months
Veteran Service: Yes
Number of hirings: 1
Job Details
*****Direct Client Requirement*****
Job Title: Sr Azure DevOps Data Migration Architects
Location: Denver, Colorado (Remote, Only local)
Duration: 3 Months
Interview type: Skype or Phone
Job type: C2C,W2,1099
Experience: 10 years
Job Description
Period of Performance
The Trails Developer shall commence on or before September 18, 2023 and continue through December 31, 2023.
Purpose: Create an Enterprise-wide plan for data and agile work item migrations and implement the migration with a pilot team: CDHS Trails to adjust and refine it before distribution Enterprise Wide. OIT has a central work item tracking tool for technical teams and is using it to improve and standardize process enterprise wide. Creating a standard migration path to this common tool will streamline the efforts by any team that requires a migration, thereby reducing cost and time needed.
Scope of Work
Migration of work items from CDHS (TFS) on-prem to OIT AzD per business requirements. See Functional and Business Requirements.
Minimum Resource Requirements - Required
· Familiarity with Azure DevOps migration tool options
· Familiarity with Azure DevOps work items (area paths, etc)
· Familiarity with TFS on-prem data, whether APIs or Direct SQL Data Access
· Familiarity with basic script/code writing and rest API calls
Functional and Business Requirements:
Move Epics, features and user stories, including comment history and attachments
1) Determine migration tool
a) Research tool for import/export
b) Considerations for choosing tool:
i) How much customization would be needed to accommodate business requirements?
ii) Epics, Features, User Stories, Tasks and links must be maintained during migration (Maintain current hierarchy)
iii) Maintain assignee during migration
iv) Can “discussion entries” (a.k.a. Comments) be migrated over?
v) Links to other work items copied (other than hierarchy mentioned above)?
vi) Attachments
vii) Migrate/map “states” (e.g. New, Committed, etc.)
viii) Current “custom” fields
ix) Tool must have some sort of logging that racks successful copying
2) Determine migration scope
a) Define which items need to be migrated
b) Work in phases or full migration at once?
3) Map fields
4) Historical data
a) Define scope of how much history must be migrated
b) How long does CDHS AzD need to remain available as read-only? Are there audit requirements to consider?
5) Security Considerations
a) Define and set security permissions, as well as any other security considerations prior to migration
6) Training and Access Considerations
a) Define training and set access permissions
7) Perform Migration
a) Migrate work items
Job Title: Sr Azure DevOps Data Migration Architects
Location: Denver, Colorado (Remote, Only local)
Duration: 3 Months
Interview type: Skype or Phone
Job type: C2C,W2,1099
Experience: 10 years
Job Description
Period of Performance
The Trails Developer shall commence on or before September 18, 2023 and continue through December 31, 2023.
Purpose: Create an Enterprise-wide plan for data and agile work item migrations and implement the migration with a pilot team: CDHS Trails to adjust and refine it before distribution Enterprise Wide. OIT has a central work item tracking tool for technical teams and is using it to improve and standardize process enterprise wide. Creating a standard migration path to this common tool will streamline the efforts by any team that requires a migration, thereby reducing cost and time needed.
Scope of Work
Migration of work items from CDHS (TFS) on-prem to OIT AzD per business requirements. See Functional and Business Requirements.
Minimum Resource Requirements - Required
· Familiarity with Azure DevOps migration tool options
· Familiarity with Azure DevOps work items (area paths, etc)
· Familiarity with TFS on-prem data, whether APIs or Direct SQL Data Access
· Familiarity with basic script/code writing and rest API calls
Functional and Business Requirements:
Move Epics, features and user stories, including comment history and attachments
1) Determine migration tool
a) Research tool for import/export
b) Considerations for choosing tool:
i) How much customization would be needed to accommodate business requirements?
ii) Epics, Features, User Stories, Tasks and links must be maintained during migration (Maintain current hierarchy)
iii) Maintain assignee during migration
iv) Can “discussion entries” (a.k.a. Comments) be migrated over?
v) Links to other work items copied (other than hierarchy mentioned above)?
vi) Attachments
vii) Migrate/map “states” (e.g. New, Committed, etc.)
viii) Current “custom” fields
ix) Tool must have some sort of logging that racks successful copying
2) Determine migration scope
a) Define which items need to be migrated
b) Work in phases or full migration at once?
3) Map fields
4) Historical data
a) Define scope of how much history must be migrated
b) How long does CDHS AzD need to remain available as read-only? Are there audit requirements to consider?
5) Security Considerations
a) Define and set security permissions, as well as any other security considerations prior to migration
6) Training and Access Considerations
a) Define training and set access permissions
7) Perform Migration
a) Migrate work items
Interview type: Telephonic, Virtual
Experience years required: 10
Work hours: Monday to Friday, 8 hour Shift
Company job ID: JPC - 5610
Education: Bachelor’s Degree
Job Updated: 12/22/2023
Recruiter Details