Continuous Integration can help to find integration issues earlier and to visualize the status of the build to all involved. Integration problems can be detected at build-time in stead of run-time during testing and teams can get immediate feedback on changes that they made and on the impact on components that are developed by other teams.
Teams rarely consider success as a mode of failure, but not preparing for exceeding their goals can be just as dangerous as ignoring basic software and infrastructure needs. Mark Simms and Mark Souza discuss anti-patterns they've seen and some of the best ways to architect to win in spite of your own success.
Oftentimes, complex software projects span across multiple repositories on account of external dependencies. This can be a challenge in itself, explains Google WebRTC engineer Patrik Höglund, who also described Google's approach to developing software that uses dozens of third-party libraries such as Chrome.
InfoQ interviewed Hans Aerts, vice president software development and agile coach at TomTom, about why they decided to adopt SAFe and how it was introduced and used to simplify the organizational structure and stop doing projects, why they focus on throughput rather than output, how they modified SAFe for Custom Systems, and what using SAFe has brought TomTom.
An interview with Yaniv Yehuda, Co-Founder and CTO of DBmaestro, about how they are doing agile development and using DevOps, how they implemented continuous delivery, on agile practices that turned out to be difficult to implement, and the benefits that they are getting for using agile and DevOps practices.
InfoQ did an interview with Gil Zilberfeld about better ways to do product planning and tracking, his thoughts about #noestimates, including value in product planning discussions, and how to improve decision making in product development.
At Unruly teams have been applying eXtreme Programming (XP) since being founded in 2006. Teams take a test-first approach to developing code and invest in automated checks that can be run in live environments. InfoQ interviewed Rachel Davies about the importance of a continuous approach to testing, how this has evolved over the years and the business advantage that it delivers to Unruly.
Tomas Rybing, Director, Project Management at Aptilo Networks, proposed a prioritization technique called ‘Priority Pyramid’, in agile environment.
Jurgen Appelo proposes a new technique of work management called the chunking technique intended to increase productivity.
InfoQ did an interview with Gil Zilberfeld about managing the expectations that organizations have of agile and how to prevent misconceptions, valuable ideas and practices from agile and what the future will bring for agile.
The gap in agile adoption between Eastern Europe and the US and Western Europe is becoming smaller. Scrum is the most widespread framework, Kanban adoption is growing and SAFe, LeSS, DAD are trending. The way that companies are transitioning to agile is significantly different in Eastern Europe.
The recently released Maven 3.3.1 adds support for core extensions to be added to a project through additional metadata as well as using alternatives to the eponymous pom.xml file for building. This has been used to create build scripts for JRuby that build upon Maven but use a JRuby script to represent dependencies and plugins.
MSBuild, the command-line tool used to build Visual Studio solutions and projects has been released to GitHub under an open source license. This paves the way for non-Windows systems to build .NET-based applications without requiring Visual Studio to be installed.
There are some alternative ways of identifying different classes of service in kanban. This post talks about these methods.
At QCon London 2015 Phil Calcado shared lessons learnt from SoundCloud’s move from a monolithic to microservices architecture, and stated that the core requirements for building a microservice platform include developing capabilities for rapid provisioning, basic monitoring and rapid application deployment.