At the fifth ‘Agile on the Beach’ conference, held in Cornwall, UK, several leading practitioners of agile software delivery presented the state-of-the-art and emerging trends within this domain. Key messages included the need for the more rigorous use of the scientific method throughout the software delivery lifecycle, and the benefits provided by applying agile principles to product development.
Doing pair programming when working remote helps to increase interaction between developers and build relationships in teams, it makes knowledge flow and can prevent developers from drifting away. You can experiment with tooling to find a setup that works for you. Empathy and egolessness can emerge organically when doing pairing in a distributed team. Read about experiences with remote pairing.
You can increase the quality of products by constantly increasing the level of automation of the delivery process and working with DevOps teams who constantly deliver small features to get quick customer feedback. A case story from ING Lease explaining the problems they had, experiences from the first steps of their agile and DevOps journey and exploring what they want to achieve in the future.
Here's an experience story from a tester who decided to move onward and become a Scrum master to help her team to become more agile, with learnings from their agile journey and pieces of advice for doing change in organizations.
In the closing keynote of the Agile Eastern Europe 2015 conference Yves Hanoulle did an experiment together with his son Joppe in pair presenting. InfoQ interviewed Joppe and Yves Hanoulle about doing experiments, checking the safety of the environment and ways to make it safer, learning from failure, and presenting in pairs at conferences.
Laughing can help to create a better team climate which can lead to better results. There is compelling evidence that happiness and positivity can lead to success. Here are some suggestions for what you can do when you want to improve happiness in teams.
Pair Programming is good for increasing the software quality and collaboration within team members but it is hard to implement. This news describes the reasons why it is hard and how to figure out good practices of pair programming for your team.
The software craftsmanship movement talks about practicing as a way to to develop programming skills to become software craftsmen. Technical practices are considered to be important, it takes time to learn them and become better programmers.
Valentin Tudor Mocanu described upgraded form of pair programming using pairing and non-solo development.
Software debt exists in different ways. Technical debt is widely known, some other forms are competence debt and quality debt. Software debt can cause product maintenance costs to increase and can depress developers. Several solutions exist to manage software debt.
An exploration of recent advice from Henrik Knibert, Ward Cunningham and Hayim Makabee on technical debt, how to make the most of it and when to pay it off.
Simplicity, feedback, communication, respect and courage, these eXtreme Programming (XP) values still inspire the team of the XP Days Benelux 2013 conference. InfoQ did an interview with two of the conference hosts, Merlijn van Minderhout and Pascal Van Cauwenberghe, about new developments in agile, successful agile transformations and the needs of European organizations in agile adoption.
Swarming is a technique that helps agile teams to deliver working software fast and frequently. What is swarming, what are the benefits of swarming, and when and how to apply it?
The Wall Street Journal has begun to take notice of the growing number of technology companies that have been practicing Pair Programming and has published their take on the practice in an article titled Computer Programmers Learn Tough Lesson in Sharing.
Wikispeed founder Joe Justice gave a talk in Wellington, New Zealand, this week in which he spoke about the Wikispeed mission of "Rapidly Solving Problems for Social Good", starting by using agile techniques to build a 100MPG vehicle with the intent of creating a new approach to motor-vehicle manufacturing, using open-source and crowd-source approaches building on agile values and principles.