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.
Recently there have been a number of posts which challenge the way agile methods have been applied in industry and present some ideas on improving adoption and outcomes by tackling the underlying problems. Andy Hunt proposes a completely new approach branded The GROWS Method(tm) and Dan Greening suggests clarifying the core concepts which underlie agile approaches and describing them for use.
Vasco Duarte suggests that people should experiment with #NoEstimates to learn and find ways in which it can help them to deliver value on time and under budget. He is writing a book on #NoEstimates in which he explains why estimation does not work and how you can use #NoEstimates to manage projects.
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.
Making teams working together can be challenging, but it is often needed to develop and deliver large complex products. In her opening keynote about scaling dilemma's at the Agile Adria 2015 conference Mary Poppendieck presented ideas for organizations that want to scale agile.
The world has changed - therefore we need to transform command-and-control companies for them to adopt a new organizational model, says Niels Pflaeging. The BetaCodex Network that he co-founded applies research and open innovation to increase understanding of a "Beta" model for organizations that is suited to today's markets.
Last week the AgileWelly meetup group hosted an OpenSpace event in which over 100 people participated in examining topics under the theme "Agile Adolescence: The Growing Pains". Over the course of the day over 25 sessions were held which explored factors ranging from deployment of continuous delivery to actors that result in highly motivated teams.
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.
InfoQ did an interview with Charles about the role of the PMO in an agile organization.
The Agile Alliance has announced the speaker lineup and program for the Agile 2015 conference and the Agile Executive Forum, both events being held in Washington, DC in August 2015.
David Dame, enterprise agility change agent and organizational coach introduced scaling engagement agility in his recent blog. He says that instead of process scaling, think of engagement scaling.
This post talks about using an agile implementation for data warehouse projects.
DevOps promises to break down the barriers between the developers and the systems operators, but success with DevOps hinges on the company's culture and flexibility.