Our Path

• Custom Built Solutions: One of the most complex aspects of the migration project was the identification and understanding of several custom-built applications that had been built by contractors hired by various government groups. In most cases these contracts had ended and the original contractors who built and maintained the solutions were no longer available or able to be contacted. These SharePoint hosted “applications” generally consisted of a combination of custom pages (using JavaScript, jQuery, CSS, etc.), custom forms (usually Microsoft InfoPath), and custom workflows (SharePoint 2010 & SharePoint 2013). Each of the sites that fell into this category required identification of stakeholders/owners, meetings to understand the requirements and functioning of the system, brainstorming sessions to come up with ideas for how the functionality could best be recreated in SharePoint Online, and finally execution of the migration/rebuild.
  
  
  Agile Approach: To handle the large amount of work associated with this project and only a small team to execute, we chose to create a product backlog where each site existed as an item in the list. A group of sites which had been reviewed and estimated would then be packaged into a Sprint, each item assigned to a migration team member, and that sprint would then be executed over the course of two weeks. Each site migration functioned as its own small project with the migration team member working with the product owners, implementing daily stand-up meetings, testing, and requirements gather or feedback sessions as needed.