As someone that has worked on projects and technology for over 20 years, I’ve seen a lot of different migration needs, use cases, merges, and moves of data that is used to organize teams and larger groups of people. Sometimes the effort of moving data from one system to another is small, like moving a project of 50 tasks from one application to another. “Hey, worst case scenario, you can re-type those 50 tasks, right?” Other times it’s porting an entire application to a different hosting environment or combining multiple large instances together. Regardless of the scope or effort, organizations I’ve been in or worked with often make some major mistakes. These mistakes cause lack of efficiency or even worse, a stoppage in work!
In this presentation, I’ll share some best practices when approaching a migration from one PM tool to another, along with some of the pitfalls that I’ve learned from in the years of experiencing these things. The outcome of this talk will be to provide a framework that attendees can use as a take away for future migration work.
- Best practices for migration approaches to new project management tools like Asana, Jira, or MS Project
- The typical pitfalls in migration efforts
- How to avoid pitfalls by using the best practices when moving to a new PM tool
- Project Managers
- Program/Portfolio Managers
- PMO leaders
- Product Owners
- Product Management
- Technical leaders
Vice President, Sales and Marketing
Michael Roberts is an IT industry professional with more than 25 years of experience in bringing software to market. His industry certifications and accreditations include those from ICAgile, Cisco, CompTIA, Microsoft, Atlassian, GitLab, and the Scaled Agile Framework. With his experience as a technology executive, he’s guided many companies to successful IT and software projects.