Sr Azure DevOps Architects- || remote || 20 + || USC GC H1B

[Manish Candid8]

Role: - Sr Azure DevOps Architects-
POSITION : Remote
VISA : USC GC H1B
Experience : 20+
Duration: 4 months
manish.c...@gmil.com Mani...@candid8.us 878 888-6242
 Description:

 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

Determine migration tool
Research tool for import/export
Considerations for choosing tool:
How much customization would be needed to accommodate business requirements?
Epics, Features, User Stories, Tasks and links must be maintained during migration (Maintain current hierarchy)
Maintain assignee during migration
Can “discussion entries” (a.k.a. Comments) be migrated over?
Links to other work items copied (other than hierarchy mentioned above)?
Attachments
vii) Migrate/map “states” (e.g. New, Committed, etc.)

Current “custom” fields
Tool must have some sort of logging that racks successful copying
Define which items need to be migrated
Work in phases or full migration at once?
Map fields
Historical data
Define scope of how much history must be migrated
How long does CDHS AzD need to remain available as read-only? Are there audit requirements to consider?
Security Considerations
Define and set security permissions, as well as any other security considerations prior to migration
Training and Access Considerations
Define training and set access permissions
Perform Migration
Migrate work items

Thanks & Regards,
Manish
Technical Recruiter
Candid8
Cell:  878 888-6242 |
manish....@gmail.com || mani...@candid8.us