At the Agile Greece Summit 2015 Erhan Köseoğlu presented a case study of scaling agile from Vodafone Turkey. InfoQ interviewed him about why Vodafone decided to implement agile, how they dealt with situations where people resisted, how they established a culture that supports agile, how they involved their customers in the agile transition, and which advice he want to give to C-level executives.
An agile transformation needs a convincing involvement and statement by top management to show that the game really has changed says Jürgen Dittmar. InfoQ asked him about how management can be an obstacle in agile transformations, changing the mindset and approach for managing organizations, how managers and leaders can enable agility in organizations, and examples from applying Management 3.0.
Even with best intentions it can be challenging for people to follow up on actions that they agreed to do. They can start to doubt if they can do the actions and become afraid to fail. Several authors have recognized this and came up with suggestions for dealing with it and making change happen.
It can be challenging for people when they learn an idea at a conference and try to apply it in their work environment. Fanny Pittack and Alex Schwartz practiced a “change dojo” with conference attendants and provided suggestions to do successful change in organizations. InfoQ interviewed them about using change dojos for organizational change.
Tester should go beyond their testing discipline and go into the organization. By asking questions they can start a movement that increases product quality and helps organizations to become more successful as Mike Sutton explained in his closing keynote at the Agile Testing Day Netherlands 2015 about test beyond quality – beyond software.
Testing teams and their managers need to unlearn the traditional mindset and practices when they want to adopt an agile way of working says Navneet Goyal. At the International Conference on Software QA and Testing on Embedded Systems he gave a talk about how test teams should adapt themselves in agile projects.
Agile adoption in organizations where command and control is the most dominant management style can be tricky. There have been situations where an agile transition didn’t deliver the expected improvements, or even failed and was stopped. Several authors suggested ways to adopt agile in organizations with a command and control management style. How did you deal with it when transitioning to agile?