Olaf Lewitz gave a keynote about Integral Quality at the Agile Testing Day Netherlands 2015. InfoQ asked Lewitz about quality attributes, what causes poor quality software, the relationship between the structure and culture of the organization and software quality and about clarifying intent and increasing trust.
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.
At QCon London 2015, Helen Walton and Pete Burden came up with a discussion on the impact of culture in project’s success (failure indeed) and gave practical advice on how to influence the organization's culture to which a person is working for
Marco Achtziger shared his experiences with deploying continuous testing in large scale agile project at Siemens Healthcare at the OOP conference. InfoQ interviewed Achtziger about continuous testing and continuous integration, infrastructural and social challenges with continuous testing, testing processes and tools, and improving continuous testing.
When you want to scale agile you have to view it as “a way of doing things, a mindset and a culture for the whole company” says Christoph Mathis. To scale agile you need to change the culture to achieve a learning organization.
To become agile you might need to change the core values and beliefs of an organization. Applying value systems from spiral dynamics can help organizations to go from doing agile to being agile as Dajo Breddels showed in the path to agility at the XP Days Benelux 2014 conference.
The starting keynote at Velocity Conference Europe 2014 was all about how human error is too often the easiest way to explain away a failure and how a different approach is needed. Steven Shorrock, European Safety Culture Programme Leader at Eurocontrol, explained why a Systems Thinking approach applied to safety is a better answer.
Continuous learning supports agile adoption in enterprises. A culture change can be needed to enable and support continuous learning. There are several things that managers and agile coaches can do to establish and nurture a continuous learning culture.
At DevOpsDays Amsterdam, Mark Coleman asserted that all organizational's cultural changes start with one person influencing another. He finds that Charles Handy's writings on power and influence help on understanding how an organizations works and how one can go on to change it. Mark discussed Charles Handy's six sources of power and six methods of influence.
Writing in the Wall Street Journal, Rachel Shannon-Solomon suggests that most enterprises are not ready for DevOps, while Gene Kim says that they must make themselves ready if they want to survive.
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?
The 8th annual State of Agile Development Survey was announced at the Agile 2013 conference. Previous surveys have provided insight into agile adoption. You can participate in the survey, and get the data before it goes public.
Being one of the principles of the agile manifesto, sustainable pace is considered important by many to deploy agile. But achieving a sustainable pace can be difficult, and teams are often asked to improve their velocity. What did you do to adopt sustainable pace with your team? And how did you improve the speed in which your team delivers, and establish a new sustainable level?
Agile methods have the potential of creating great results. But those great results are not a guarantee; in fact anecdotal evidence suggests that those great results are only achieved by a small percentage of those teams and organizations adopting and adapting agile methods. There are invisible requirements for this success. One of these requirements seems to be safety.
In 2006, The New York Times had 20 engineers, all located in a separate building off-site. Engineering and journalism were organized as completely separate entities, even ad sales departments were separate. How do you change a culture like this into a culture where technology drives and supports journalism?