At the recent Agile 2016 conference, ICAgile announced a number of milestones – more Certified Experts qualified, some additional certification pathways, and substantive growth in certified participants and member training organisations. Ahmed Sidky and Shannon Ewan discuss all of this with InfoQ and why the agile mindset is more important than any set of practices or techniques.
This article describes two novel practices for continuous delivery: Latent-to-live code pattern and Forward compatible interim versions. You can use these practices to simultaneously increase speed and reliability of software development and reduce risks. These practices are built on top of two other essential continuous delivery practices: trunk-based-development and feature toggles.
Software technical practices are usually adopted as a means of creating better products. These practices can create and maintain a healthy human system. Technical practices raise the consciousness of individuals and the team as a whole. Technical practices hack consciousness giving us a quick, deep chute into depths of connection that improve our selves, our products, and our world.
Bimodal IT has been supported by many and criticized by many. InfoQ reached out to enterprise experts to dig deeper into the pros and cons of this strategy and how/when/if is it applicable.
More and more companies are realizing that having an Agile organization is critical to attracting and retaining the latest generation of millennial engineers. Here’s why.
We hear, and even use, the phrase “agile mindset.” But what is it, really? In this article several themes are identified, and ideas for introducing and nurturing these themes are discussed. 4
Christine Doig spoke at OSCON Conference about data science as a team discipline and how to navigate data science Python ecosystem. InfoQ spoke with Christine about challenges of data science teams.
The book Effective Debugging by Diomidis Spinellis describes 66 different approaches for effective debugging of applications and systems.
It is not Agile's fault, it is your fault- are you fed up with such statements? This article tries to provide a more constructive answer on how to make Agile successful. 13
Iterative development requires gradual flow of small-sized, prioritized requirements from end customers to delivery teams. The use of all-conclusive, rigid, non-negotiable BRDs leads to dysfunction.
Mobile app development adopted an iterative, rapid development process. Prototypes have a role to play in this agile approach, enabling developers to build, test, iterate rapidly and at lower cost.
What makes an agile team successful is the way people develop an effective level of interaction. Growing agile means both focusing on culture, and on co-evolution of practices and tools. 2