At the Agile Testing Days 2014 in Potsdam Jan Jaap Cannegieter spoke about using different sides of our brain to optimize testing and he will redo this presentation during the Agile Testing Day Netherlands 2015. InfoQ interviewed Cannegieter about how agile has changed testing, creativity and thinking in testing, skills of agile testers, and how testers can make steps towards agile testing.
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.
In agile software development feedback plays an important role. Many are aware how feedback supports dealing with changing requirements and adjusting the way of working in teams with retrospectives. But there is more that feedback can do in agile. “An effective feedback cycle in Scrum is more than having sprints and doing retrospectives” says Kris Philippaerts.
The Scaled Agile Framework (SAFe) provides practices, roles activities and artifacts for applying Lean and Agile development at enterprise scale. InfoQ interviewed Dean Leffingwell about deploying the scaled agile framework, building cross functional agile teams and aligning teams, the people part of SAFe and the principles of lean and agile leadership.
Glenn Vanderburg, director of engineering at LivingSocial, gave an interesting recount of his effort to implement TeX’s algorithms in Clojure at the last ClojureConj conference. In the process, he discovered how much programming has changed in the last thirty years.
Adopting agile in organizations usually impacts the role and activities of project managers. Scrum offers the possibility for project managers to become Scrum masters or product owners. Project managers can also adopt their way of working and the things they do to work together with Scrum masters and agile teams.
In this article we discuss some of the misunderstandings surrounding DevOps and provide an introduction to a process that can bring the cultural shift that DevOps is all about.
The Manifesto for Agile Software Development values "working software over comprehensive documentation". This core value asks us to think about how much and which kinds of documents are needed and when they need to be written.
The Scrum Holy War warns about the religious fervor of Scrum and why it won’t save your company.
This article contains comments from googlers providing insight in how Google’s engineers use their 20% time on pet projects.
A sales manager answers the questions of can sales be agile and how to make the change.
Michael Stanke, director of software delivery at Puppet Labs, has written on SysAdvent about how DevOps is the development of a culture that can successfully overcome complex and difficult system thinking problems. Michael shares his experience of transitioning into a new position full of opportunities to make technical and process oriented contributions.
Early results of a study on the effects of agile development practices are showing improvements in productivity and quality. These results aim to answer questions on development projects schedules and budgets. They also provide insight in the results of outsourcing and co-located teams.
Tobias Mayer started Business Craftsmanship: an organizational development and transformation approach to teach and apply ideas from Agile software development to any knowledge work context. Several posts have been published, for example about “Core Values” and “In Praise of Processes”.
There have been numerous attempts over the years to determine the best way to measure the effectiveness of an Agile adoption. Some recent articles have reignited the debate around the most useful metrics.