Organisation
Work/Task Breakdown
Phase 1 : Complete Data on VSS Projects
A wiki area has already been created to:
- outline the high level tasks to achieve migration of code from VSS and SVN to Git;
- be used to track progress of the migrations and sign-post to relevant documentation.
Quick Links
There was a previous project to migrate code from VSS to SVN. The list of applications in VSS was collated for that project and will be used as a starting point for migrating these applications to Git. The progress of this project was documented at Legacy Strategy for replacing Visual Source Safe with SVN within Applications Division. The list on that wiki page should not be used as the data has been migrated to an Excel spreadsheet attached to this page at INF141 Migration Decision Tracker.
The data in the Excel spreadsheet is incomplete so the first 2 phases of this project will capture accurate, complete information to inform the migration project.
Task Details
Update columns A - I in the INF141 Migration Decision Tracker to ensure that the information gathered for VSS projects is accurate and complete, including the existing location of code in VSS, when it was last updated and by whom.
Phase 2 : Collate Data on SVN Projects
The previous project only gathered data on VSS projects. We need to gather equivalent data for SVN projects and augment the decision tracker with this information.
Note that the Migration Decision Tracker contains some information on SVN projects that were previously migrated from VSS to SVN, but the information is not complete.
Task Details
Update the INF141 Migration Decision Tracker to add details of SVN projects in columns A - I, including the existing location of code in SVN, when it was last updated and by whom.
Phase 3 : Migration Decisions
For all projects identified and logged in the INF141 Migration Decision Tracker, a LEAVE/MIGRATE decision is required. At least one migration of each type of application - from simple to complex - shoudl be done to provide some estimation if we cannot do migrate all the applications within this current proejct/budget. This decision must be ratified by someone in the Production team who has enough information to make a determination on whether the application is in active use.
This phase can run in parallel with Phase 1 and Phase 2 above.
Task Details
Update the INF141 Migration Decision Tracker to add a migration decision for VSS and SVN projects (columns J - N) where data on the project is complete in columns A - I.
Phase 4 : Code and Deployment Migration
For all projects marked with a Confirmed Migration Decision of MIGRATE in the INF141 Migration Decision Tracker, these must be added to the Migration List at Code and Deployment Migration Plan. Each project must then be migrated to Git and Gitflow, and have its Bamboo automation updated if applicable. The child wiki page contains further information on this process.
Resources, Skills and Costs
The budget is fixed at 50 days. The project will migrate as much as it can.
We anticipate Apps Management will provide most effort, led by Andrew Hobden, with consultative expertise from Mairi Fraser and Bill Lee and support from other Apps staff as required. PM effort is 7 days, including support from Programme Manager.
Project Governance
Sponsor Stefan Kaempf and Key Stakeholder Bill Lee will provide governance.
Project Stakeholders
(Please copy and paste from Stakeholder List)
Project Estimations
(Please attach/link from Estimation Log)