Transitioning a Co-located Scrum Team: Lessons Learned

Sally is an experienced project manager who works in the Oil & Gas Industry. She has worked on global change management projects, global implementation projects, software development projects and a building-and-data center renovation project.


Topics: Agile, Communications Management, Resource Management, Scrum, Talent Management

In 2016, the corporate strategy for our year entailed doing a transition from a co-located team in the United States to a distributed team also in India to reduce cost. When we started, we worked in a productive, co-located agile scrum team in the States. The main risk for the project was losing velocity for si to 12 months while we brought new team members up to speed.

It has been about two years since the team started the process with team members distributed around the world, and I wanted to share my lessons learned…

1. Continuously refine your interview process until you can staff candidates successfully. It took a while to perfect the recruiting technique to add the right members to the team. Some of the lessons I learned through the recruiting process were:

Please log in or sign up below to read the rest of the article.

ADVERTISEMENT

Continue reading...

Log In
OR
Sign Up
ADVERTISEMENTS

"No Sane man will dance."

- Cicero