XP (eXtreme Programming) Engineering Practices such as Continuous Integration, User Stories, Pair Programming and Test Driven Development can mean the difference for a Scrum team between saying that you’re agile and actually being able to be competitive in the market and maintain high quality and confidence in your code.
Pair Programming is probably considered to be the most extreme ‘Extreme Programming’ practice, and a powerful technique for unlocking learning in a software development team. This video looks at this cultural practice that supports our ability to create better software faster in continuous delivery and DevOps teams.
If today many people equal Agile with Scrum, the Agile approach is also deeply rooted in software engineering practices, like pair programming or refactoring, promoted by the eXtreme Programming (XP) movement. In this book, Emily Bache presents the Samman Technical Coaching approach. It is a method for helping software development teams to become more agile and raise the quality of their work.
Modern software development inspired by Agile approaches welcomes changing requirements, even late in the process, but how can we write our software so that those changes don’t create a mess? Evolutionary design is the key.
The concept of team is at the heart of Agile software development and frameworks like Scrum. Forming high performance Agile teams is however not obvious. In this article, Debbie Madden suggests five steps that could bring your software development teams beyond the basic principles of Agile.
If delivering business value should be the main goal of a software development project, not all the developers’ activities are contributing to this objective. In his book ” Scrum Shortcuts without Cutting Corners”, Ilan Goldstein discusses how you should deal with bugs and the technical aspects of your software project.
Pair programming is one of the original practice of eXtreme programming, but it is also one of the least used by Agile software development teams. In his blog post, Alisdair McDiarmid explains how Customer.io uses pair programming with remote teams.