The Agile Manifesto establishes 12 principles for Agile software development. Most software that has a dependency on another software inherits its Agile features—and in this article, we will explore what makes Apache Kafka suitable for Agile software development.
One of the Agile principles is simplicity—the art of maximizing the amount of work not done is essential. Kubernetes provides simplicity through different features based on the Single Responsibility Principle for decoupling, and through automating tasks such scaling, resource allocation, and making updates.
While a few other types of containers are available, Docker is the de facto standard for containerization. Containerization involves running multiple applications in containers on a Docker Engine that runs on an underlying operating system. The principles of Agile software emphasize simplicity, interactions among individuals, working software, customer collaboration, and responsiveness to change. Docker containers make all of these feasible.
For software companies and developers, keeping up with the trends means offering state-of-the-art software products and establishing themselves as innovation leaders. Enterprises and businesses will, on the other hand, have to decide between purchasing an existing software solution or cashing in for a customized product tailored to their needs.
Most software developers are in either the agile or the waterfall camp. Agile is required to be competitive, but many enterprise processes still rely on waterfall practices for stability. They can coexist.
Melissa Benua, director of engineering at mParticle, chats with TechWell community manager Owen Gotimer about the importance of whole team quality, how to get started using the test pyramid, and how developers can start writing testable code.
In this interview, Brandon Carlson, a consultant at Lean TECHniques, explains how all the newer aspects of software have come together. He explains how things have changed since agile has grown in prominence and what DevOps does for testing and development.
Larry Putnam Jr., co-chief executive officer at QSM, sits down to talk about the importance of the proposal when executing a successful project, five key questions that should be answered before any project starts, and how software estimation ties into the proposal process.
Steve Berczuk is a regular contributor to TechWell and StickyMinds and a principal engineer and ScrumMaster at Fitbit in Boston. In this interview, Steve discusses configuration management and agile, helpful tools, and how testing has evolved over the years with the rise of agile.
More than two decades ago, Richard P. Gabriel proposed the idea that “Worse Is Better” to explain why some things that are designed to be pure and perfect are eclipsed by solutions that are compromised and imperfect. This is not simply an observation that things should be better but are...
Your organization is embracing agile. When it comes to adopting the process, your team seems to be doing all the right things. Yet deep down, something still doesn’t seem quite right. As their leader, it could be that you haven’t figured it out either. Perhaps your team is lacking some...
Transforming software development across geographic locations in a large company is difficult. But Nationwide Insurance found a way to successfully implement more than forty agile teams in multiple locations around the United States using their internal Application Development Center.
Top web companies employ continuous delivery of software to build and deploy systems faster and gain a marked competitive advantage. You can do it, too! Andy Singleton shares the patterns for testing in real time that result in more frequent and more reliable releases. He explains why...