Over the past few years, I've transitioned project teams from their traditional Waterfall ways to a more Agile approach using various techniques at first and then decisively moving toward a single methodology. My preference is the Agile model presented in Scrum.  With my old PMO baggage, I struggled through the potholes and roadblocks that are typical when you attempt to change the way people have always done things.  As the more senior Scrum practitioners advised, it took about six months before the change became the norm and people weren't talking about why we were changing things anymore; they were talking about how we could change things.  As any project manager knows, this is the ultimate compliment and a huge win for the team.  They are now open to change instead of fearing it. 

While change is great for a team to accept and embrace, what happens to the other teams that are impacted? How do they relate to a Scrum team and their nontraditional ways?  I've been researching other Scrum Masters and teams to find how they have converted the agile atheists and here are some helpful insights I've found:

• The Agile PMO Role
• Is the Agile PMO Possible?
• How to Create an Agile PMO
• The Agile Manager
• Can you teach an old PMO new tricks?

Keep checking back for more materials and findings.  I may decide to track a case study of my own soon so if you're interested, please let me know there are some followers out there.