Sr Azure DevOps Architects / Remote ( Denver, CO), 3+ Months Contract
Job Description
Remote Role, Location is no preference
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. Client 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 Client 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
Apply tot his job
Apply To this Job
Remote Role, Location is no preference
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. Client 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 Client 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
Apply tot his job
Apply To this Job