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.
Microservices are conceptually too big; they conflate optimizing for organisational and technical factors, but solutions to problems of each type may not fit together very well, Phil Wills, senior architect at The Guardian, explained in a presentation at the QCon London conference promoting thinking about independent services and single responsibility applications, rather than microservices.
At the last QCon London, Michael Brunton-Spall, Technical Architect at the UK's Government Digital Service, expressed his views on how DevOps patterns are crucial to successfully operate microservices. Brunton-Spall identified the key ingredients to identify a microservice, explained how to build your first microservice and the necessary tools and practices to manage an ecosystem of microservices.
At QCon London 2015, Dave Farley proposed that although the state of software development has been suboptimal in the past, studies are revealing that the implementation of continuous delivery leads to considerable improvement. Farley stated that continuous delivery changes the economies of software development, and provides more rapid business idea validation and reduced defect rates.
Yuval Yeret is a senior enterprise Agile Coach at AgileSparks. At the upcoming Agile India conference he is talking on good and bad ways to kickstart agile the Kanban way. He spoke to InfoQ about the synergies between Kanban and DevOps.
This post includes the limitations of Five Whys technique.
Mingle continuous integration now takes 40 minutes to complete one build.Sudhindra Rao, Software Consultant at ThoughtWorks shares the achievement.